brian

brian

@briancloutier.com

what is the ideal future and how do we get there?

279 followers2K following113 posts

the three kinds of gaming streamer: - entertaining: come and laugh with me - educational: learn how to get better at this game - competent: watch someone who's incredible at this game

some proposals for passwordless wifi. All of these are possible, and have been possible for many years, but standards are hard to bootstrap:

View full thread

when you visit your friend's corporate office your visit is already known ahead of time by envoy. your public keys are also known ahead of time, when you walk in your device automatically connects and is given guest access

same with airbnb: when you book credentials are passed to your device (which syncs them to all your other devices), when you walk into your airbnb the wifi announces which kind of credentials it's looking for and your devices send them over. From your perspective you just walk in and you're on wifi!

I'm very curious about the rationale, LSM seems like it should work pretty fine here. The circular bufferarity means every insert also inserts a tombstone so there's some unfortunate write amplification, but it doesn't seem outrageous to add a max keyrange length while sticking to the LSM model

Jaz@jaz.sh

And my stretch goal for this year is probably something like building a custom database for Timelines since it turns out the fixed-length, circular-buffer-per-user style with high write throughput (>1M writes/sec) pattern is not a great fit for LSM-tree based DBs or like, any conventional DBs really

as in: there's some global maximum timeline length and during mergesorts (compactions and queries) it only keeps the most recent n entries for each timeline

a "small world" custom feed which throws you into a cohort with ~20 other small accounts. the cohorts slowly change over time as it learns from who you interact well with and tries to match you with the perfect little community key engagement metric: how many users eventually become irl friends?

the paradigm of running `sudo apt install calibre` seems wrong every tool in the apt repositories should be "installed"; it is downloaded into a local cache when I first try to use it and automatically removed from the cache if I haven't used it in a while. nix, uv, bun, docker approximate this

some proposals for passwordless wifi. All of these are possible, and have been possible for many years, but standards are hard to bootstrap:

View full thread

when you walk into the cafe your device gets a notification: each MB will cost $0.10, once you hit approve you're immediately connected, your device handles the payments and shows you a running tally of how much you've spent

there's a wifi QR code on your airline boarding pass. By scanning that code you associate your device with your payment information and can simply hit "approve" to the charge it shows you in the payment portal

some proposals for passwordless wifi. All of these are possible, and have been possible for many years, but standards are hard to bootstrap:

View full thread

when you walk into someone's house their device is immediately notified, once they tap yes your device is allowed to connect to their wifi networks

a setting on my phone which pre-approves any of my starred contacts to connect to my wifi, when they walk into my house my wifi recognizes their public key and simply works without them doing anything

some proposals for passwordless wifi. All of these are possible, and have been possible for many years, but standards are hard to bootstrap:

love it, - did:plc, you trust bsky not to censor your account, otherwise have full control - did:web (typically), you trust your registrar to control your identity - did:web (this monstrosity), you trust your ISP and their dynamic DNS, famously very trustworthy and stable (!), to host your identity

This post is unavailable.

this must be the mathematician's version of finding a bug in your compiler all your derivations are correct, it's the published result which is wrong!

Daniel Litt@littmath.bsky.social

We started carefully rechecking the papers we were using, and eventually found an error, in a reasonably well-cited paper published in 2016. 6/n

in software your dependencies all have issue trackers you can submit corrections to, in math it seems your options are: privately email the original authors; publish your own paper; with little intermediate ground?

Daniel Litt@littmath.bsky.social

We contacted the authors, who promised to get back to us; they were confident the issue could be repaired. But eventually we found a counterexample to the main theorem of the papers in question; the authors graciously agreed. 8/n

a single-payer blockchain: the network is subsidized by one entity which directly pays out block proposers this makes sense by the same economic logic which powers franchise restaurants

love this! some more nostr's which nature has grown: - historically: books are sent to many libraries - academic papers: submitted to both journals and arxiv - music: submitted to both spotify and soundcloud - burning man: if it ever fails there are many other events which could pick up the slack

Gordon@gordon.bsky.social

Yes. Not only is it an interesting general-purpose protocol, it also demonstrates a pragmatic decentralized architecture that more protocols should consider (relay networks) newsletter.squishy.computer/p/natures-ma...

and of course: certificate transparency probably the biggest nostr in tech; new certificates are sent to multiple logs, browsers require certs to be published in multiple logs, the system can easily survive any of them failing

I always assumed PLC uses some kind of merkle-powered append-only ledger a la certificate transparency, call me a crypto bro but that's the right way to do what PLC attempts to do appalled to find out today PLC uses the nostr approach but with a single trusted relay which can censor anything 😮

a lexicon which defines the rules for a custom feed, and a universal custom feed which reads those rules from your repo and serves you exactly what you asked for

the truly principled way to do this is to first add a lexicon for webassembly binaries, then you can write little filters which reference the right binaries and the universal custom feed runs those filters when building your feed for you 😉

I love the idea of an atproto-powered wiki! With atproto we can have an opinionated wiki which shows you your favorite version of each page, ignores all contributions by anybody you've muted / blocked. We already have a wiki for consensus knowledge, atproto can give you a wiki without edit wars

bryan newbold@bnewbold.net

I agree somewhat: wiki is not a great fit for this version of atproto. want it more centralized, and repos don't scale up that far very well (for now) lexicon component and URIs could be helpful-ish? I feel like something could be worked out... but should stay focused for now

I am continually surprised this doesn't cause more problems git merge mostly just works without introducing any bugs but it has this seemingly huge flaw! looking forward to an LLM-aided git merge which considers the intent & semantics of each commit while merging

there's an opportunity to create the netlify of bluesky, put all your records into a git repo and this service serves them for you - a bluesky account is a bag of tuples, all a PDS "really is" is an interface relays use to fetch your tuples why not decouple the data storage from the serving?

how would one go about automatically finding the closest renaissance (in this case baroque) painting for some image? mb similarity search over an embedding db but this match is so perfect because it's a crop of the original image, some kind of registration algorithm has to happen during the search?

ArtButMakeItSports@artbutmakeitsports.bsky.social

The Triumph of Bacchus, by Diego Velázquez, 1628-29

Going the other direction: people keep trying to give every webpage a comment section (hypothes.is) but it's really hard to get a critical mass of users But now you can bootstrap using the bluesky network: a browser extension which adds a sidebar of (filtered) bluesky comments to _every_ page

Emily Liu@emilyliu.me

By popular request, here's how to add Bluesky replies as your blog's comment section! This requires some technical know-how for now, but I'm hoping that we see some no-code solutions for this pop up soon, like Ghost or Wordpress plugins. emilyliu.me/blog/comments

New atproto applications require a webserver for hosting the interface to the application. Your PDS just holds the data, not the application itself. A new lexicon for defining interfaces/applications would enable atproto to become beautifully self-hosting

Yesterday the firehose averaged over 700 events per second. Two million people liked at least one post and one million people made at least one post, an incredibly high ratio. New today: 11 people placed a bunch of pixels @place.blue

this is incomplete data (still working on stability) but I've started drinking from the firehose, over one million people sent at least one like in the last 24 hours! I'm enjoying browsing this long tail of experiments & typos

the bluesky architecture enables overlay feeds: it pulls from your Discover BUT also syncs with mochi and occasionally throws in some of your flashcards. It syncs with readwise and throws in some longforms you might prefer to read

The custom feeds API is incredibly flexible and could be co-opted to expose some fun features: - a choose your own adventure where you react to a post from a limited menu of posts then are shown the next menu - voting: you're shown two SoME math videos and asked to react to the one you like most

You are up to date.