Interesting project! Can you explain the vision a bit more - I understand that every instance can have their own version of an article, but how would a user know which version of an article is most relevant to them to read (and maybe even contribute to)?
Sorry if you were just making a joke, my sarcasm detector is not really working anymore (/s at the end would help). But if not, this comment really perfectly captures the entitlement in open source.
Now imagine you spend months (or even years) of your free time to build something for people to use freely, and the result is that you get endless comments from random strangers, telling you that you work for them and that you need to respect and be grateful to them. I honestly am impressed that open source still exists at all at this point.
I just want to add a counter-point to the argument that Lemmy devs are somehow opposed to contributions. In my experience, there has been no resistance to contributing any type of change (I have personally added niche features for running Lemmy in a distributed manner, optimizations, bug fixes, etc). In fact I would claim the complete opposite - I have received plenty of support and good code reviews from maintainers whenever I have wanted to contribute anything.
I think there is truth to the claim that Lemmy maintainers don’t have a lot of patience for people making demands and snarky comments, but that is very different from being opposed to contributions. Also, after running a big instance for a while now, I completely understand this lack of patience - when some of your users just keep being rude to you, it wears down your patience. It’s easy to patiently and kindly respond to the first 100 rude users, but at some point after that, it just becomes gradually more mentally exhausting, to the point where it’s basically impossible.
Even the example provided in the blog post: I don’t think snowe had bad intentions, but I do think they had clearly misinterpreted the situation with that issue, and their comments were needlessly condescending.
Important note, this feature is only available for US customers.
Good luck with the update! One great thing about 0.19 is that it allows users to check federation status between instances, will be awesome to get that for lemmy.world as well.
Nowadays it’s allowed only for users with >4 week old accounts. It’s not perfect, but having this barrier to entry will hopefully prevent at least some problems.
I think the OP is talking about Lemmy having both a content preview and a text area for link posts.
Some users tend to write their own summary in the text area, so when opening up a post, the result will be:
I agree that this is a bit clunky in terms of UX
What exactly is the issue with our admins? If you feel you’ve received some unjustified moderation, feel free to contact me and I can have a look.
I’m sorry for your experience and I hope you’re doing better now. It’s very important to note that the major victims in this “attack” are absolutely the abused children. That’s exactly what makes this the most disgusting attack on Lemmy to date.
Cloudflare CSAM protection is not available outside of the US, unfortunately.
As a test, I ran this on a very early backup of lemm.ee images from when we had very little federation and very little uploads, and unfortunately it is finding a whole bunch of false positives. Just some examples it flagged as CSAM:
Do you think the parameters of the script should be tuned? I’m happy to test it further on my backup, as I am reasonably certain that it doesn’t contain any actual CSAM
Any thoughts about using this as a middleware between nginx and Lemmy for all image uploads?
Edit: I guess that wouldn’t work for external images - unless it also ran for all outgoing requests from pict-rs… I think the easiest way to integrate this with pict-rs would be through some upstream changes that would allow pict-rs itself to call this code on every image.
Damn, even $11.99 sounds like a lot - I only pay 12.99€ for a family plan in Europe.
Is there a “lost lemmings” community yet? 😄
But do police departments etc really even need to be on social media?
The problem is that if you have two communities with exactly the same purpose, then that will encourage people to duplicate posts to both. This splits up discussions into two separate comment threads. Also, merging these communities at the client end will cause you to see any duplicated posts twice 😅
Yeah, kind of a strange choice to split like that. Are they intending to start crossposting to both communities?
Nice work!
This is already implemented in lemmy 0.18.1 for comments and posts!
If I have several backends that more or less depend on each other anyway (for example: Lemmy + pict-rs), then I will create separate databases for them within a single postgres - reason being, if something bad happens to the database for one of them, then it affects the other one as well anyway, so there isn’t much to gain from isolating the databases.
Conversely, for completely unrelated services, I will always set up separate postgres instances, for full isolation.