chaospatterns

I use Jellyfin for music mostly and it struggles with metadata. For example, if a song has two artists on it and I edit to correct it, it won't update correctly and I'll edit up with the artist "Artist A; Artist B".

Have you tried a packet capture with Wireshark or tcpdump to see what it's doing? It might give better clues than a general error message.

Yeah, I'm a little disappointed. I was hoping Unifi would do something like release an AP with integrated Thread support so users could benefit from the already pre-positioned APs to then add Thread coverage.

On Windows the system wakes up when connected or disconnected from an AC adapter. On Linux the system will momentarily wake up but immediately go back into suspend.

I get why this could be a source of bugs, but if I unplug my laptop while its asleep why would I want it to turn on?

I'm working on adding ActivityPub to my Hugo blog right now. I support RSS, but I figured AP support means that you can get it into your Mastodon feed or even Lemmy feed making it easy to follow. Additionally, commenting (assuming it doesn't get taken over by spammers.)

Which stops malicious usage, but doesn't stop cases where web pages over use pushState as users move around instead of replaceState. I've seen maps that would add to the history every time a user moves around the map.

Flash isn't dead yet.

I just had to use it to connect to an ancient Siemens building automation system. Luckily we're replacing it this year.

I'm on Wayland and KDE/Plasma. It worked on GNOME, but sadly not on Plasma.

Not all filtering is the same. Client side filtering requires more data to passed over the network that then just gets dropped. It also means rules that are not shared across devices.

Most importantly, these use CSS filters which are computationally more expensive because it has to take an entire DOM element, serialize it to text, string search it vs a server side filter that can just look at a one or two field variables. Even if it's not filtered in SQL on Lemmy's side I'd say it's still more efficient overall.

You do what you want, but adding extra work on the client side is not what I'd want for my users. Of course, if your Lemmy instance does not supporting filtering, then this is moot.

And it'll be faster and more efficient to do it server side as opposed to making uBlock Origin handle it.

How many users are using browsers that are old enough they don't even support JS? It's one thing to disable it for security/privacy (which the OP was talking about), because those users are probably more tech savy.

Do these old browsers not support DuckDuckGo?