the distros you tried were… adventurous, to say the least, none of those would even occur to me. the my rule of thumb is:

1. fedora - for the newest hardware, you qualify big time, especially if RH was an initial choice for you
2. ubuntu - middle of the road, best for the majority of users, excluding newest or really old hardware
3. mint/debian - for older hardware

everything else is for hobbyists and/or special use cases, not for people expecting to do actual work.

nope

anyone dunking on the article, this is pretty far away from a how-to-lilst; it’s more of a “think about these things if you haven’t up until now” and as such a net positive. wrong community for it, though.

I’m gonna disagree on both counts.

I run fedora on my desktop and a bunch of laptops and have done so for years; I would never recommend it to a beginner, or even do the install and all the laborious post-install steps and then hand it over.

Plasma is closer to a standard desktop paradigm, but it has its stupid choices that aren’t welcome on a laptop - FOUR finger gestures, really? why?! also, it’s way too configurable so it’s super-easy to fuck up something without an easy way to reset it.

so, both the options you mentioned are natural progressions for an intermediate user, someone who started with an easy option like Ubuntu + Gnome, and then progressed because they don’t need the kiddie wheels no more; but not as first distro.

anyone knows how to accomplish similar with LineageOS? I had a programmable power off and on timer ona Samsung S3 a long time ago, but that’s missing from the current builds.

I used to run my stack on macOS and back then I used Catch to grab episodes of shows I was subscribed to via ShowRSS and Filebot to rename and sort the downloaded movies and shows in a Plex-friendly layout; Plex then grabs new additions autmatically, pretty sure you don’t need to rescan manualy.

like most here I replaced that mess with Sonarr/Radarr and eventualy switched over to Jellyfin when Plex introduced one “feature” too many.

everybody recommending mint skipped over the fact that this is a convertible, i.e. has touch. mint/cinnamon/mate isn’t terribly optimized in that regard and is rocking X11, a headache a beginner doesn’t need nowadays. mint is a phenomenal choice for older laptops, but not this one.

with a heavy heart, I’m recommending Ubuntu. it runs Gnome, which is a way more modern DE, runs on Wayland so has solid gestures and touch support, and lastly, it is very beginner friendly. you’ll be able to sort out any potential issue as that’s the most widely used distro and has solutions and tutorials for practically everything.

once you’ve crossed over and gain some experience, you’ll inevitably start banging your head on the ceiling (snaps and such). by then you’ll have enough experience and knowledge to move to something better.

also, a darknet diaries episode.

this is like month+ old info, at least mention that when posting. otherwise people assume it’s an update.

I deployed RocketChat on two different client installations (didn’t check the licensing you’re mentioning, I’ll have to look into that) and I run a Prosody instance (XMPP) on my own; tried Matrix for a short while and ran away from that mess as fast as I could. anyhow, although the messengers work without any significant issues or downtime, the amount of flak I get from non-tech normies about the client apps is staggering.

the apps just aren’t up to current UX standards. they’re used to Twitter and iMessage and Telegram quality UX, and getting used to these PoC-quality apps - both on mobile and desktop - makes them “feel icky”. I’ve had to intervene on a number of occasions when some of them transferred their business-related comms to other platforms because they just can’t/won’t get used to these apps.

check out dell latitude 5285/5290 2-in-1. they are Surface Pro lookalikes with detachable keyboards, but with way service-friendlier interior - easy to open and SSD, comms, battery can be easily replaced, whereas RAM is soldered. the screens (12" 1920x1200 IPS mutlitouch) are gorgeous and the hardware isn’t too shabby, kabylake (7xxxu) and kabylake-r (8xxxu), with standard UEFI BIOS so you can install Linux and have SecureBoot even. I can get them locally for $100-150, dependent on config and equipment (even less if they’re without battery and keyboard).

edit: yeah, I misunderstood your idea, I thought you wanted a cheap linux tablet. what you actually want is a fantasy - an ultra-portable device with huge battery autonomy running linux and such a thing doesn’t exist, for any kind of money.

namely, the mentioned dells are twice the heft of a normal android tablet and the battery autonomy is laughable; not only is it not an improvement over a normal laptop, it’s likely to be worse, as that thing’s essentially a laptop with extras, like touch, gyros, etc.

then comes the real hammer - touching the thing. Gnome and Plasma (and their derivatives) have touch support but if you’re coming from an android or iOS tablet, that support is in its infancy. it’s crude, inconsistent, flaky, and not very well propagated throughout the system. it’s way better than it was a few years ago, but this is not something you’ll want to hang your career or education on.

you can tweak the thing into something semi-usable, and for the price (around $100) that’s a worthwhile endeavour and cute hobby project. it bears repeating, it is not daily driver material, and that includes way pricier solutions - saw a Ryzen 6-series the other day for like $700; everything I’ve written applies to it as well.

how about adding the cutoff limit in the ui then? find myself shrinking and shrinking an image until it gets accepted and then promptly forgetting what the limit was.

so, no need to resize images before upload on account of “image too large”, lemmy will handle that?

can you share the server spec?

regarding the pricy enclosures, there are vastly cheaper eGPU solutions especially if you’re able to utilise the on-board M.2 or mini-PCI slot. if you don’t move the laptop around, it’s a viable option. this would be an example - not an endorsment. you’d need a $15 PSU to power the graphics and it works well in linux, with the hotpluggability being the primary issue; if you’re willing to shutdown before attaching the eGPU, close to no issues.

you can run it as graphics card (i.e. utilize its display outputs) or just use the laptop’s display with optionally switching between the onboard and discrete graphics.

to me the Ian Holm abomination was terrible, without any redeeming qualities. same thing as rogue one, exact same shittyness, zero technological progress, crude and unnecessarily distracting.

using rsync:

why not btrfs send | btrfs receive? is there some advantage to rsync?

did you hotswap the drives after each btrfs replace or shutdown and then swap?

what’s your host OS and do the drives spin down if inactive?

thanks for the writeup!

I’ve set up a local mail archive with just dovecot + imap plugin. you don’t need the full mail server with postfix and whatnot, as it’s not intended to send anything anywhere, or even receive anything for that matter. it just sits there ready to be searched with thunderbird, no need for other complex solutions you’ve mentioned.

found the culprit: I’ve connected my jellyfin-media-player apps to a CNAME alias provided by my Pi-hole (jellyfin.box) and a matching nginx proxy entry:

        listen 80;
        listen [::]:80;

        server_name jellyfin.box;

        location / {
                proxy_pass http://127.0.0.1:8096/;
       }

so when I disconnected the app from the jellyfin.box server and connected it to the “new” server at server.box:8096 it started working immediately. looks like I’m missing some headers in that proxy so I’ll look into it.

edit: yepp, adding headers fixed it, I can connect to the jellyfin.box server and have it detected by all other devices on the network.

        location / {
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection $http_connection;
                proxy_pass http://127.0.0.1:8096/;
        }

glad it’s working for you but no dice here. installed it fresh on a laptop, same deal, doesn’t detect either of them.

both installs are flatpaks, how about yours?