Cryptography nerd

  • 1 Post
  • 1.4K Comments
Joined 1 year ago
cake
Cake day: August 16th, 2023

help-circle







  • Technically yes but also no.

    Synchronized reading is hard when the pixel count is high. At some point it’s hard enough to pull all the data through the controller at once quickly so you need either multiple circuits, or one circuit that reads a section of pixels at once (row by row = rolling shutter effect).

    Some of this is processing limits in the internal controller in the sensor, but it’s also timing and signal routing and synchronized readout for a massive amount of pixel sensors. It’s literally tens of millions of triplets of RGB detectors which has to be read simultaneously 60 times per second, and basic color correction has to happen right in the controller, before the main CPU / GPU gets the image stream.

    At some point you even get cooling issues, and need a cooling system behind the sensor.










  • You don’t have to deal with being sent links to other people’s mail servers’ public mail lists, and then figuring out how to get your own mail server to figure out how to join that conversation. Mailto links open in your mail client which already knows what your server is.

    Mastodon don’t have a mailto: equivalent, pages can’t identify themselves in a way your browser recognize as a Mastodon host, your browser won’t remember your Mastodon account(s) specifically. And federation sync issues aren’t even dealt with here…


  • That’s what bluesky’s DID based account identity does. Unless you make that key the sole authority (no key rotation, like nostr) then you need a registry as authority (like bluesky’s PLC registry)

    Bluesky specifically lets the account hosting server handle your auth, the directory points to where your account server is as in when you enter your handle, every 3rd party service and federated peer can do OAuth seamlessly to your account host. Then you can log into every compatible site with your handle, instead of having to get redirected “home” before you can interact. Your account server’s repository keeps records of all your posts and your social network, and you can even migrate seamlessly across hosts.


  • They’re actively working on making it easier to fork the entire platform.

    There’s already 3rd party account hosts, moderation labelers, feed generators, and alternative implementations like whitewind (blogging system on top of the same account repo & lexicon architecture) were you can use the exact same account. All of these works together independently of which hosts / providers you use.

    Relays and microblogging appviews (a fully functional bluesky mirror) are technically possible but more expensive to duplicate but there’s work on making that practical too.

    You can already bypass PLC by using DID:Web for account identity.

    The single most important thing if you want to be able to recover from bluesky going bad is to just back up your account recover signing key, and to keep a recent backup of the repo to preserve your post history and social network (follows, etc).

    All the rest can be rebuilt if you have your account hey and backup. The content addressing will make it seamless!