Live data from Hacker News

Our experience with the Fediverse, and why we left

infosec-handbook.eu

131–140 of 224 posts

Re: Our experience with the Fediverse, and why we left

#131

Earlier quoted context omitted.

> You need to have a thick skin Actually we need the rest of social media to have this, and then we don't need these alternative platforms. There are simply too many people who have grown up without having any meaningful opposition in their lives - without having someone challenge their ideas and values and making them defend said ideas and values, and they simply do. not. know. how to cope with it.

Why is grinning-and-bearing harrassment by people who want you dead virtuous? “people who have grown up without having any meaningful opposition in their lives” always feels like a dogwhistle to me, because the people saying this tend to have far more privileged backgrounds than the people being harassed.

The entire world has been forced to act as diplomats. When coming from vastly different world views and experiences, being charitable in your interpretation of others is essential; it is important to distinguish disagreement, harassment, and true threat so as to avoid false positives and further degradation of the conversation. That charity requires having a very thick skin, and yes, it’s unfair when it’s not reciprocated and you are being targeted.

I think social media has taught us that most people are terrible diplomats. Which is to expected when a person’s threat response is engaged. Having a thick skinned and measured reaction to threat is still the best way to reduce that threat. And it requires a level of discomfort unprivileged people are generally much better at dealing with; the people who need to hear that advice most are those advantaged enough to be unfamiliar with dealing with discomfort.

I think a better solution than forcing everyone to become diplomatic or banning those who violate the norms of others is to have somewhat siloed social groups that are represented by open minded thick skinned diplomatic types that permeate the borders. That’s part of what’s appealing about a federated model; I think it better mirrors our social tendencies and historically successful political systems with diverse constituents (representative republics seem to be the only proven systems capable of dealing with lots of different peoples long term).

I’m of the opinion that the most virulent partisanship is actually due to the lack of silos rather than the echo chamber narrative. Before the internet, in group conversations stayed behind closed doors. That privacy allowed people who would be outraged at the contents of those conversations to get along in a diplomatic middle.

Now those conversations are public, and people seem to be fighting over control of one big room where all the walls have been removed.

Re: Our experience with the Fediverse, and why we left

#132
post #115

Earlier quoted context omitted.

If you're interested in hosting a discussion based community similar to HN or reddit, I'm working on a project that might interest you. Link in my bio.

Thank you - I'm going to check it out. I also had a look at Lemmy recently which promises better fediverse support in the future. Is there a link to a live example? Didn't see one in the README

Yes, sorry. https://littr.me

However, fair warning, my project doesn't have yet federation enabled. It's on a backburner until I have a better handle on moderation.

Re: Our experience with the Fediverse, and why we left

#133

Earlier quoted context omitted.

The problem with Twitter/"microblogging" isn't just post length. The problem with Twitter/"microblogging" is also lack of hierarchical structure. A BBS has a series of subboards, those subboard have posts and the posts have comments. Sure, things can degenerate to just a series of "mega-threads" but if it's done, everyone the topic and the subtopic and so you can good contextual discussion. Facebook has a three level…

And I guess this is where I go into full old lady "get off my lawn" mode and mention that I still remember when forums used WWWBoard and its clones (anyone remember CyBoard or VIPBoard?) that provided full comment threading. Any comment can be directly replied to and have its own tree of comments. Like... well, like HN, or Reddit. I really thought forums lost something when UBB and its clones (vBulletin, phpBB, etc.)…

I've used both kinds of forums, and I think both trees and linear threads - let's call them 'streams' - have their places.

If you imagine a forum as a large dinner table, trees are like conversations that start out at one corner of the table, maybe with a few people participating, and then usually split off into individual exchanges that don't interact with each other. When that happens late in the dinner after coffee and liquor, people usually move around and form little groups.

Streams are like shared conversations involving the entire table - one person at a time talks, everybody listens and replies. Sometimes people try to talk over each other, sometimes it's mostly two or three people talking and the others are nodding along for a while. But it's what makes the experience a communal one, and it's how you get to know the people in the group other than the few you directly spoke to.

It also acts as a moderating influence, since if two people are getting into a heated debate over some niche issue, other attendees will usually try to mediate for the sake of the event, instead of ignoring them and letting them fight among them.

Stream-based forums IME tended to form more robust communities where people recognized each other's names and avatars, whereas even in smaller subreddits I might recognize a couple of very frequent commenters but nowhere near as easily or as often. On the other side, tree-based forums make it much easier to establish a rapport with the couple of people you wanted to talk to and ignore everybody else.

(Potential objection: nothing's stopping a tree system from acting like a stream by having a "main" thread where most everybody pipes up. In theory that's true, but in practice I find that threads simply don't have the staying power of streams, because they fade off into the 'click here for the next 20 replies' purgatory where only the participants and a few lurkers follow. Streams keep all the eyeballs in the same place.)

Re: Our experience with the Fediverse, and why we left

#134
post #91
post #58

Earlier quoted context omitted.

writefreely has a better UI for reading long form posts and is quite popular among the academic communities on the fediverse. personally I host a gitea server and link to my longer documentation on my federated account. that gives me a bit more freedom to edit the content and easier to reference. matrix servers are also great for hosting federated long form content.

Could you expound on using matrix for long form content? I host a synapse homeserver, and feel like I’m not using it to its full potential.

AFAIK, there is no implementation beyond some proof-of-concepts, but the idea is that Matrix (via bridges) can receive and send activitypub updates and treat them as messages in a room. So you could follow and respond to people on a room and they would receive updates on their ActivityPub server. It

This idea is not new, really. Movim (https://movim.eu) is running a federated social network on top of XMPP for over a decade already.

Re: Our experience with the Fediverse, and why we left

#136
post #99

Earlier quoted context omitted.

At this point, the Usenet servers which took massive amounts of bandwidth and disk space take tiny amounts of bandwidth and disk space (assuming you don't allow binary posts). Maybe it's time for Usenet to come back. - Truly federated - Topic focus instead of people-focus - Killfiles! - Proper threading - Standards-based servers and clients

Usenet over UUCP worked just fine, with UUCP serving up email too on the dial-up batch syncs.

So did FTP over e-mail. The tech evolves. UUENcode sucked, btw. And the NZB-based file aggregation and directories served up were pure trash.

Re: Our experience with the Fediverse, and why we left

#137
post #27

I would argue that what is described in this post is inherent in all social networks. The wonderful thing about the Fediverse is that depending on the node you connect to, or the people you choose to federate with (in the event that you have your own instance) that your experience will be vastly different. It’s given me some of the most enjoyable interactions I’ve ever had online in the last ten years. You need to ha…

The wonderful part is also its Achilles heel. Mastodon is advertised as an alternative to social networks, but since your identity is tied to your node, its much closer to joining a web forum structured like twitter with the possibility (but not guarantee) of interacting with similar forums. From that perspective it's great. When people offer it as an alternative to conventional social media, it comes up massively sh…

> Contrasted with facebook (or a twitter with groups), if you join a group of motorcyclists, there's little to no risk that you'll be excluded from the Scooter group of-which you're already a member because a few bikers got into a spat with scoot-gang, nor will you be excluded from any of the groups that get along well with scoot-gang.

Are you sure? On Reddit, membership of one subreddit often results in bans from others, and Reddit is centralized.

Re: Our experience with the Fediverse, and why we left

#138
post #124

Earlier quoted context omitted.

I wish the Mastodon ad campaigns on Twitter would focus more on the digital sovereignty benefits. It seems like all anyone takes away from federated protocols is "it's more secure" in some ambiguous way. On the Signal topic, I've been put off talking about the security concerns of centralized vs decentralized lately as everyone seems to interpret this as "US X NOT Y".

Reach out to Eugen about that -- afaik he runs the @joinmastodon Twitter account directly or has someone helping him with it, but he's approachable about feedback.

Thanks, I did reply back when I noticed it. They seem to be collecting other people's posts on the topic at the moment.

My main concern is the misconception that federated protocol provide ambiguous "security" that is:

> Safer social media experience https://joinmastodon.org/

There's noting safe or secure inherent to federated social media.

Re: Our experience with the Fediverse, and why we left

#139

Earlier quoted context omitted.

That analogy is a bit too harsh. How about like saying you went to Texas but then only visited Austin?

No, it's not too harsh. A Mastodon instance doesn't even give you access to Diaspora* users.

Diaspora is not part of the fediverse and never has been. Diaspora is federated but has always used their own, separate protocol.

Re: Our experience with the Fediverse, and why we left

#140

There's subtext here, right? Is this related to Gab and the rest? From their earlier post about Fediverse: >Some parties in the Fediverse demand “self-censorship.” Especially when we talk about particular services or products, individuals contact us and demand that we delete our posts. “We shouldn’t talk about the topic,” so other people don’t start to use these “evil” services and products. In our opinion, such dema…

I’m not sure, but even if not I still feel like that’s a silly complaint. Party A says something on the Internet that offends party B. Party B says something on the Internet that offends party A. Party A complains that they’re being asked to self-censor. I see it as both parties using the service as designed to speak their minds. Party A also has the tools to mute Party B if they don’t like what they have to say.

I mean, it's

Party A says something on the Internet that offends party B.

Party B asks party A to self-censor/tells them to shut up, which offends party A.

Party A complains that they’re being asked to self-censor.

When party B is asking A to self-censor, there's nothing wrong with A complaining about what B is saying. If A's lying or being dishonest, oh well.

Post reply on HN