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.
On Lemmy 0.19.3, reports go to:
Did the upgrade solve it for you?
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.
Not yet, it’s a known limitation in Lemmy right now
You are correct, this is one of several security issues with the current 2fa implementation.
I started working on an improved version of 2fa for Lemmy last week. Unfortunately, I’ve been very busy for the past few days with some other stuff, but I’m hoping to get a PR up this weekend.
Damn, even $11.99 sounds like a lot - I only pay 12.99€ for a family plan in Europe.
I think it works best if you have a lot of screen real estate. My sweet spot is around 5120x1440p (either ultrawide or two monitors) with about 5 desktops. I never overlap windows and it works amazingly for me.
I used to do this with Gnome, nowadays I use the exact same workflow in Mac OS, and I feel super productive with it. I haven’t used alt tab in about a decade now 😃
For me, it only works with good keyboard shortcuts for the following:
Nice work!
This is already implemented in lemmy 0.18.1 for comments and posts!
The “last seen” column actually shows when the block was lifted!
According to this post:
New community creation disabled
There are already plenty of communities here. New communities can be created on other instances.
Aha, I see where the confusion is. The thing is, the name of a community includes it’s home instance. So !some_community@lemmy.ml is a completely different community than !some_community@lemmy.world, for example. These communities have different mods, potentially different rules, etc.
You should think of it in the same way as e-mail addresses: “[email protected]” and “[email protected]” might have the same name up to the “@” symbol, but most likely they are two completely different people!
As a user, you can of course subscribe to many of these if they all seem alive and interesting, and you can see a combined feed for all your subscribed communities in the “subscribed” section of your front page. Potentially in the future there could also be some kind of grouping functionality, where you can yourself group together related communities for a single feed.
I’m not fully sure what you mean by “without referring to a particular instance of that community on a particular Lemmy instance”. Are you trying to link to a community that will always open on the readers local instance? If so, then the way to do it is like this: [[email protected]](/c/pics@lemmy.ml). Results in: [email protected].
Caveat: this link will only work on instances which have previously had at least one subscriber to the linked community.
I would recommend reconsidering that solution - I’ve already seen some malicious image uploads which Cloudflare has caught. For example:
Maybe you can check which specific rule from the ruleset was being triggered? For me, legit uploads are still working with the default ruleset (as you can see by the screenshot I uploaded in this very comment), so maybe you enabled some extra rules?
Can you elaborate which functions are blocked by the managed rules? I haven’t noticed anything legit being blocked yet, just a bunch of obviously malicious things.
Try enabling the captcha in your instance settings, it might help a bit as well!
I think people will eventually get used to the idea that the name of a community is not just the part before the “@”.
I mean, even regular people have no difficulty understanding that e-mail addresses like [email protected] and [email protected] are two different “identifiers” and, most likely, two completely different people. Given a bit of time, I think there will be a general understanding that “[email protected]” and “[email protected]” are different names
On 0.19.3, you can:
false)