Like peers could sign sites?
HN user
evbogue
https://evbogue.com/
https://wiredove.net/#ev
https://github.com/evbogue
ev@evbogue.com
773-510-8601
We need git-ssb
Yes, and it only supports storing one's data in one place. If we use local-first as our measuring stick for a decentralized system then ATProto fails since we can't store the msgs anywhere -- such as on the nodes of my friends. Prior art such as secure-scuttlebot had this figured out, and thus no one ever complained about ssb being centralized.
It is not common, but it is becoming more common: https://arewedecentralizedyet.online/
Twitter Bootstrap 2 was the height of web design. If we can go back and stay there forever why should anyone fault our society.
ATProto would need to use signing key cryptography and content addressable storage to be distributed. If we can't store our data with third parties or create an offline-first system then it's not a decentralized social network.
Codex-cli / OpenClaw. If you need a browser use Playwright-mcp.
I can't see why I'd want an agent to click around Gnome or Ubuntu desktop but maybe that's just me?
I use it. I think everyone should try the original version out before it gets too muddled so they get the spirit of the thing even if it doesn't end up being the thing -- in a safe space where you know what data you're allowing it to claw thru.
This is why I'm hoping fiatjaf has a recommendation here. I have a feeling he might have a proposal that solves this. But doesn't solve all of it, just some of it.
What's stopping us from doing both?
If multiple personal data servers (pdses) share the same set of posts how would we guarantee that they are tamper resistant to third parties?
Do you have ideas about how Bluesky could decentralize?
How does Anthropic detect that a person is using OpenClaw vs using Claude Code?
Forgive me if someone asked this already and I can't find it in the comments.
I received the error, but then my account reflected that I had been credited the $20 eventually but still showed that I could claim it.
lol, email me! I'm still an active user. ev@evbogue.com or 773-510-8601
As an early Deno purist I must invoke the 10 Mistakes talk that Ryan gave when he launched Deno: https://m.youtube.com/watch?v=M3BM9TB-8yA&t=11s&pp=ygUScnlhb...
Agreed about the article tone. I'm a Deno lifer over here, and will definitely not try to cover up the mistakes they've made along the way or the trouble their deploy product has had over the past few months. Ryan Dahl is obviously polarizing as a personality for many people, always has been since he decided to "hate almost all software" or even before that when he created Node.js.
I don't use Fresh. Serverless is kind of a weird offering that forces developers to do a lot of work to adjust their programs to running all over the place. I even wish Deno had never supported NPM because that ruined their differentiator.
I'm going to keep using Deno and I hope they use this opportunity to refocus on their core product offering so that I can move back to using it from this VPS that is hosting all of my Deno servers right now.
and thx for being the first person to notice the thin wrapper
userspace
This obviously needs some iteration on the protocol design as other commenters have mentioned, but I'd still be up for partnering up over here at https://anproto.com/
It can be both.
Bluesky does solve a lot of SSBs problems. Both projects can learn from each other. The past can become the future and the present inform the past.
This isn't just on Paul, Jay has publically stated that she doesn't believe users (even powerusers) can be trusted with keypairs.
I'd like to encourage anyone who is wary of Bluesky to check out Paul (and Dominic's) back-in-the-day project Secure-Scuttlebot which solved most of the issues that Bluesky suffers from by using content addressable storage and signing key cryptography correctly.
The actual SSB codebase has been kind of broken since 2020, but I have a fork on my own Github that works and comes with a basic client that you can vibe/claw on top of: https://github.com/evbogue/ssbc
I'm happy to supply pub invites to anyone who wants to play around with the old sbot with me as we work towards making social media distributed again.
So you disagree?
I'd like to speculate, with the recent success of AI agents on the command line with OpenClaw, that perhaps IRC could be the future of AI-enabled chat rooms?
dude you represent yourself as a tony the AI worm.
I'll do an:// urls if you bring yourself and your code agent to myproto for an afternoon.
I disagree that Bluesky is in conflict with The Ecosystem Is Moving. In contrast to most decentralized/distributed protocol projects they've managed to maintain control of almost all of their infrastructure with the exception of the personal data servers (pdses) of which they control 99.01%[1]
Almost all ATProto apps just fetch posts by handle => did:plc => post-type aka "lexicon", so they depend on what Bluesky decides to give them. If someone were to introduce unknowns into the flagship product's "lexicon" they could fix that at the API or Indexing level before shipping this data to the apps that depend on their API.
An actually decentralized network would have to overcome Moxie's criticism of the ecosystem. Can it be done? We'll keep trying.
at://hash at://pub i guess I don't know why we need at:// that seems like something we'd need in Beaker Browser.
After reading the docs at https://atproto.com/specs/at-uri-scheme and building applications that integrate with the Bluesky API, it’s clear why this format is useful for interacting with their system. For developers working outside the ATMosphere, however, it may feel less familiar compared to more conventional REST API patterns.
We can have both a directory and use content addressable storage and give people the option of using their own keypairs. They are not mutually exclusive. Bluesky chooses to have a central directory and index.
Yes. SSB and ANProto do this. We actually can simply link to a hash of a pubkey+signature which opens to a timestamped hashlink to a record. Everything is a hash lookup this way and thus all nodes can store data.