CBOR isn't a hobby spec. It's integral to the WebAuthn API spec. Every time someone uses a passkey, CBOR is used to exchange messages with the authenticator
why was CBOR used for WebAuthn and was that a good idea?
Readit News0x006A commented on From XML to JSON to CBOR cborbook.com/introduction... · Posted by u/GarethX
0x006A commented on Xkcd 1425 (Tasks) turns ten years old today simonwillison.net/2024/Se... · Posted by u/ulrischa
One could say, "This didn't age well." but I think the real point of "it can be hard to explain the difference between the easy and the virtually impossible" is only reinforced by an almost ironic twist that switched the hard and easy around. Who would have thought ten yeas ago?
Its worth looking at the alt text of the xkcd itself: In the 60s, Marvin Minsky assigned a couple of undergrads to spend the summer programming a computer to use a camera to identify objects in a scene. He figured they'd have the problem solved by the end of the summer. Half a century later, we're still working on it.
It kind of is layered on top, no?
WebDAV didn't really catch on, but the general product space of remote drives did. The problem with WebDAV is that like most Web* tech (and maybe Braid) it's design by committee in the abstract. To make remote drives work well for the end user requires a fairly complicated protocol with tons of ugly edge cases. The interoperable standards from committees approach tends to fail in those situations, whereas hard driving startups that use proprietary protocols they can iterate quickly tend to win.
Iteration speed > openness, when there's nothing to copy from. Standardization tends to be about bigger companies trying to commodify their competitors.
many proprietary protocols iterate themself out of existence, just because some of them survive does not mean its the better model. Look at the video codec space, proprietary codes have long lost and have gone the way of Real Media, Windows Media Video and many others. While H.26X which is the result of design by committee are used everywhere.
0x006A commented on Hackers interrupt UAE TV streaming services with deepfake news theguardian.com/technolog... · Posted by u/sandebert
is the video available somewhere?
0x006A commented on Bluesky signups are now open to the public bsky.social/about/blog/02... · Posted by u/jakebsky
Let's say you just eliminate the requirement altogether. What percentage of non-phone number signups are going to be "thoughtful people" compared to bots?
Sure you'll get people who refuse to sign up with a real phone number, that's a given. Some percentage of those people will be "thoughtful." You'll also eliminate a huge number of bots, automated signups, etc.
It's hard to argue letting all those bots on will not decrease system quality.
do you have an example of a platform that does not require a phone number for sms verification and is filled with bots? we have many that use sms verification and are infested with abusive content and bots.
0x006A commented on Canonical LXD forked by former project leader stgraber github.com/stgraber/incus... · Posted by u/loloquwowndueo
https://github.com/cyphar/incus/issues has a nice list of planned cleanups the fork will have compared to lxd
Deleted Comment
0x006A commented on Linux kernel use-after-free in Netfilter, local privilege escalation seclists.org/oss-sec/2023... · Posted by u/kuizu
> delete an existing nft rule that uses an nft anonymous set. And an example of the latter operation is an attempt to delete an element from that nft anonymous set after the set gets
deleted
I'd be very interested to hear how this can be done by an unprivileged user.
Try to race set add/removals, sure, but if it depends on the set itself getting deleted, that seems… harder.
on https://bugzilla.redhat.com/show_bug.cgi?id=2196105 a comment suggests that it might only be possible if you have "unprivileged user namespaces" enabled
0x006A commented on Show HN: ChatGPT Inline Bot on Telegram chatgptontelegram.com... · Posted by u/sandoche
Thank you for your question and for bringing up your concerns. My micro-enterprise is registered in France, you can find more about me and all the side projects I worked on at sandoche.com, hope it helps and feel free to use to contact button to get support :)
Some sites say your company was closed down in 2021, whats up with that? Etablissement fermé le 01-07-2021