brian
@briancloutier.com
what is the ideal future and how do we get there?
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
- entertaining: come and laugh with me
- educational: learn how to get better at this game
- competent: watch someone who's incredible at this game
January 24, 2025 at 4:24 AM
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
- entertaining: come and laugh with me
- educational: learn how to get better at this game
- competent: watch someone who's incredible at this game
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
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
January 21, 2025 at 8:57 AM
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
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?
key engagement metric: how many users eventually become irl friends?
January 17, 2025 at 11:44 PM
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?
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
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
January 17, 2025 at 10:34 PM
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
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
a cool visualization from the washington DOT, the optimal amount of traffic is a lot higher than you might prefer it to be (ht www.construction-physics.com/p/reading-li...)
January 13, 2025 at 2:49 AM
a cool visualization from the washington DOT, the optimal amount of traffic is a lot higher than you might prefer it to be (ht www.construction-physics.com/p/reading-li...)
some proposals for passwordless wifi. All of these are possible, and have been possible for many years, but standards are hard to bootstrap:
January 12, 2025 at 3:23 AM
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
- 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
January 8, 2025 at 5:38 AM
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
- 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 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!
all your derivations are correct, it's the published result which is wrong!
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
January 2, 2025 at 12:24 AM
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!
all your derivations are correct, it's the published result which is wrong!
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
this makes sense by the same economic logic which powers franchise restaurants
December 31, 2024 at 1:53 AM
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
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
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
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...
December 30, 2024 at 11:18 PM
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
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
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 😮
appalled to find out today PLC uses the nostr approach but with a single trusted relay which can censor anything 😮
December 30, 2024 at 5:58 PM
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 😮
appalled to find out today PLC uses the nostr approach but with a single trusted relay which can censor anything 😮
does anyone run an alternative atproto relay? everyone seems to read from "the firehose" but surely there are others somewhere out there?
December 27, 2024 at 11:07 PM
does anyone run an alternative atproto relay? everyone seems to read from "the firehose" but surely there are others somewhere out there?
after reading every NIP the nostr protocol also seems very cool, it's a shame it is currently being used exclusively to talk about bitcoin
GitHub - nostr-protocol/nips: Nostr Implementation Possibilities
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
github.com
December 27, 2024 at 4:37 AM
after reading every NIP the nostr protocol also seems very cool, it's a shame it is currently being used exclusively to talk about bitcoin
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
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
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
lexicon component and URIs could be helpful-ish? I feel like something could be worked out... but should stay focused for now
December 26, 2024 at 6:58 AM
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
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
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
December 26, 2024 at 2:21 AM
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
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
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
this week on NULL BITMAP, intuition for snapshot isolation: it’s like git buttondown.com/jaffray/arch...
Git Workflow is Snapshot-Isolated
We are apparently continuing our series of posts borne from thinking about Amazon DSQL. Today we are talking about skew. Amy and Bill are two developers...
buttondown.com
December 25, 2024 at 7:35 PM
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
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?
- 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?
December 23, 2024 at 12:09 AM
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?
- 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?
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?
The Triumph of Bacchus, by Diego Velázquez, 1628-29
December 22, 2024 at 6:04 AM
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?
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?
my first custom feed: Top Articles
It shows you the links the people you follow have most shared in the last 24 hours
It shows you the links the people you follow have most shared in the last 24 hours
December 14, 2024 at 7:49 AM
my first custom feed: Top Articles
It shows you the links the people you follow have most shared in the last 24 hours
It shows you the links the people you follow have most shared in the last 24 hours
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
A new lexicon for defining interfaces/applications would enable atproto to become beautifully self-hosting
December 11, 2024 at 10:15 AM
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
A new lexicon for defining interfaces/applications would enable atproto to become beautifully self-hosting
Don't think I'll be doing a firehose post every day but really enjoying watching new services launch. In the last 24 hours a few more new atproto applications launched and saw some adoption:
- @pinksea.art, a drawing BBS
- pastesphere.link, a pastebin
- @woosh.link, a linktree
- @pinksea.art, a drawing BBS
- pastesphere.link, a pastebin
- @woosh.link, a linktree
Pastesphere
pastesphere.link
December 9, 2024 at 12:27 AM
Don't think I'll be doing a firehose post every day but really enjoying watching new services launch. In the last 24 hours a few more new atproto applications launched and saw some adoption:
- @pinksea.art, a drawing BBS
- pastesphere.link, a pastebin
- @woosh.link, a linktree
- @pinksea.art, a drawing BBS
- pastesphere.link, a pastebin
- @woosh.link, a linktree
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
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
December 8, 2024 at 12:41 AM
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
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
I'm enjoying browsing this long tail of experiments & typos
December 7, 2024 at 1:35 AM
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
I'm enjoying browsing this long tail of experiments & typos
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
But now you can bootstrap using the bluesky network: a browser extension which adds a sidebar of (filtered) bluesky comments to _every_ page
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
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
November 28, 2024 at 9:08 AM
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
But now you can bootstrap using the bluesky network: a browser extension which adds a sidebar of (filtered) bluesky comments to _every_ page
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
November 27, 2024 at 10:47 PM
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