You're referring to using only fedi-safety instead of pictrs-safety, as was mentioned in §"For other fediverse software admins", here, right?
Kalcifer
joined 1 year ago
There is already a PR about fixing the low contrast: https://github.com/openstreetmap/openstreetmap-website/pull/5325
That's great news! The dimmed tiles do feel like a bit of a cop-out 😜
One thing you’ll learn quickly is that Lemmy is version 0 for a reason.
Fair warning 😆
One problem with a big list is that different instances have different ideas over what is acceptable.
Yeah, that would be where being able to choose from any number of lists, or to freely create one comes in handy.
create from it each day or so yo run on the images since it was last destroyed.
Unfortunately, for this usecase, the GPU needs to be accessible in real time; there is a 10 second window when an image is posted for it to be processed [1].
References
- "I just developed and deployed the first real-time protection for lemmy against CSAM!". @db0@lemmy.dbzer0.com. !div0@lemmy.dbzer0.com. Divisions by zero. Published: 2023-09-20T08:38:09Z. Accessed: 2024-11-12T01:28Z. https://lemmy.dbzer0.com/post/4500908.
- §"For lemmy admins:"
[...]
- fedi-safety must run on a system with GPU. The reason for this is that lemmy provides just a 10-seconds grace period for each upload before it times out the upload regardless of the results. [1]
[...]
- §"For lemmy admins:"
Probably the best option would be to have a snapshot
Could you point me towards some documentation so that I can look into exactly what you mean by this? I'm not sure I understand the exact procedure that you are describing.
[...] if you’re going to run an instance and aren’t already on Matrix, make an account. It’s how instance admins tend to keep in contact with each other.
This is good advice.
Fediseer provides a web of trust. An instance receives a guarantee from another instance. That instance then guarantees another instance. It creates a web of trust starting from some known good instances. Then if you wish you can choose to have your lemmy instance only federate with instances that have been guaranteed by another instance. Spam instances can’t guarantee each other, because they need an instance that is already part of the web to guarantee them, and instances won’t do that because they risk their own place in the web if they falsely guarantee another instances (say, if one instance keeps guaranteeing new instances that turn out to be spam, they will quickly lose their own guarantee).
How would one get a new instance approved by Fediseer?
There is a chat room where instance admins share details of spam accounts, and it’s about the best we have for Lemmy at the moment (it works quite well, really, because everyone can be instantly notified but also make their own decisions about who to ban or if something is spam or allowed on their instance - because it’s pretty common that things are not black and white).
Yeah I think I'm more on the side of this, now. The chat is a decent, and workable solution. It's definitely a lot more hands-on/manual, but I think it's a solid middle ground solution, for the time being.
If you ban a user [...], then if you are automating this you end up with the issue of if anyone screws up then how do you get someone’s account unbanned on all those instances?
The idea would be that if they are automatically banned, then the removal of the user from the list would then cause them to be automatically unbanned. That being said, you did also state:
If you ban a user and opt to remove all their content (which you should, with spam)
How do you get all their content restored
To which I say that I hadn't considered that the content would be deleted 😜. I was assuming that the user would only be blocked, but their content would still be physically on the server — it would just be effectively invisible.
how do you trust all these people to never, ever, ever get it wrong?
The naively simple idea was that the banned user could open an appeal to get their name removed from the blocklist. Also, keep in mind that the community's trust in the blocklist is predicated on the blocklist being accurate.
127
Vultr doesn't let you pay with crypto until you've already set up payment using a credit card or PayPal
(sh.itjust.works)
Gotta get that KYC!
140
TIL that recipes are not protected by copyright law in the USA (and likely Canada)
(sh.itjust.works)
37
[SOLVED] Have you ever experienced stuttering in a game if you receive a message in a desktop messaging app during gameplay?
(sh.itjust.works)
Solution
This is a bug in KDE Plasma [1.1][2]. It appears that it might be fixed in KDE Plasma v6.2 [1.2][3].
Original Post
I have noticed this behavior with Element and Signal while playing Deadlock. The game will have a pretty severe stutter, ie the frame-rate will substantially dip, for half a second or so at the exact moment that a message is received. It seems to happen with every message. Do note that these are only messages that would result in a system notification. All other messages that are silent, ie they have no pop-up notification, do not result in any stutter.
- OS: Arch Linux, Kernel: v6.6.49-1-lts
- DE: KDE Plasma v6.1.4
- WM: Wayland
- CPU: Intel Core i5-4690k
- GPU: AMD Radeon RX 6600
Updates
- I have tried disabling this setting in Deadlock:
- I have tried windowed-borderless
- I have noticed that the moment that the stutter occurs, my CPU spikes maybe 20% and my GPU drops to 0%.
References
- @narc0tic_bird@lemm.ee. "Have you ever experienced stuttering in a game if you receive a message in a desktop messaging app during gameplay?". sh.itjust.works. Lemmy. Published: 2024-09-09T23:12:24Z. Accessed: 2024-09-10T00:03Z. https://sh.itjust.works/comment/13818926. https://lemm.ee/comment/14674507.
-
it’s a bug in KDE Plasma
-
[the bug] might be fixed [in KDE Plasma] 6.2
-
- "Bug 487780: Fullscreen game stutter when Plasma receives notifications.". Robert. bugs.kde.org. Published: 2024-05-30T03:58Z. Accessed: 2024-09-10T00:06Z. https://bugs.kde.org/show_bug.cgi?id=487780.
- Zamundaaa. "Bug 487780: Fullscreen game stutter when Plasma receives notifications.". bugs.kde.org. Published: 2024-08-19T12:01:08Z. Accessed: 2024-09-10T00:13Z. https://bugs.kde.org/show_bug.cgi?id=487780#c13.
There are some remaining code paths that can block direct scanout - namely effects that haven't been fixed, or that may need to block direct scanout in some situations. There's a new API in 6.2 that effects can use though, https://invent.kde.org/plasma/kwin/-/merge_requests/6203, which blocks direct scanout only when really necessary. It's implemented for all built in effects, and external javascript effects automatically make use of this API too.
62
20
[META] Current moderator actions occurring in this community are not visible in the modlog
(sh.itjust.works)
In one of my posts, I noticed this removed comment:
I was curious what it was, so I checked the modlog, but it states that the last mod action in this community occurred a month ago:
What's up with this? Are mod actions being scrubbed from the modlog?
view more: next ›
Yeah, that was poor wording on my part — what I mean to say is that there would be unvetted data flowing into my local network and being processed on a local machine. It may be overparanoia, but that feels like a privacy risk.