Blocking incoming traffic and accepting outgoing traffic is usually the default for distributions anyway.

I’m not the creator of the survey, but I’ve just send them the link to this discussion on Mastodon, so they can take the feedback into account.

There’s an issue with posts about which games work and which don’t.

https://github.com/pop-os/cosmic-epoch/issues/311

Thanks for the correction. It’s a shame that sysadmins balcklist middle nodes too, since they won’t see any TOR traffic originating from your IP address anyway.

Make sure to not refresh the page, else it seems like all progress is lost.
I found out simultaneously that I enabled pull down to refresh the page in Firefox Android.

Edit: The survey wasn’t created by me, I just shared it.

There’s different types of relay, including exit relays, which are the legally problematic type. Middle, guard, and bridge relays don’t face the same issues with law enforcement and IP blocking.

Blender and DaVinci Resolve work better on Nvidia. AMD might work, but it will be a hassle and you’ll likely need the proprietary AMD drivers anyway.

With Nvidia supporting Wayland and the open-source NVK continuing to get better, you could even switch to open source drivers for gaming at some point, if you prefer.

Edit: I’ve had enough issues with AMD GPU’s clocking down while gaming, leading to micro stuttering. So don’t buy AMD just because everyone tells you they work flawlessly.

For CPU and mainboard, everything works well — just don’t buy a random unknown SSD from Amazon, then you’re asking for data loss and random issues.

He said somewhere that he did ask a top contributor if they care, and they didn’t. He also said that he rewrote a bunch of code to be able to change the license.

I can’t verify this, but it doesn’t seem like he infringend on someones copyright. Small changes (e.g. a few lines) don’t even (necessarily) qualify for copyright (just like the few sentences I wrote here likely don’t).

Yes, there’s many ways to make programs unable to use other network interfaces. E.g. I’m creating a network namespace with a single wg0 interface, which I make services use through systemd NetworkNamespacePath.

That said, I’d argue gluetun is pretty much foolproof, especially with most people using docker which messes with iptables (edit: although I don’t know if this’d be an issue for this use case).

I also think the Element Web UI is lacking, but it’s gotten better over the last few years, after they started taking design more seriously. With Element X they do proper UI/UX design as a first step, and then implement it.

The old Riot.im client was exceptionally terrible, in performance and design, so I’m really happy with Element X.

Element being focused on corporate needs is nothing new, since they’ve a few large (government, healthcare) contracts, and they’ve struggled with financing for years now. Big deployments using Synapse is the big reason dendrite doesn’t see much development anymore, even though it was planned as a replacement for Synapse at first.

I believe many of their side projects (P2P, VR) exist because they try to find possible business avenues, although I feel like most of them aren’t successful (and they stretch to thin because of that).

Unencrypted messages are useful for very large rooms, where encryption doesn’t provide meaningful more privacy since public rooms have to be considered public space anyway. Encryption does have overhead, so it makes sense to disable it.

Private rooms are E2EE by default and can’t be created unencrypted (at least in the Element X mobile UI). This is a good way to handle it IMO.

Discord uses their own screen sharing implementation because it performs better than what’s available in Electron by default. I don’t expect Element to achieve that, considering their focus isn’t gaming.

The user experience is generally worse than Discord, like any federated system compared to centralized platforms.

There is Cinny, a client with an UI similar to Discord. Element X is a great mobile client, and imo far superior to Discord for 1 on 1 chats (to be fair, I really dislike Discord 1 on 1 chat experience, so I’m biased).

Edit: It’s worth noting that Element X does not support Spaces yet, which allows for grouping of rooms similar to Discord Server.

• Terminal file manager are useful on a server over ssh.
• ripgrep and fd support is better than any GUI file manager find and replace.
• Some people like using vim keybindings
• The three panel view is really useful. On the left is the parent folder, the middle the current and on the right a preview, e.g. the selected folder or the contents of a picture or a text file. It’s faster to navigate and pop back into the shell.

I really wonder how you managed to uninstall nix. Editing configuration.nix shouldn’t even allow for removing .nix…

Anyway, this post made me remember why I used btrfs for my new btrfs system.

Good idea to write a function, I’ll do that right now. Over the last few weeks I’ve been regularly doing the Ctrl+Z, bg, disown, which does get old pretty quickly. At least I now remember the terms and don’t have to search for them each time I need it :D

No, this runtime only works if the developer enables it on their side.

Yeah, I’m not sure whether Bitwarden always had support for exporting the vault on mobile, but it’s an awesome feature.

They are evaluating different ways to continue to support ad blocking. E.g. “unbraving” Brave Browser, or just implementing their adblock-rust.

They most likely won’t support MV2, since it would get increasingly difficult with each update to Chromium.

https://github.com/ungoogled-software/ungoogled-chromium/issues/662

Creating a wayland compositor based in wlroots is much more work than an X11 window manager. And then there’s quite a bit of work to keep up with new Wayland protocols.

But I personally don’t think there’s a need for more compositors, since the existing compositors do support all kinds of tiling.

E.g. river has custom layout providers, which allows for creating completely custom tiling behaviour. There’s even a hyprland plugin which implements river-layout-v3.