Why LVM + BTRFS instead of only using btrfs? Unless you need RAID 5/6, which doesn’t work well on btrfs.
Why LVM + BTRFS instead of only using btrfs? Unless you need RAID 5/6, which doesn’t work well on btrfs.
Nintendo didn’t put legal pressure on emulator devs for decades at this point, which made devs less cautious about preserving their pseudonymity.
Now it’s too late and they can’t stop Nintendo from finding out who they are and which mistakes they did at some point over the years.
Maybe a new generation of emulator developers will be more protective of their identity, by using hosting providers like Njalla or privacy networks like i2p. The latter would limit access (as it requires i2p), which isn’t desirable for most users.
Most people using these sites prefer the lossless codec flac anyway, which can be transcoded to anything.
MP3 320kbps and MP3 V0 is transparent to most (all?) people, so there’s not much of a reason to go with a newer codec, except for space savings.
There’s not even much of a reason to go with 320kbps, as V0 achieves the same quality with smaller files. That’s why almost nobody actually downloads MP3 320.
I personally think MP3 is there for historical reasons, as I don’t see a reason for using lossy codecs for archiving purposes. Just download flac and transcode it once or on demand on a media server for streaming.
Not natively, as far as I know. NTFS works well on Linux for the most part (unless you need permissions), but macOS natively only supports reading.
FAT32 is universally well supported, but the partition size limit and 4GB file size limit make it unusable for me.
Linux filesystems as well as macOS filesystems aren’t supported natively anywhere else, so ExFAT it is.
ExFAT does make sense, since it’s the only filesystem which supports read and write on all major OS. Sadly it’s also pretty basic, and thus not the first choice on any OS - except for USB sticks.
I generally recommend formatting any new storage media before using it. Just to make sure it’s properly formatted to work with my machine, and the manufacturer didn’t mess up their implementation for some reason.
What format did the drive use? HFS+?
Navigation within a single workspace is pretty much the same as in Sway/i3.
I don’t remember how it’s done in Sway/i3. If you have two monitors side by side, moving the focus from the left most window on the right monitor to the left, moves the focus to the left monitor.
A major difference is the workspace design. In Cosmic, there’s currently a single set of workspaces for each monitor. In Sway there’s one set shared between all monitors.
The workspaces can be either horizontal or vertical, which is useful depending on how you configure a multi monitor setup. This is because with vertical workspaces, moving down from the bottom window moves the focus to the next workspace (and vice versa).
In my case with two monitors side by side, this is awesome, because moving the focus feels like moving naturally on a single giant plane. E.g. moving down moves to the next workspace, then moving to the left moves to the left monitor, where I could move up to the workspace above etc.
It’s difficult to explain for me, so I recommend giving it a try (or maybe wait a while, depending on your needs, e.g. there’s no VRR, no window rules etc. Also, currently monitors have to be aligned at the top edge to be recognised as side by side. If they aren’t, moving between monitors and workspaces doesn’t behave right.).
I like the Cosmic tiling better than Sway, because it tiles through the long edge by default.
I.e. If I just two windows after each other, Sway will tile them as two equal columns. If I open another window, it’ll add another column, while making each column the same size.
Cosmic also creates two equal columns with two windows, but the next window tiles the focused column horizontally.
With three windows this means half the screen is a single window, the other half is two windows taking up a quarter of the screen. Obviously if you instead focus another window, it’ll be tiled instead.
This is basically the same behaviour as the autotiling script for Sway/i3, but it works reliably (I’ve always had issues with those scripts).
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.
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.
fclones is fast and supports hardlinking/softlinking of duplicates instead of removing them.
I’ve used it successfully to deduplicate my documents folder (and “archive”).
As its quite the amount of data, I recommend using the --cache
option to make subsequent runs way faster, if you want to dial in the options. This directory can be deleted at any point and isn’t necessary.
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.
I disagree with the notion that it’s better for the cheaters to have an easier time (and less chance of being detected), but you’re right, BattleEye doesn’t solve the cheating problem for GTA.
Rockstar should fix their netcode and run game server on dedicated server, instead of their customers PC’s. I’d think decting aimbot isn’t the biggest issue, while cheaters are able to break entire lobbies…
IMO no game should require client side anti cheat except for shooters, where looking through walls and aimbot is actually difficult to detect server side. At least for those is it possible to find valid arguments (except for being lazy).
tl;dr
Read the first sentence after each citation ;D
So Wayland, a protocol, is needing the addition of other protocols?
Yes. What we know as Wayland is the Wayland core protocol and a few other protocols that are absolutely necessary for desktop use (stable).
Then there is staging, which is not necessarily implemented by all compositors, e.g. fractional scaling.
Unstable also exists, which is even easier to get a protocol into (idk the exact requirements, likely the amount of support and explicit dislike by contributors).
These are often only used by a subset of compositors with e.g. XDG decoration allowing compositors to announce to clients (windows) that they support server side decorations (top bar with close/minimize/maximize buttons). This isn’t implemented by Gnome, but most other desktops support it.
Different desktops also have their own protocols, which are published so that apps targeting those desktops can implement them. Some are also supported by other desktops, if they think they are suitable for them.
E.g. wlr layer shell makes status bars possible, which are used by basic compositors like Sway or Wayfire. KDE also supports it, even though it was originally created by wlroots.
Does this make it a Wayland Distro?
In a way you could say that a compositor is a Wayland distro, as it implements a subset of Wayland protocols.
In the end this is good, because it allows for rapid development and discontinuation of protocols. E.g. if a better protocol comes around, both protocols can be supported at the discretion of every compositor.
The goal was to solve the problem of X11, where Xorg still has to support drawing UI by itself, even though no program or toolkit uses it anymore (the 80s were very different). The Wayland core is so minimal there shouldn’t be any issue with using it for a very long time.
Also, Wayland was developed by people with the goal to use it in automotive and other industry applications, where basic desktop functionalities, like multiple windows or session lock, aren’t useful.
Cheat makers are likely behind this, asthey have monetary incentives to do so. If its Linux users I’d feel bad because stopping others from playing just because they can’t, is extremely bad behaviour.
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).
It’s more so that you are allowed to try to block ads. If YouTube adds DRM or otherwise manages to stop usage of ad blocking, they are completely in their right to do so.
IIRC if something runs on your system, you have the right to mess with it, however you want — e.g. block specific parts of the site, or use reader mode etc.
That’s one of the reasons I don’t like buying games with Denuvo. Waiting a few years before buying games is something I usually do anyway, so at that point Denuvo DRM would’ve already been removed.
https://flathub.org/apps/dev.edfloreshz.CosmicTweaks
https://github.com/cosmic-utils/tweaks