I’ve used one called CIFS Documents Provider in the past, worked very well.

It adds SMB/CIFS as a storage provider like Google Drive or Nextcloud to the Android built in file manager.

Available only from Play Store, AFAIK. And I think I was still on Android 14 last I used it.

I’m not sure if this is of any help, but I had the same issue with Wake on LAN enabled. This was a while ago with an Asus motherboard.

If you don’t need WoL, disable it and it should fix it if your MB is affected.

But if you do need WoL, look at https://wiki.archlinux.org/title/Wake-on-LAN.

The section 5.2.2 Fix by kernel quirks was what fixed it for me.

FlorisBoard with the Material theme.

Tried many, but FlorisBoard’s bugs bug me the least, not that there are many. The one feature I wanted was password manager autofill bar, FlorisBoard worked the best at the time and has been solid since. Material theme is nice too.

Correct me if I’m wrong, but isn’t DDG browser also based on Chromium?

Another vote for Aurora.

Universal Blue in general has been really solid, I remember one time in the last year or two when there’s been any need for manual intervention. And that came with a notification after boot, with a link to instructions that were all copy-pastable as-is to the terminal.

My biased opinion is that most people run Nextcloud on an underpowered platform, and/or they install and enable every possible addon. Many also skip some important configurations.

If you run NC on a bit more powerful machine, like a used USFF PC, with a good link to it, the experience is better than e.g. OneDrive.

Another thing is, people say “Nextcloud does too much”, but a default installation really doesn’t do much more than files. If you add every imaginable app, sure it slows down and gets buggy. Disable everything you don’t need, and the experience gets much better. You can disable even the built-in Photos app if you don’t need it.

Not saying NC is a speed daemon, but it really is OK. The desktop and mobile clients don’t get enough love, that’s true.

I’m talking about the “bare metal” installation or the community Apache/FPM container images. AIO seems to be a hot mess, and does just about everything a container shouldn’t be doing, but that’s just my opinion.

Eikö siitä ole väläytelty, että nettiyhteyksiin pitäisi lisätä kasettiveroa vastaava kustannus? Koska internetissä löytyy tekijänsuojattua materiaalia.

Käytännössä se kai ajaisi saman asian kuin suoraan laitteiden verotus.

Borgbackup in addition to git. Since there’s probably not much data, any cheap VPS could act as storage.

Hyvä pointti! Maksuvaihtoehtoja on tarkoitus kyllä lisätä, kun/jos käyttäjämäärä kasvaa, mutta korttimaksunvälittäjät on pikkusummilla aika kalliita. Toistaiseksi perinteinen lasku on kyllä vaikuttanut enemmänkin toivotulta, ei tarvitse miettiä mihin korttitietoja syöttää.

Sen verran korjaan väärinkäsitystä, että ensimmäisessä laskussa on 30pv maksuaikaa, joka on samalla ilmainen kokeilujakso. Seuraavissa sitten normaali 14pv.

There’s occasionally something buggy, but the last time I ran Windows there were a lot of bugs too. They’re just abstracted away, which Linux DEs don’t do at all.

For me, it’s about choosing the bugs that bug me less. If Windows is working better for you, just run Windows. Internet points are not worth much.

Portability is the key for me, because I tend to switch things around a lot. Containers generally isolate the persistent data from the runtime really well.

Docker is not the only, or even the best way IMO to run containers. If I was providing services for customers, I would definetly build most container images daily in some automated way. Well, I do it already for quite a few.

The mess is only a mess if you don’t really understand what you’re doing, same goes for traditional services.

Most likely, a Hetzner storage box is going to be so slow you will regret it. I would just bite the bullet and upgrade the storage on Contabo.

Storage in the cloud is expensive, there’s just no way around it.

There was a good blog post about the real cost of storage, but I can’t find it now.

The gist was that to store 1TB of data somewhat reliably, you probably need at least:

• mirrored main storage 2TB
• frequent/local backup space, also at least mirrored disks 2TB + more if using a versioned backup system
• remote / cold storage backup space about the same as the frequent backups

Which amounts to something like 6TB of disk for 1TB of actual data. In real life you’d probably use some other level of RAID, at least for larger amounts so it’s perhaps not as harsh, and compression can reduce the required backup space too.

I have around 130G of data in Nextcloud, and the off-site borg repo for it is about 180G. Then there’s local backups on a mirrored HDD, with the ZFS snapshots that are not yet pruned that’s maybe 200G of raw disk space. So 130G becomes 510G in my setup.

I have a feeling you are overthinking the Matrix key system.

• create account
• create password you store somewhere safe
• copy the key and store somewhere safe
• when signing on a new device, copy-paste the key

Basically it’s just another password, just one you probably can’t remember.

Most of the client apps support verifying a new session by scanning a QR code or by comparing emoji. The UX of these could be better (I can never find the emoji option on Element, but it’s there…). So if you have your phone signed in, just verify the sessions with that. And it’s not like most people sign in on new devices all the time.

I’d give Matrix a new look if I were you.

Wireguard runs over UDP, the port is undistinguishable from closed ports for most common port scanning bots. Changing the port will obfuscate the traffic a bit. Even if someone manages to guess the port, they’ll still need to use the right key, otherwise the response is like from a wrong port - no response. Your ISP can still see that it’s Wireguard traffic if they happen to be looking, but can’t decipher the contents.

I would drop containers from the equation and just run Wireguard on the host. When issues arise, you’ll have a hard time identifying the problem when container networking is in the mix.

You install the Google services and Play store from the gOS Apps application, then use them like normal.

Behind the scenes they run in the sandboxed environment, but to the user it makes no difference.

• Open the GUI network settings
• Set DNS to the IP of the PiHole, make sure the “automatic” switch is off.
• Do the above for each active interface (ethernet, wlan) and for both IPv4 and IPv6
• Save/apply settings
• Turn the interface(s) off, then back on
• resolvectl flush-caches just in case

Look at resolvectl dns to check there’s no DHCP-acquired DNS servers set anymore

If you use a VPN, those often set their own DNS servers too, remember to check it as well.

Viestit on kyllä Whatsappissa salattuja, totta. Salausavaimet eivät vain ole käyttäjien hallinnassa, vaan Metan palvelimilla, joten halutessaan Meta saa kyllä viestien sisällönkin purettua.

Voin toki olla väärässäkin.

Ja eihän WA oikeastaan ole e2e, koska avaimet on Metan palvelimilla.

Se, että Meta pääsee viesteihin ei ole tuntunut hetkauttavan ketään.

Niin, tuohan ei ole mikään uusi juttu. Päinvastoin, päästä-päähän-salaus on se uusi juttu…

Mutta tämän asetuksen myötä viranomaiset saisivat suoraan pääsyn kaikkeen viestintään, ja kaikki viestit sitten joku tekoäly kahlaa myös läpi. Lähettää kuvan lapsista uimassa mummolle, niin kohta on virkavalta oven takana.

Ja noin 5 minuuttia käyttöönotosta takaportti on käytössä kaikilla jolla on varaa maksaa lahjuksia.