Wine developers. Yes, Valve/Proton has given it a big boost in the last few years but the Wine project has been under steady development for 30 years, almost as long as Linux itself. I remember trying it for the first time back in the day and being amazed that it could run Minesweeper.
Some kind of federation for hashtag follows is what I'd like to see the most. Currently I am using a larger instance mainly to get a good chunk of the traffic for the hashtags that I am interested in. The ability to filter content for user follows would help in this area too. I want to be able to follow a user but only see their posts with specific hashtags.
Oh, and markdown support! Really miss having a proper way to do lists, literals and code blocks.
Personally I am comfortable with that as long as there is a public git repo. An issue tracker is the one thing I'd miss the most. I think how well this goes down will greatly depend on the project's target audience. notmuch is a project that I follow closely and very occasionally contribute to that works this way.
My favorite way to handle RSS is rss2email. This will be exactly as good as your email workflow. Been using this for many years, I have about 16K RSS feed items under my "rss" tag in notmuch
Already moved in the sense that I am not creating any new projects on GH. I am rehosting old projects opportunistically. No plans to get rid of the account unless GH does something really messed up.
The linked post has some analysis of Reddit's loss off traffic based on SubredditStats data. I noticed the same trends when I was looking earlier but some of the drop-offs look so dire that it made me think that maybe the data collection broke. Any idea how they get their data?
Most of the discussion is spoiler free with a few minutes of spoilers at the end after a warning. The spoilery portion is optional, the spoiler-free discussion stands on its own.
Antennapod's implementation of this is so nice. My Antennopod DB dumps have survived 5 years, multiple device transitions and almost 1500 hours of podcast listening.
Some other apps that I use that do a good job at dumbing/restoring their data:
Fedilab: client for Mastodon and some other fediverse instance types.
Keymapper: remap physical buttons and keyboard keys
Newpipe: video and music player for youtube and some other services
Much of the post is the author reminiscing about how the community has changed over time, the author's Steam library, whether we need to dual boot and how great KDE is. After scrubbing through it I have no idea what makes the distribution special and why I'd want to pick it over other options.
mastodon.el is great if you are an Emacs user, works very well and you have all the usual Emacs conveniences on hand.
For Lemmy so far I am sticking with the default web UI and Jerboa. Tried some other alternatives but I keep coming back to these.
In the default Mastodon web UI you can simply click on a hashtag and then press the "Follow hashtag" button. If you want to follow a hashtag that's not showing up in your feed yet then you can search for it and then click on it in the search results. If you don't see the "follow hashtag" button that might mean that your instance is running a very old version of Mastodon. Hashtag follows were added in version 4.0 which came out at the end of last year.
One caveat is that hashtags follows only show posts that "make it" to your instance either because they were created locally or because another user on your instances followed the person who posted them. In practice being on an instance with a sizable user base or an instance that's oriented towards your interests should work well.
I think the reason you are getting downvoted is that Go is not at all like your characterization of Java and .NET. In fact Go was developed as a reaction to some of those problems and it's very well suited for developing things like CLI programs on Linux. Can you imagine tools like fzf, restic or rclone written in Java?
Also, in many ways Go is arguably closer to the spirit of C (despite the GC). A small, pragmatic language that you can keep in your head, little magic, the code does what it says. Rust is more akin to the C++ kitchen sink approach. Neither is inherently better than the other though and I am glad that we have several decent options with different trade-offs for different use cases.
I'd really like to see some client-API consolidation. A common client API that could efficiently handle both "microblog" style and threaded discussions (lemmy etc) and leave the door open for other discussion formats too. This would allow for clients/frontends to flourish even more and backends could compete on features and efficiency. The backend specific features could be expressed through an extension mechanism of the common API.
Go with the frontend kept as simple as possible.