News for hackers. Stuff that matters.
Re:Fediverse.Party – Explore Federated Networks by networkimprov on Sunday May 02, 2021 @12:16AM (#27012306)
Zillions of websites have active discussion boards, despite the success of Reddit and FB Groups.

A handful of webmail providers have centralized a large fraction of all email users. They already have the control you're concerned about.

Non-federated email means you have accounts at several sites, and most sites have membership requirements (customers-only, employees-only, etc). A client app keeps track of all your accounts. A webmail intermediary is unnecessary. The mnm demo gives a sketch of this [1] and the FAQ gives more detail [2].

[1] https://mnmnotmail.org/demo.html

[2] https://mnmnotmail.org/faq.html

Re:Fediverse.Party – Explore Federated Networks by josephg on Sunday May 02, 2021 @07:22AM (#27014227)
If email worked the way those sites do, I'd need a microsoft webmail account to talk to microsoft webmail people. And a gmail account to talk to gmail people. And an apple account to talk to people there. And so on. That would be a much worse experience of email than we have today.

Federation in email is used constantly and ubiquitously. Why would anyone want to turn it off?

Re:Fediverse.Party – Explore Federated Networks by networkimprov on Sunday May 02, 2021 @01:32PM (#27017076)
I don't mean to be impolite, but it seems like you haven't read any of the links I posted.
Re:Fediverse.Party – Explore Federated Networks by shkkmo on Sunday May 02, 2021 @01:54AM (#27012650)
Given that you could easily "unfederate" SMTP/pop3 and have the exact same model, I don't see how exactly the lack of federation will be a selling point.

I see any value in TMTP in the improvements as a protocol and I think it will be only be hurt by having no provision for federation in the protocol.

Re:Fediverse.Party – Explore Federated Networks by networkimprov on Sunday May 02, 2021 @03:18AM (#27013013)
A TMTP server could act as a proxy between a client and service; there are a few use cases for that (mentioned in FAQ, but not in current protocol draft).

I'm not aware of any use cases for store-and-forward federation that aren't better served by a client-server network. And I've been thinking about this around the clock for four years :-)