avidamoeba

avidamoeba, 8 months ago (edited 8 days ago)

Is that bad though? I don’t mind renting a movie I really like even if my friend has it on their Plex. Especially if it’s from a small studio. Currently I do that via Google TV. Plex Inc being a small private company might use the money better than a publicly traded giant. I wouldn’t mind my friends and family spending a few bucks on it either.

Of course if Plex starts enshitifying existing private streaming features to push this, that’ll be another matter altogether. Which would not be unexpected.

avidamoeba, 8 months ago

Linux’es diversity has never been found in the large fundamental pieces of software. Instead it’s typically been found in the nooks and crannies between them. We’ve typically had one or several of those and most have used those. It’s the kind of diversity you find between evolutionary differences between the same species, not revolutionary differences.

avidamoeba, 8 months ago

Melts in long term support

avidamoeba, 8 months ago

It doesn’t use GTK does it?

avidamoeba, 8 months ago (edited 2 months ago)

Beautiful, so there’s a good chance for it to not be a hot mess! Looking forward to it. 😊

avidamoeba, 8 months ago (edited 2 months ago)

Could be a defective library that’s used by many apps. Glibc, etc. That said, if something like this is that broken, others should be complaining about it too.

avidamoeba, 8 months ago (edited 2 months ago)

Let’s not. It’s not a good tool.

avidamoeba, 8 months ago (edited 2 months ago)

Prometheus.

It’s open source, it’s easy to setup, its agents are available for nearly anything including OpenWrt, it can serve the simplest use case of “is it down” as well as much more complicated ones that stem from its ability to collect data over time.

Personally I’m monitoring:

• Is it up?
• Is the storage array healthy?
• Are the services I care about running?

I used to run it ephemerallly - wiping data on restart. Recently started persisting its data so I can see data over the longer run.

avidamoeba, 8 months ago (edited 2 months ago)

OP, this is terrible advice. Do not follow! Unless you run into a problem with Ubuntu LTS or distro based on it that you and the community cannot solve and it’s due to the LTS, stick with LTS. The vast majority of users are on LTS which is why there are tested solutions for most common problems you might run into. LTS releases last for many years so once you solve a problem, it’s likely you won’t have to solve it again for a long time, unless you decide to make your life more interesting by upgrading or changing the OS. Non-LTS releases last for 9 months or so, then you’re thrust onto a new set of changes and bugs that may or may not hit you, with much fewer comrades to test them and find solutions for. As a new user, if you’re going with Ubuntu or Ubuntu-based OS, stick to LTS. You’ll have enough hurdles to cross getting acquainted with the OS itself.

avidamoeba, 8 months ago (edited 2 months ago)

Great advice substantiated by clear reasoning. I second it. More specifically, grab Ubuntu LTS. Going with an Ubuntu LTS based distro might present some extra challenges but it would probably be fine too.

Ubuntu is great for the reasons outlined and it provides an obvious path to Debian, should you want to move away from it in the future.

avidamoeba, 8 months ago

I did a similar inquiry a few months ago. I tried DocuWiki and Wiki.js. Ended up with Wiki.js. It’s very easy to setup with docker-compose. Everything is stored in Postgres but it also exports to the local filesystem in Markdown. Its advanced built-in search is pretty good.

avidamoeba, 9 months ago (edited 7 months ago)

Seems like a measurable improvement although not dramatic in most benchmarks.

avidamoeba, 9 months ago

If they received a lot of money from their work and they used it to increase the impact of their projects, they wouldn’t be billionaires. The money would have been spent on the projects. If Linus headed a non-profit that received 10B a year revenue and spent most of it, leaving Linus with 0.5M-1M yearly salary, he wouldn’t be a billionaire and the billions spent on the Linux project would have had a significant impact. If on the other hand he pocketed 1B a year, there would be 1B less for the Linux project. And Linus would have been/become a different person.

avidamoeba, 9 months ago

Is it? I’ve been on Debian/Ubuntu since 2005 and I’ve never seen anything on-screen whenever I’ve gotten a kernel oops.

avidamoeba, 10 months ago

Use a package management system that supports this use case.

avidamoeba, 10 months ago (edited 9 months ago)

In short, it’s difficult. You have to be careful to only use themes that are are tested to work with your version of GNOME. That’s why while using GNOME, I’d stick with whatever stock theme variants come preinstalled. At least you get a few accent colors on Ubuntu. You can always change your wallpaper. 🥹

avidamoeba, 10 months ago (edited 10 months ago)

Removing snap is somewhat unwise. Ignoring it is the safe way to go. Ubuntu might ship a system component you’re not aware of via snap. If you kill snap support you may end up with a broken system. To avoid headaches, simply ignore snap.

avidamoeba, 10 months ago

Did they finally switch to Qt?

avidamoeba, 10 months ago (edited 10 months ago)

Ooof. That hurt.

avidamoeba, 10 months ago (edited 10 months ago)

Because you can package and deploy OS components with it. As a result you can build an OS with it, do foolproof updates of it and …gulp, happy tear… rollback components without involving any other system like a special filesystem.

My bravery comes from being a software guy that’s been doing OS software development for over a decade so I believe my opinion is somewhat informed. 😂 I’m currently working on a software updates implementation for an automotive OS.

avidamoeba, 10 months ago (edited 10 months ago)

I think they’re a good way to package apps. Superior to Flatpak for sure. I like Flatpak too and if Canonical abandoned Snap tomorrow, I’d switch my snap-packaged apps to Flatpak. The only non-bullshit downside of Snap is the proprietary server-side and the lack of multi-repo support. I don’t care much about either because I know implementing either is fairly uncomplicated and it will happen should the reason arise. If Debian wanted to start using Snap, it’d take them a month to get the basics working with their own server side. If the client side was proprietary too, I’d have had a completely opposite opinion on Snap. Finally Canonical supplies all the software on my OS. I use third party repos only when absolutely necessary. If Canonical ran a proprietary apt server side, I wouldn’t even know, apt doesn’t care. Some of the myriad HTTP mirrors could easily be running on IIS, or S3, or Nexus. The trust equation for snap is equivalent.

avidamoeba, 10 months ago (edited 10 months ago)

The initial use case for Snap, when it used to be called Click (circa 2012-13), was mobile apps for Ubuntu Touch. Those were the same as desktop Qt apps, just using the a mobile theme and layout. Canonical developers just had the foresight to create a design that isn’t limited to that use case. As a result Snap is a superset of Flatpak in terms of use cases. Flatpak can probably be rearchitected to match that if anyone cared. If that were the case I’d also be drumming it up.

The funny thing is, we wouldn’t be having any of these discussions over the merits of Snap if RedHat came up with it instead of Canonical and the server side was OSS from the get go. When RedHat was cool that is. In fact likely Canonical would have been using thet too. Just like they use PulseAudio, Systemd, and Wayland.

avidamoeba, 10 months ago

We won’t stop using the market till it starts working.

avidamoeba, 10 months ago

I’m pretty excited about it. It’s a much cleaner solution to the problem immutable OSes are trying to solve. Dare I say it’s better even than the Android model because it covers the whole stack with a single system.

avidamoeba, 10 months ago

Based on what I saw on macOS I wouldn’t touch Homebrew with a 10 feet pole. We have proper packaging systems in the Linux world. The Chromium snap is supported by Canonical so that’s a great candidate for anything that comes with snap or can use snap. If I couldn’t use snap, I’d use the Chromium flatpak from Flathub.