Re: A native internet protocol for social media from Marcus Rohrmoser on 2023-04-18 (public-swicg@w3.org from April 2023)

From: Marcus Rohrmoser <me+swicg@mro.name>
Date: Tue, 18 Apr 2023 08:38:14 +0200
To: public-swicg@w3.org
Message-ID: <D2894192-E957-4203-8D5B-ACDA392C6EE0@mro.name>

On 17 Apr 2023, at 8:27, Melvin Carvalho wrote:

> ne 16. 4. 2023 v 23:48 odesílatel Bob Wyman <bob@wyman.us> napsal:
>
>> Melvin wrote:
>
>>> The challenge lies in creating a protocol that is interoperable,
>>> scalable, and allows users to have full ownership of their 
>>> conversations.
>
> in today's context, one might consider utilizing websockets

Websockets don't scale, do they? Imagine 10k subscribers/subscriptions 
from 10k instances. That means 10k persistent connections/websockets, 
doesn't it? What does that mean in terms of resources (descriptors etc.) 
and energy?

And what is the use case other than real-time? Which shouldn't be a 
requirement. Maybe not even an option from standpoints of personal 
privacy, mental health or technical energy consumption.

ActivityPub isn't instant messaging. And it shouldn't morph into that if 
it brings downsides. Which it does.

Marcus

Received on Tuesday, 18 April 2023 06:38:29 UTC