Yes, this does help, but atproto as a whole still doesn't scale well:

In the beginning of our network, we have 26 users, which conveniently for us map to each letter of the English alphabet: [Alice, Bob, Carol, ... Zack]. Each user sends one message per day, which is intended to have one recipient. (This may sound unrealistic, but this is fine to do to model our scenario.) To simplify things, we'll have each user send a message in a ring: Alice sends a message to Bob, Bob sends a message to Carol, and so on, all the way up to Zack, who simply we wrap around and have message Alice. This could be because these messages have specific intended recipients or it could be because Bob is the sole "follower" of Alice's posts, Carol is the sole "follower" of Bob's, etc.

Let's look at what happens in a single day under both systems.

Under message passing, Alice sends her message to Bob. Only Bob need receive the message. So on and so forth.

From an individual self-hosted server, only one message is passed per day: 1.
From the fully decentralized network, the total number of messages passed, zooming out, is the number of participants in the network: 26.
Under the public-gods-eye-view-shared-heap model, each user must know of all messages to know what may be relevant. Each user must receive all messages.

From an individual self-hosted server, 26 messages must be received.

Zooming out, the number of messages which must be transmitted in the day is 26 * 26: 676, since each user receives each message.

Okay, so what does that mean? How bad is this? With 26 users, this doesn't sound like so much. Now let's add 5 users.

Under message passing:

Per server, still 1 message received per user per day.
Per the network, it's 5 extra messages transmitted per day, which makes sense: we've added 5 users.
Under the public-gods-eye-view-shared-heap model:

Per server: 5 new messages received per user per day.

Per the network, it's ((31 * 31) - (26 * 26)): 285 new messages per day!

But we aren't actually running networks of 26 users. We are running networks of millions of users. What would happen if we had a million self-hosted users and five new users were added to the network? Zooming out, once again, the message passing system simply has five new messages sent. Under the public shared heap model, it is 10,000,025 new messages sent! For adding five new self-hosted users! (And that's even just with our simplified model of only sending one message per day per user!)

Source: dustycloud.org/blog/re-re-blue…

As well as this, if there was a reddit-like atproto AppView, setting up multiple instances of it would still result in the same problems.

But this is assuming private messages no?

When 99% of the public traffic is on posts that will federate to most servers, this model becomes irrelevant.

Das Bild zeigt zwei Cartoon-Vögel auf einem Felsen vor einem blauen Hintergrund mit grünen Pflanzen. Der linke Vogel ist rot und hat eine besorgte Miene, während er spricht: "Schatz, wir müssen reden!" Der rechte Vogel ist orange und hält ein Smartphone in der Hand, während er antwortet: "Kann ich nicht einfach irgendwo unterscrollen und auf „Akzeptieren“ drücken?" Der orange Vogel scheint auf das Smartphone konzentriert zu sein. Die Szene spielt auf die moderne Kommunikation und die Verwendung von Smartphones an, insbesondere im Kontext von Online-Interaktionen.

Bereitgestellt von @altbot, privat und lokal generiert mit Ovis2-8B

🌱 Energieverbrauch: 0.164 Wh

Open social media software enables all users alike, the ones who want to genuinely connect with other people on the left hand, and on the right hand, the ones who want to scam as much as they can out of NPCs just for a higher score carved into their grave marker. They each benefit from the same work, but one side tends to kick back more to the toolmakers.

But that's not capitalism. The only innovation capitalism breeds is how to capture more of the consumer benefit of trade.

@77nn Quali librerie/framework linguaggio utilizza si legge a 11:41: Vite, typescript ecc ecc..
Ci sono le istruzioni di deploy sulla pagina github che ti crea nel repo, ho chiesto che venissero inseriti più assegnatari per un task, ma non ho chiesto esplicitamente una piattaforma multi-utente, e in effetti non è stata creata come tale.

Con LLM la chiarezza nell'esprimere requisiti e richieste è fondamentale. Chiaro che se fossi partito con zero conoscenza dell'ambito e zero terminologia...

The image shows a parking lot with a trailer in the foreground. The trailer is beige with a wooden platform and has a large wicker basket-like structure on top, labeled "RIO GRANDE BALLOONS." The basket is secured with straps and appears to be a hot air balloon basket. The trailer is hitched to a vehicle, likely a pickup truck, which is not fully visible. In the background, there are two parked vehicles: a silver SUV and a dark-colored pickup truck. The setting is outdoors, with trees and a clear blue sky visible. The ground is paved, and there is a small landscaped area with shrubs near the trailer. The scene is well-lit, suggesting it is daytime.

Provided by @altbot, generated privately and locally using Ovis2-8B

🌱 Energy used: 0.178 Wh