- cross-posted to:
- main@feddit.de
- cross-posted to:
- main@feddit.de
What is Lemmy?
Lemmy is a self-hosted social link aggregation and discussion platform. It is completely free and open, and not controlled by any company. This means that there is no advertising, tracking, or secret algorithms. Content is organized into communities, so it is easy to subscribe to topics that you are interested in, and ignore others. Voting is used to bring the most interesting items to the top.
Major Changes
A full list of fixes is below, but this patch release includes federation compatibility and bug fixes, as well as fixing vulnerabilities in our websocket rate limiting.
Upgrade notes
Besides the addition of a search rate limit to the lemmy.hjson, there are no config or API changes.
Follow the Docker or Ansible upgrade instructions here.
Support development
We (@dessalines and @nutomic) have been working full-time on Lemmy for almost two years. This is largely thanks to support from NLnet foundation. If you would like to support our efforts, please consider donating.
If you’d like to support development, and make sure that we will always be available to work full time on Lemmy, consider donating to support its development. We’ve spent hundreds of hours on Lemmy, and would like to be able to add more developers to our little open-source co-op as time goes on.
Changes
Lemmy Server
- Federate user account deletion (fixes #1284) (#2199)
- Dont federate initial upvote (#2196)
- Add missing mod log entries for federated actions (fixes #1489) (#2198)
- Make sure application questionaire is required. Fixes #2189
- Fix verify_mod_action check for remote admin actions (#2190)
- Run cargo upgrade (#2176)
- Migrate towards using page.attachment field for url (ref #2144) (#2182)
- Exclude removed/deleted posts from community outbox (#2184)
- Fetch community outbox in parallel (fixes #2180) (#2181)
- Adding a ban expires update job. Fixes #2177
- Add email translations (#2175)
- Add test files for Friendica federation (fixes #2144) (#2167)
- Lowering search rate limit. Fixes #2153 (#2154)
- Rate limit ws joins (#2171)
- Delete unused diesel.toml file (#2166)
- Rate limit websocket joins. (#2165)
- Doing tests in sequential order. Fixes #2158 (#2163)
- Dont log errors when rate limit is hit (fixes #2157) (#2161)
- Fix rate limit check for register. Fixes #2159
- GNU social compatibility (#2100)
- Consolidate and lower reqwest timeouts. Fixes #2150 (#2151)
- Check that config is valid before saving (#2152)
- Dont log error if duplicate activity is received (fixes #2146) (#2148)
- WIP: Email localization (fixes #500) (#2053)
- If viewed actor isnt in db, fetch it from other instance (#2145)
- Show rate limit algorithm. Fixes #2136
- Adjust retry interval for sending activities (#2141)
- Add jerboa link to readme. Fixes #2137
- Forbid remote URLs for avatars/banners (fixes #1618) (#2132)
- Remove docker/prod unused files (fixes #2086) (#2133)
- Rework error handling (fixes #1714) (#2135)
- Dont allow admin to add mod to remote community (#2129)
- Reject federated downvotes if downvotes are disabled (fixes #2124) (#2128)
Lemmy UI
- Dont allow community urls like /c/{id} (fixes #611) (#612)
- Fix loading indicator on search page (fixes #443) (#606)
- Upgrade deps (#604)
- Remove auth token from error message. Fixes #600 (#601)
- Fix error during new site setup (#596)
- Differentiate between mods and admins in mod log (#597)
- Fix comment fedilink (fixes #594) (#595)
Sadly this is how hosting these kinds of services works at the moment. There is no way the devs can change this. If it helps you it’s not actually that hard, like @dessalines@lemmy.ml already said there are many step by step tutorials that will be great introductions into the world of system administration.
Well, I don’t know if that’s really sad, I think people should have a minimum of knowledge to host online services. Doing it while learning system administration from scratch and hoping it will be easy is kind of naive.
I did not read the docs but if it’s not the case maybe some basic knowledge should be listed as requirement along with some links to tutorials?
Unfortunately, most step-by-step tutorials assume knowledge of many basic things, which are not always even mentioned. For example, recently one of the users tried to explain to me that you just need to use the command "docker build -t lemmy-ui. " and etc., but there is a funny problem: I didn’t even understand where (in which environment or in which program) I can use it, and where I can’t. And also what to do after.
And so everything turns into collecting a million needles in a haystack. Of course, I understand that this is an integral part of learning everything related to programming. But often life works in such a way that one person, a professional in his field, can spend 4 hours of his time, saving 400 hours for 100 beginners. At the same time, without such help from a professional, probably 95% of potential active users and novice developers can simply get stuck and abandon their interest.
yes you are 100% correct, sorry. I don’t really know of any system administration tutorials for total beginners. We all learned this organically somehow, how to deal with ssh. We were bloody beginners who did stupid mistakes as well in the past, I used to always break my linux installs :D