gotosocial VS Mastodon

Honestly if a server allows free login, then it shouldn't matter how the donations are spent, the admins are probably at a loss anyway. I've seen large phpBB forums run on donations for a long time, so maybe federated socials can work too. One unfortunate thing I've noticed from running a single-user GoToSocial instance is that it consumes a lot of storage, I'm getting 8Gb just from myself and the instances I follow. This could be brought down with more agressive cache settings, but it still shows that people using these new social media still have habits from Twitter or Reddit, where bandwidth and storage is paid for by advertisers, and don't realize how many gigabytes they're casually moving around. I really hope this won't be the downfall of the Fediverse.

I'll be starting my own instance of the fediverse, something for myself and family only. I'll start with gotosocial, and add a reddit like alternative too, but haven't decided between kbin or lemmy yet. Maybe I'll add pixelfed down the line.

gotosocial is easy to install and easy to use, but you need 3rd party apps on your phone or computers to use it properly. Another option is snac2, you need to compile it manually but it is easy to use once compiled. Its web interface is kinda outdated, but it is usable as it is. Both are very light on resources, and can be installed on $4 vps.

[2] https://github.com/superseriousbusiness/gotosocial

GotoSocial would be another option (also in Go with SQLite backend.) Although you'll need a front-end because it doesn't ship with one.

https://github.com/superseriousbusiness/gotosocial

Not sure if you only want Mastodon. If not, I am running https://github.com/superseriousbusiness/gotosocial on a CPX11 Hetzner instance which costs 5.18 euros/month. Am hosting a few other things, but CX11 instance for 4.51 euros/month will also do well.

The main one is how they handle keys[1] which broke federation with Pleroma for a while. There's also some weirdness with their HTTP signing which breaks Honk follow requests but I'm still tracking that down.

[1] https://github.com/superseriousbusiness/gotosocial/issues/11...

Compare mastodon, pleroma, misskey, friendica, gotosocial, pixelfed, peertube (https://github.com/superseriousbusiness/gotosocial) and their main forks.

As u/riffic mentioned, Mastodon is quite heavy. But since mastodon follows (mostly) standard protocols, you can host an alternative. I’m really interested in Gotosocial, which is written in Go so it can run on a cheaper VPS. But it doesn’t seem to support all features (which will be a common thing with alternatives).

Interestingly there is some discussion for Mastodon with people asking the limit to be smaller, which raises the question as to the purpose of alt text, and how to properly handle larger text lengths in screen reader programs.

https://github.com/mastodon/mastodon/issues/12268

Through the Fast Forward program, we give free services and support to open source projects and the nonprofits that support them. We support many of the world’s top programming languages (like Python, Rust, Ruby, and the wonderful Scratch), foundational technologies (cURL, the Linux kernel, Kubernetes, OpenStreetMap), and projects that make the internet better and more fun for everyone (Inkscape, Mastodon, Electronic Frontier Foundation, Terms of Service; Didn’t Read).

Mastodon DMs have absolutely no privacy: https://github.com/mastodon/mastodon/issues/18079

For a decentralized protocol doing things right is much more important than doing things fast, it is very difficult (and in a lot of cases impossible) to break backwards compatibility.

Postmortem on what happened here: https://news.ycombinator.com/edit?id=39305884

The v1 API of Mastodon limits the size of the tree that it will expand for users who are not logged into the server: https://github.com/mastodon/mastodon/blob/main/app/controllers/api/v1/statuses_controller.rb . I am guessing that this or some similar limit applies to threads being returned to unauthenticated users of the web UI. It just arbitrarily stops expanding the replies at some point, including the main thread from the OP.

If a thread is truncated, users expect it to expand automatically and autoscroll when you hit the bottom. In my desktop browser, that does not occur, and there is no indication that there is more to see. This is the situation of the web interface as of Mastodon version 4.2.5.

The issue is very sensitive to observer conditions. If you are logged into the server, the behavior is different. If you use a Mastodon app instead of the web, the behavior might be different. As the tree expands, the cutoffs become different. If you look at the thread on a different Mastodon server, the tree is different because every server has its own view of the Fediverse.

HN needs a best practice for linking to Mastodon threads in a way that provides a consistent experience to HN readers. The average Mastodon server would be crushed by hundreds of HN readers grabbing the entirety of a huge thread all at once, so this might involve some thread-unroll-and-cache service. I tried https://mastoreader.io/ but it did not solve the problem.

Alternately, we push changes into the Mastodon web UI to warn users when they need to click to see more and assume that people will get used to the navigation.

Suggestions?

Fixed in Mastodon v4.2.5 https://github.com/mastodon/mastodon/releases/tag/v4.2.5

>You can defeat the Affero clause by putting the software behind a proxy, for example

Could someone elaborate on this? This is NOT my understanding of the license, and it seems absurd considering e.g. Mastodon is AGPL but the standard install requires a reverse proxy[1]. If using a proxy defeats Affero, why would the Mastodon team do this? Are they stupid?

[1] https://github.com/mastodon/mastodon/blob/main/dist/nginx.co...

Mastodon is free and open-source. Go ahead and add the flag:

https://github.com/mastodon/mastodon/blob/main/CONTRIBUTING....

Didn't say anything about freedom of speech. And again: I'm not the one to talk to. I don't have any strong feelings on the topic, but if you do, you should take it somewhere that people who can do something about it will see.

I tried to find an existing discussion to help get you started, but couldn't. You can start one here: https://github.com/mastodon/mastodon/issues

It's easy to sit here on Hacker News and say "they should just..."

Coming up with a standard for an international project will be a long, noisy discussion. You'll tread on internecine conflicts you had no idea about. Old wounds from past related discussions will come out. People will soapbox.

This is why I have no interest in discussing it. It probably won't go anywhere in a place where it actually could. It definitely won't here.