pfraze

Congrats on the launch, tangled team!

Just pick the right technologies for the right problems. If your scale is entirely interpersonal - small orgs, friends, family devices - then p2p is much more likely to be a good choice.

Yeah, mod team reacted accordingly. The site needs automated dogpiling detection and intervention. It's a problem.

The current cross-deals aren't purely circular; quite a bit of revenue is, in fact, flowing into the AI industry from the outside (you know, via customers). What's more notable is the shared risk, as the deals tie multiple companies across the chain to a set of shared bets.

If the frontier labs suddenly found themselves unable to compete with cheap open weight models running on widely available compute, then one might expect the frontier labs to be the only ones exposed to that risk, while a chip-manufacturer like nvidia could thrive in either environment. A partnership or commitment from the chip manufacturers to the frontier labs could change that. Whether that kind of inescapable connection exists is hard to predict without a lot of specific modeling, and at this point I'm inclined to think that neither chip nor datacenter demand is going to drop any time soon, and that the commitments would be unwound before a company like nvidia is threatened.

I’m asking what you mean by “Bluesky openly promotes communist symbolism”

I’ll give a pretty honest accounting of that.

We made it a pretty big goal from the start to clearly communicate to users that the network is extremely public, and that we believe open access to public content is an important part of preventing another round of walled gardens. This is generally understood and appreciated, but the community has a wide range of opinions about it. Some people see public as public and that they’re there to have their voice heard. Some people see it as a pretty uneasy arrangement at best, and would rather it wasn’t that way.

The atproto community has been spending a large portion of the year developing “atproto spaces,” which are essentially a way to cheaply mint mini-atprotos with access control. This is the answer to non public data. It will be added to the Bluesky app and the ecosystem, and it will remain accessible to apps based on the grants of the users, but the spaces will not broadcast their content on the firehose. I believe, based on the reception we’ve received from that work, that people appreciate that it’s being done, and that people eager for less exposure will pick it up.

This should, hopefully, resolve any tensions at play. We will continue to advocate for public speech and I think many people will continue to participate in it, but I am quite curious to see if the non public spaces gain more adoption overall. My guess, based on people’s general use of the internet, is that they naturally will. The public arenas serve a particular purpose and not everyone is always trying to be a part of them.

EDIT: did I really just say "let me give an honest accounting of that." I have been spending way too much time with llms.

> You would repost a page by linking to it from your own.

Ah right, of course. Fair enough. I think Dave Winer is trying some similar ideas, though I haven't looked at it beyond knowing he's trying to extend RSS to support these capabilities.

Yeah that'd be interesting to try. If you extend the endpoints and the vocabularies around RSS/OPML enough, you could likely create a fairly robust dataset replication protocol. Microformats are a decent schema basis, but you might want to build upon them as well. If you want to make the users' sites reusable as a datastore across applications, you could introduce an oauth flow to enable 3rd party writes. You might also want to add content signatures so you can verify the data authenticity from third parties (e.g. to support the equivalent of reposts).

Genuinely curious, how would you build it differently? Would you stick with atproto's indexing model and try to simplify it, or would you use another approach?

The team came from the IPFS and Scuttlebutt worlds. "Better" is relative to your design goals. Iroh is better for point-to-point connections & localfirst. Matrix is better for chat rooms. Etc. The general logic of atproto was to serve large scale publishing with an open model that doesn't seriously degrade the UX. The scale orientation means - at least until the non-public spaces land - you're syncing a lot of records to provide an alternative microblogger to bluesky. The account hosting system, however - the pds - remains exceedingly cheap and easy to run. Pros and cons, matching with the design goals.

PLC's board composition and country of residence are designed to shield from that. At best it will only ever be as effective at this as ICANN, which is roughly our target.

It does?

New account, 4 comments, one includes “Musk’s takeover of Twitter was a net win for free speech”