zarenki

zarenki , 9 days ago

It is open source, but had some controversy. Most prominently the addition of telemetry a few years ago, which was never included in the builds managed by Debian or most other distro maintainers. They also added a Contributor License Agreement which lets the Audacity project change its own license (even to a non-foss one, though they promise they won't) without needing to have the change approved by any individual developers.

zarenki , 7 days ago

I'm not completely sure but I think they removed it at some point after the public backlash (which was 3 years ago now). For the Windows version at least, there apparently used to be an option during the installation wizard for setting whether telemetry is enabled or not. Most Linux distros never had the telemetry at all. I don't know about Mac.

zarenki , 12 days ago

and it's free

This is very uncommon in the US. Most major banks (I'm not aware of any exceptions) charge a fee for each outgoing wire transfer, usually $25-$30. Bank of America, Wells Fargo, Chase, and PNC for just a few examples I'm aware of, plus every credit union that has local branches in my area. Some of those banks even add a second fee at the recipient's side for incoming wire transfer.

They often encourage customers to rely on third party services like Zelle instead for small transfers to friends and family. Many banks' sites/apps can also handle transfers between two accounts that both belong to the same bank for free too.

zarenki , 19 days ago

Even their earliest "uncarrier" features weren't without issue. Making certain services (spotify, apple music, youtube, netflix, etc.) not count against subscribers' data caps, while continuing to enforce data caps for other uses, goes against the spirit of net neutrality. This also includes throttling video streams by default to force lower quality (with opt-out on their site).

Promos like a free pizza on Tuesdays seems like a neat optional perk on the surface but their existence fundamentally mean subscription expenses on cellular network service are partially going towards things that have not even the slightest tangential connection to the service.

zarenki , 1 month ago

It is a Linux machine. Runs a Debian derivative, and it's not like Windows or anything else that isn't Linux/BSD can run on a RISC-V laptop.

This isn't the first RISC-V laptop, but the significance of a RISC-V laptop existing is primarily for developers who work on software targeting RISC-V systems. The ability to run RV64 programs without emulation and to natively compile RV64 software without cross-compilers is valuable to some people. Also, China in particular sees value in having computing products that aren't affected by sanctions; the processor in this is designed and manufactured by a Chinese company without licensing any intellectual property from US or UK.

Explaining what RISC-V is

RISC-V is a relatively newer CPU instruction set architecture that competes with x86 (Intel, AMD) and ARM (Qualcomm, Ampere, MediaTek, etc.). Its current designs don't really match those two in general-purpose performance yet but has the distinction of being a free, open, and extendable standard. Whereas x86 has only two CPU vendors and ARM has many vendors who all need to pay per-core license fees to ARM Holdings and have limits imposed on what they can do to it, RISC-V processors can be made by any hardware vendor with the means to make a processor and can be custom-designed to better fit specialized use-cases. Its use in general-purpose CPUs is catching on fastest in China but it sees use across the world in academia and in special-purpose processors by companies like Western Digital.

zarenki , 1 month ago

Yes.

My home server has dropbear-initramfs installed so that after reboot I can access the LUKS decryption prompt over SSH. The one LUKS partition contains a btrfs filesystem with both rootfs and home as subvolumes. For all the other drives attached to that system, I use ZFS native encryption with a dataset that decrypts with a keyfile from that rootfs and I have backups of an encrypted copy of that keyfile.

I don't think there's a substantial performance impact but I've never bothered benchmarking.

zarenki , 2 months ago

The problem with those TV apps is DRM. All the major streaming services require that you either use a locked down platform (probably checking SafetyNet and more on Android TV) or settle for their browser UI which lacks dpad support and gets quality throttled to 1080p or lower.

Circumventing that DRM is possible, but no project at the scale of a platform like those would dare the both legal risk and support headache of making those circumventions (which are very liable to break) a core part of the OS.

Kodi (and distros using it like LibreELEC) exist for people who want a FOSS platform for using non DRM encumbered media with a TV remote interface.

zarenki , 2 months ago

Something I've noticed that is somewhat related but tangential to your problem: The result I've always gotten from using compose files is that container names and volume names get assigned names that contain a shared prefix by default. I don't use docker and instead prefer podman but I would expect both to behave the same on this front. For example, when I have a file at nextcloud/compose.yml that looks like this:

volumes:
  nextcloud:
  db:

services:
  db:
    image: docker.io/mariadb:10.6
    ...
  app:
    image: docker.io/nextcloud
    ...

I end up with volumes named nextcloud_nextcloud and nextcloud_db, with containers named nextcloud_db and nextcloud_app, as long as neither of those services overrides this behavior by specifying a container_name. I believe this prefix probably comes from the file-level name: if there is one and the parent directory's name otherwise.

The reasons I adjust my own compose files to be different from the image maintainer's recommendation include: to accommodate the differences between podman and docker, avoiding conflicts between the exported listen ports, any host filesystem paths I want to mount in the container, and my own preferences. The only conflict I've had with other containers there is the exported port. zigbee2mqtt, nextcloud, and freshrss all suggest using port 8080 so I had to change at least two of them in order to run all three.

zarenki , 2 months ago

Likely reversing a major anti-consumer decision is nice, even if it took seven years.

Knowing that consumer protections repeatedly flip back and forth every time the executive branch switches political party, and even then only if we're lucky, is not so reassuring. What's stopping it from being repealed again in a few years?

zarenki , 2 months ago

if the featureset is not clear enough at first glance

My experience as someone who has barely dabbled in Matrix, tried comparing clients, and knows a lot of people who stick to Discord: a lot of Discord users heavily use custom emotes, voice chat, and screen sharing. It's not even easy to figure out which Matrix clients support each of those features without installing everything and trying it out. There's a clients comparison on matrix.org that mentions Voip but not stickers or video.

For stickers alone:

• Element is widely considered the go-to Matrix client but uses a strange integration system for predefined sticker packs instead of the MSC2545 stickers that more closely resemble what users coming from Discord would want.
• Cinny seems to have the best support for stickers/emotes but its site doesn't mention them at all. It supports uploading and managing sticker packs at either a channel or user level, provides a nice picker UI to send any picture from those packs as either a large "sticker" or a small inline "emoji", and allows using them for reactions.
• FluffyChat mentions stickers on its site and has the second best sticker support, with all of those except reactions and a graphical sticker picker for inline emoji (need to type them as shortcode).
• SchildiChat, Nheko, and NeoChat have some sort of limited support for custom stickers/emoji. NeoChat is the only one of those that advertises stickers on its main site. Nheko mentions them in a GitHub readme.

Being able to freely use custom emotes without paying for a Discord Nitro subscription nor server boosts would be a great selling point but it's not something most users would be able to figure out before signing up. The limited client support isn't great; e.g. Fluffy is the only Android client that supports sending custom stickers but some people may dislike the chat bubbles style UI.

zarenki , 2 months ago

I never had problems with Debian stable, especially on headless server. But it's not especially well-suited for brand new desktop hardware; even Ubuntu LTS and RHEL focus more on hardware enablement backports than Debian.

I've had a worse experience with Debian testing breaking my system with updates than Arch. Adding to that the freeze period (2012's was the worst, lasting 11 months) makes testing feel like the worst of both worlds between rolling and standard release distros.

zarenki , 2 months ago

Not every work environment is the same.

When I first started with my current employer I was given a system with RHEL preinstalled and I replaced it with Fedora on my first day. I was told to use LUKS and given a normal OpenVPN profile but otherwise they don't control or monitor anything about my workstation. No matter how many years or decades I stay at this company, it's extremely unlikely I'll ever touch an OS that isn't Linux-based during work time.

Every previous job I've been at also had me use Linux for my primary workstation, because my field of work more or less requires it, but some have needed me to access a separate Windows system/server/VM on rare occasions.

zarenki , 2 months ago

As someone who used to use Arch a decade ago: I still use pacman for devkitpro at least, and I do miss how fast its parallel downloads get, but the tool I use to manage packages is far from the most important difference between distros to me, even if you assume not needing AUR.

zarenki , 2 months ago

The first I tried was Ubuntu 7.04 but I didn't stick with it and went back to XP. Until I ended up with a hardware setup that wouldn't work on Windows XP (widescreen monitor + Intel graphics driver with no widescreen mode options) but worked perfectly on Ubuntu 9.10. I never truly went back to Windows since.

Tried a few other distros in 2011 then switched to Arch for a couple years, Xubuntu for a couple years, Ubuntu GNOME for 7-8 years, and finally switched to Fedora last year.

zarenki , 2 months ago

Nonfree media codecs like HEVC/h265 are affected by US software patents. Distributing them from US servers without paying license fees to MPEG LA can put the host at risk of lawsuit. VLC, deb-multimedia (Debian), and RPM Fusion (Fedora) all avoid that by hosting in France, but even with those sources enabled patent issues can break things like hardware acceleration. Free codecs like AV1/VP9/Opus avoid all these problems.

Microsoft is US-based and can't avoid those per-install fees. They could cut the profit from every single Windows license but apparently chose not to.

zarenki , 2 months ago

You joke, but it really exists: the company that acquired uTorrent 17 years ago now sells an ad-free version of their current torrent client as "BitTorrent Pro" for USD$20/year, or alternatively as part of a VPN service bundle for $70/year.

Needless to say, stick with FOSS clients like qBittorrent/Deluge/etc instead.

zarenki , 2 months ago

Debian. I was in a similar boat to OP and just a couple weeks ago migrated my almost 8-year-old home server setup from Ubuntu LTS to Debian Stable. Decided to finally move away from Ubuntu because I never cared for snap (had to keep removing it with every upgrade) and gradually gained a few smaller issues with Ubuntu. Seems good to me so far.

I considered RHEL/Rocky but decided against them largely because I wanted btrfs for my rootfs, which their stock kernel doesn't have, though I use a few Red Hat developed tools like podman and cockpit. Fedora Server and the like have too fast a release lifecycle for my liking, though I use Fedora for my desktop. That left Debian as the one remaining obvious choice.

I also briefly considered throwing a Debian VM into TrueNAS Scale, since I also use this system as a ZFS NAS, but setting that up felt like I was fighting against the "appliance" nature of what TrueNAS tries to be.

zarenki , 2 months ago

That's actually a choice you're offered during Debian's interactive install. When you're offered the option to set a root password, if you leave it empty the system will disable direct root login and instead give your first normal user sudo access.

zarenki , 2 months ago

Every single other browser is Chromium.

One exception I'm aware of: GNOME Web (aka epiphany-browser) uses WebKitGTK, which is based on Apple's WebKit rather than Google's Chromium/Blink. But it's Linux desktops first and foremost. Not on mobile platforms, not exactly intended for Windows (might be usable with Cygwin/WSL) or macOS (seems to be on MacPorts) either, and even on non-GNOME desktops like KDE it might seem a bit out of place.

I daily drive Firefox but Epiphany is my first choice fallback on the rare occasion I encounter a site that's broken on Firefox.

zarenki , 3 months ago

The passive adapters that connect to DP++ ports probably still rely on this HDMI specific driver/firmware support for these features.

zarenki , 3 months ago

If you're planning to subscribe to Proton Unlimited or Proton Family regardless, you might as well try Proton Drive. They try to be fairly privacy focused similar to Proton's other products.

Mega has a similar privacy-oriented design. Such that the server side shouldn't have direct access to your unencrypted file data or its decryption keys.

Still, any web-based service necessitates trusting the JavaScript you receive not to leak out your password or keys. Both Proton and Mega have a good track record so far in that regard, but the best practice for privacy with raw data storage is to encrypt your own data with local tools and treat any remote server as untrusted.

zarenki , 3 months ago

I would not count on all major distros maintaining support for processors as old as Core 2 forever.

RHEL 9 in particular (and by extension CentOS Steam, Alma, Rocky) already dropped support for all of the processors affected by this breakage since 2022.

Linux systems often group these CPU feature set generations into levels, where "x86-64-v2" requires SSE4 and POPCNT (Nehalem/2008 and newer) and "x86-64-v3" requires AVX2 (Haswell/2013 and newer).

Ubuntu and Fedora are already evaluating optimized package builds for both v2 and v3 but haven't announced any plans to drop baseline x86-64 yet; I wouldn't be surprised to see it happen within the next two years. Debian is a relatively safer bet for old hardware.