Show newer

@customdesigned Whilst this is all technically correct and useful, I think a bigger factor is going to be the front end for non-technical users. And that includes brands that want to have a presence and add that mode into their marketing campaigns. Lastly, sometimes a single user with high profile can bring an audience with them and dominate a particular platform, whilst remaining an average presence on others.

@derek Heh. In my case it actually is (use a BATMAN layer 2 mesh for local LAN).

@orcmid There is nothing wrong with HTTP - it just doesn't scale. Your Dell server in your office is not going to support a million people viewing your site.

There is nothing wrong with TLS - it just that a secret cabal decides what CAs are included by default in popular browsers - wielding an effective power to cancel.

There is nother wrong with DNS are originally conceived - it has just been centralized because companies were mad that using a new "cool" TLD wasn't resolved by all users (depending on the sysadmin for their DNS resolver). There were the original ARPA TLD list, and ISO country codes that everyone agreed on. (With some disputes over nations out of favor - e.g. Kurds today banned by ICANN.) But using .COM for your company was BORING.

But mainly, ICANN was sold to sysadmins as a convenience - no more following mailing lists and keeping nameservers updated for the TLDs you support. ICANN does all that work for you! All they ask in return is world domination.

There are attempts to provide a successor to HTTP that scales. E.g. IPFS, DAT, and other content addressable schemes. Note that CDN providers work similarly to IPFS, and their business model continues to hold if IPFS gets widespread adoption. (Pay us to ensure your content is cached close to your customers - instead of relying on amateurs who may or may not be reinstalling their server at the moment or turning their desktop off.)

@davoloid Agreed. And that is a big weakness of SSB - it doesn't have the selection of robust clients like Matrix does.

@derek How do mesh networks come into it? None of the protocols I mentioned have anything to do with layer3. A Mastodon server would have no idea whether there was a mesh somewhere supporting it.

@Maximus I found what toot you were replying to - but it still isn't clear what "it" is referring to in "No but it's better".

@Maximus How do you see what a toot is in reply to on mastodon?

@Marvin You have to talk about a specific client for that criticism. It works great for me. I mostly use self-hosted element web. None of the people I talk to have any issues. There was some confusion with FluffyChat, but quickly adapted to.

@Maximus It wasn't clear what features it added over and above Matrix protocol.

@derek Makes sense. The beauty of SSB (and usenet) is that such distribution is distributed and built in. But then you don't have a direct follower count.

@orcmid A long term goal is get EVERYONE to run their own DNS resolver. Or at least use a trusted geek's resolver. Like everyone did before using ICANN became widespread. DNS is *supposed* to be federated. Using ISP resolvers is a huge problem, even if you aren't concerned about centralization.

If that were accomplished, then it would be easier to convince people to add just your TLD - it wouldn't interfere with anything else (except someone else's TLD with the same name - in which case they have to choose).

@orcmid HTTP doesn't scale - without applying abominations like Content Distribution Networks - which greatly diminish confidence in authentication (private keys distributed to CDN servers).

Further, HTTPS authentication for Joe Sixpack is accomplished by using the TLS cabal - which can cancel you at a whim (and has done so). ICANN can also cancel domains at whim (part of the agreement for official TLDs).

Yes, you can run your own CA, your own TLD, and this works very nicely, and we have done it for a private Matrix homeserver. But unless you know Joe personally, he is not going to be installing your CA and DNS resolver for his browser.

@derek Hardware for who? The server with the account of the content provider? Or the servers of all the followers? (That is the problem with Matrix and many room members.)

Having not hosted activityPub servers, I don't know the limitations. Could a Mastodon account potentially be followed by millions? Could they be counted?

Show thread

I am trying to work out the strengths and weaknesses of messaging platforms from fully decentralized to federated to centralized. I am only a user on Mastodon/activitypub and IRC, but I have in the past hosted usenet and currently host:

smtp (email)
XMPP
Matrix
SSB (Secure ScuttleButt)
SIP (fully decentralized)

The impressive feature of twitter and it's totalitarian centralized ilk is that a single id can have millions of followers - and know that. SSB supports unlimited secure (signed) broadcasting, but there is no mechanism for knowing how many followers there are. Of course, TV was in the same boat, and you could get an estimate by polling. BBC broadcasts on SSB.

Counting followers is essential for monetizing content via advertising and sponsors in a decentralized manner - i.e. not subject to cancellation at a whim by a global centralized platform.

Matrix seems ideal for many of the purposes people use Teams or Substack or Slack. Private conversations e2e encrypted, logging with controlled retention (HIPPA compliant), voice and video calls, voice and video conferencing, media. But performance of small personal servers drops with number of participants in a room - I don't think it can support a million followers.

XMPP has inconsistent state for multiple devices, and is terrible at group chats. I do use it a backup for matrix and for voice/video calls. Open XMPP clients supporting VOIP and IPv6 are easier to find than SIP clients. (And SIP is even worse at state for multiple devices.)

Usenet has no authentication (not worth tacking on GPG header schemes).

Email is not designed to be "instant" (as in IM), but can be coaxed into resembling that by clients such as DeltaChat.

Ok, so now I should make a feature matrix (which includes Matrix), but have I missed any open and federated/decentralized protocols? Any other features? Current feature list:

broadcast (million+ followers)
follower count
p2p voice/video
e2e encryption
authentication
federated
decentralized (or federated that can be practically fully decentralized, like SMTP)

Did I miss any?

On Timcast (Rumble/Youtube), twice a panelist has stated "no point in using mastodon and activitypub because mastodon.org can cancel you anytime they want.

This seems like they missed the whole of federation. I traced packets while logging into qoto.org - and didn't spot anything from my network touching mastodon.org.

But maybe qoto.org and and other servers delegate to mastodon.org for login? I can' think of a good reason for that - but before I go on a rant I'm asking if there is any basis to the rumor.

Obviously, if you (foolishly) make your mastodon account on mastodon.org - the operators can cancel you (as they should be able to). I don't think people - even talk show hosts - understand what federation is.

Fact check: The scientific name for capybara comes from Hydro chaeris, which means "water hog" in Greek. :chadybara:
Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.