As an aside, distro doesn’t matter but should make sure realtime is set up properly for the optimal latency. That usually requires the linux-rt kernel. The default one isn’t quite as bad as it used to be, but linux-rt will be able to guarantee low latency processing without dropouts. Also worth tuning/hardcoding latencies in JACK or PipeWire if the audio delay is too big out of the box.
At this point there should probably be a generic “just ask random questions for other Lemmy users” community to direct those people to. People don’t seem to get that this one is similar to AskReddit in purpose, but Lemmy is small so there’s no immediately obvious general communities.
Similarly, the high availability of source code may lead to malicious instances, actors, and/or back-end modifications that would favor specific instances resounding consequence throughout the Fediverse.
That’s ultimately just the Internet being the Internet.
On the fediverse, any instance shouldn’t blindly trust any other instance for that exact reason. That’s part of the game. Instances share the data over ActivityPub, and it’s up to you to process and make use of that data. That includes spam filtering and whatnot. Some instances have CSAM detection for example.
Every instance that’s subscribed to a user or community gets the full set of data: every vote, from every user, from every instance involved. We have the data, we can analyze it. And that’s what really matters.
It doesn’t matter if there’s rogue instances trying to manipulate votes. Everyone have the data to detect and filter out the noise. Maybe one day it’ll be like E-Mail where the majority of the traffic is spam. But just like E-Mail, we’ll make filters and make it work. If all else fails, there’s always the allowlist method: only see content from sources you trust not be spammy. You can even run AI models on it to filter the data if you want. You have the data, you can do whatever you want with it to make it useful for you.
I have faith in the protocol and its openness, not the software that runs it.
It doesn’t seem to have any outrageously complicated dependencies to work, just C++, Boost and a few other recognizable names, at least at a glance. They also seemingly have an ArchLinux package, which means it’s likely to at least be buildable on latest everything. Mint will fall in between, so the odds it’ll compile are pretty good.
I think 0.19 is reverting that behaviour, because it was indeed a certified bad idea.
I think the idea was to attempt to bulletproof potentially crappy clients especially after the XSS incident, but the problem is it’s simply not even always rendered in a web context which makes the processing kind of a pain.
Wouldn’t surprise me if it becomes double and triple encoded too at times because of the federation. Do you encode again or trust that the remote sent you urlencoded data already?
Best format is the original format and transform as late as possible, ideally in clients where there’s awareness of what characters are special. It is in web, not so much in an Android or terminal app.
I don’t think the Lemmy devs are particularly experienced web developers in general. There’s been a fair amount of dubious API design decisions like passing auth as a GET parameter… Thankfully they also fixed that one in 0.19.
It indeed doesn’t, its purpose is to show the differences and clarify why/where OP might have heard you need special care for portable installs on USB sticks.
All the guides and tutorials out there are overwhelmingly written with regular USB sticks in mind and not M.2 enclosures over USB. So they’ll tell you to put as much stuff on tmpfs as possible and avoid all unnecessary reads and writes.
The only reason it will not work would be if OP has manually configured stuff in /etc/X11 in some way. You can even have both in the system at the same time (which does require a little bit of extra configuration). Absolute worst case you check out /var/log/Xorg.0.log it tells you the config you forgot in /etc/X11/xorg.conf.d/20-nvidia.conf 5 years ago doesn’t work because the GPU is gone, you delete it, restart Xorg and you’re good to go.
Even on Windows it’s kind of a myth. Some people are like you need to DDU the old driver in safe mode before swapping them out. You can really have them both installed it’s just going to be weird because on Windows both vendors come with ridiculous amounts of bloat.
AMD cards just works as long as your distro is reasonably up to date. No extra drivers, in fact, installing AMDGPU-PRO is usually worse unless you fit some specific use cases.
and then it will reach out to other instances to grab content from every external community that at least one local user has subscribed to
It’s the other way around. The local user subscribes to the community on the remote instance, which causes the remote instance to then push you every action that occurs on that community as it happens. The pull method is only used once and doesn’t bring in comments, it’s meant as a preview for when a remote community is used for the first time.
And this is why their content won’t make it to your instance: it expects the other instance to send it to you, but they’re refusing to. Similarly, they won’t accept content from your instance, even though it’s trying to.
Local and remote communities are pretty similar internally, federation happens as a separate process in a queue system.
This leads to this:
you can still subscribe to subs on defederated instances, it’s just the interactions that don’t get passed back and forth.
Any reason the VPN can’t stay as-is? Unless you don’t want it on the unraid box at all anymore. But going to unraid over VPN then out the rest of the network from there is a perfectly valid use case.
Kernel exploits. Containers logically isolate resources but they’re still effectively running as processes on the same kernel sharing the same hardware. There was one of those just last year: blog.aquasec.com/cve-2022-0185-linux-kernel-conta…
Virtual machines are a whole other beast because the isolation is enforced at the hardware level, so you have to exploit hardware vulnerabilities like Spectre or a virtual device like a couple years ago some people found a breakout bug in the old floppy emulation driver that still gets assigned to VMs by default in QEMU.
Installing Ubuntu isn’t breaking any DRM or any anti-piracy measures.
Unless your country is really strict about using devices exclusively as the manufacturer intended, but that’d be countries that also want to monitor everything you do. Hard to tell without knowing what country that is.
That said, I’m pretty sure Google is perfectly okay with people doing that. Even on the Pixel phones, they openly let you unlock the bootloader, and even allows you to add your own keys so you can relock the bootloader with a custom OS. They only care about security and people not getting a device from eBay full of malware. That’s why there’s a message during boot that’s either orange or yellow warning, to tell the users the device has been tampered with. But everything works fine otherwise.