But that's exactly the difference in a nutshell. Centralized social networks naturally gravitate towards massive celebrity accounts. Federated servers tend to gravitate towards communities. It *is* smaller, by design. I have 1/25th the followers I had on Twitter yet the engagement is far higher (and much better) so from my point of view, it's not a loss)
Great explanation, couldn't have done any better, i can see more FAQ pages coming about how to find specific people.
@mykd @blaine That's perfectly fine, but what they want, is by definition a centralized platform with all of humanity on it (and all the risks that come with that kind of power)
But there is a middle ground. All of your family members can email to each other. Of course this is NOT the same, it's a compromise. If you each join whatever server works for you, you can STILL find each other and see each others content.
@dekkzz78 @scottjenson @blaine
A million people have joined Mastodon in the last two weeks. Eternal September is a warning to you, not to them.
@dekkzz78 @scottjenson @blaine
I never mentioned attention spans.
Mastodon is pretty close to Twitter of say ten years ago. That was good enough to keep people engaged once they joined.
"They’re just going to join a general or place-based instance. They’ll then look for friends and family and their preferred big accounts in news, entertainment, sports etc."
Twitterati need to do at bit of research to get the best of the #Fediverse. The above quote suggest your saying if it's not in their face they wont hang around.
No, it’s saying they’ll just switch server if they accidentally end up on one that’s too opinionated. Probably though they’ll just join a top ten server, and never even have to think about the technology.
Yeah, but Gab was clear-cut. What should the position be about an instance that allows police officers to join it? There are admins out there who will block that server. Journalists? Ditto. Politicians? Very probably. Etc etc.
Without more nuanced control mechanisms being available, there’s a risk of a chasm developing between ever-larger “reasonable free speech” instances and tightly curated “safety first” instances. And what will that do to the fediverse?
We’re talking about accounts being banned though, not the current lack of recommendation algorithms. I really see no value in telling my mum “Sorry mum, you can’t see Stephen Fry’s toots because your admin doesn’t want you to. It’s for your own good.” I’d just set her up on mastodon.social and never even say the word “fediverse”.
@mykd @blaine Be the instance admin you want to see in the world! Create a small host for your extended family, talk with them about some ground rules, block or don't whatever celebrity they want to follow, keep instances that suck blocked. If they start at other instances, teach them to migrate to yours.
Be proactive, take matters in your hand?
@BadgerGirl @blaine
I 100% agree and support this strength of the federated network.
My concern is that as more and more people join the fediverse, maintaining the safety and peace of such spaces will mean having to block an increasingly large numbers of accounts.
Unless there are powerful, flexible, targeted tools and processes to support doing so, your mods may just end up saying “screw it we’re defederating from all mastodon.* servers.” All we would all have lost.
@BadgerGirl @blaine
Yes, technical solutions will need to be able to do a lot more at the interfaces between instances esp with a greater variety of tool as you and Blaine have mentioned.
I agree that still leaves space for bad actors to subvert each community. We know that the more isolated a group is, the greater the likelihood that its beliefs and norms drift away from those of other groups. Bad actors can weaponise that. The more connected we stay, the harder that gets.
@blaine A slight problem with federated micro-Twitters versus fully decentralized IndieWeb setups in a way.
Mastodon instances amplify their users in a different way to actual independent web pages / the IndieWeb.
But still, yeah, you’re right. I’m just sad that eg the WebFinger setup ended up a lot less static site friendly than the original and is much more catered to micro-Twitters than to actually independent sites.
@voxpelli ❤️
For me, the webfinger stuff was/is just an idea - how can we give people an online name that they control?
(There's some new thinking in this direction that is very exciting, and I think better than any of our previous approaches!)
@blaine Yeah, I remember WebFinger itself never really being intended to be a spec in itself, rather just a pattern for how to apply Host Meta rules to usernames
Which new thinking are you referring to? IndieWeb ones? Crypto ones? Browser based ones?
Please also note that webfinger is not part of any ActivityPub spec.
https://www.w3.org/TR/activitypub/#conformance
It is just a masto thing.
But the fediverse is so many wonderful softwares.
@sl007 @voxpelli the http spec also doesn't have anything to say about html, nor does webfinger say anything about ActivityPub, as it should be. Webfinger isn't "just a masto" thing, either - any social software will need to use the pattern if adoption and sharing is a concern.
It's perhaps best to think of webfinger as "DNS for people"
@blaine “It's perhaps best to think of webfinger as "DNS for people"”
I see it as more like DNS for resources (as in the R in URL). That could, of course, be a person but more usually it'll be a person's account. Webfinger acct:[email protected] returns different data from acct:[email protected].
@edavies @sl007 @voxpelli yup! I don't think of the two as oppositional, since people have multiple identities, depending on context.
But yeah, webfinger is also a useful construct to talk about things or anything where the underlying handler might change (different server, same name) but registering a domain or setting up a subdomain isn't easy. So, strictly not people, but I've always used that as a way to simplify the concept. ☺️
“any social software will need to use the pattern if adoption and sharing is a concern.”
I mean, the fediverse consists of many softwares.
Just see our Conferences
https://sebastianlasse.de/#home
And those who do only implement ActivityPub and no webfinger is superfine too.
I do not see any advantage.
Yes. Maybe.
Just hoped there would be arguments to use it.
Quite interesting when former twitter people tell the fediverse what it needs.
I did not say that webfinger is bad.
What I am saying is:
New implementors look at the official ActivityPub spec.
An implementor can be any human being in this world, even marginalized or disabled or even an anticapitalist working remote (crazy, I know).
This why I want that every kid can implement it !!!
They do not know that they need webfinger for implementation x but butter cream cookies for implementation y …
They just want to use it and interoperate. That worked all the time. Also without webfinger.
The problem is that webfinger is not part of the spec.
That's it.
If you believe it should be, this is what the Fediverse Enhacement Proposal Process (FEP) was made for or if it should be an official extension, the group can vote.
Just want to understand.
“I've been having this debate with technologists” - I am journalist and artist, sorry.
@sl007 I appreciate that, thanks.
For context: I wasn't just a Twitter employee, I created much of it but have been written out of the history because I am an anti-capitalist. I both tried to make twitter decentralized, creating the first fedi-instance with @ralphm and, when I was forced out of Twitter, was very involved in designing the protocols that became ActivityPub a decade later (thanks to the work of *many* people who came after).
@blaine @sl007 +1, the web consists of URL:s and hyperlinks. Hyperlinks links together two URL:s and can specify a relation from one to another.
None of URL, Hypertext Markup Languages or Hypertext Transfer Protocols needs to know the semantics of a relation and that relation can be specified independently of them and by a user be composed into a new creation.
Relevant spec: https://www.rfc-editor.org/rfc/rfc8288.html
We eg. did that at Flattr. We used rel-payment.