Oh, we just need a bit more surveilance, more culture war and more right-wing brain-rot pushed on us and then the EEP can finally argue that the only way for a stable majority is cooperation with the far-right spectrum from insane nationalists to outright nazis.
That kind of enshittification of politics works so well in the member states so it will work for the EU, too.
Right-wing populist and neo-fascist won’t close one of the main pipelines for right-wing and fascist recruitment? How surprising… 🥱
Even if maintainers wouldn’t just package stuff themselves. How many formats do you need to cover 95% of the eco system? More than 3?
Don’t be rediculous. By then Debian will be on 258 at best…
Oh, no! Yet another field I will simply leave blank like all the others.
You snapshot them separately, with snapshots stopping where another subvolume starts. Have a problem booting? Copy the latest /-snapshot. But if for example /var/log is a separate subvolume it persists and you can look up what was wrong.
My setup right now has subvolumes root(mounted to /), home(mounted to /home) , logs(mounted to /var/log), snapshots(mounted to /.snapshots), pacman-cache(mounted to /var/cache/pacman) and swap(for the swapfile obviously).
I do snapshots of root, home and logs (landing in snapshots) regularly that don’t require much space (only the difference between on subvolume and its snapshot uses real space in btrfs) and which can all be restored together as well as separately, while losing the temporary data in cache and swap is not problem.
And you can also transfer the snapshots somewhere else as backup (into another brtfs filesystem or as a file), including just transfering the difference from the last one as an incremental backup.
sure it might be possible to install an OS into a btrfs subvolume without wiping other subvolumes, but do I wanna risk it?
There is neither a “might” nor a risk. Subvolules behave like partitions with the only actual difference being that they are not fixed in size but all share the same space.
I would suggest starting out with nginx and just setting up a basic homepage for yourself. Even if it’s just a title and background… doesn’t matter.
This way you have to solve problems like how to reach your page from the outside (your own domain? DDNS? etc) and also how to set up Certbot for HTTPS (which a lot of services will also require later). That already includes setting up kind of parallel configurations (one for http that than redirects to https, one for https) in nginx. And you will do both later again, because you use the same dual setups to serve two different websites on the same IP depending on which the addressname a visitor entered and also will redirect some of them (or sublocations of your page) to other services that provide a webinterface as a reverse proxy.
No.
Let’s Encrypt checks if you have control over the server the name eventually leads to, usually by providing you with a token that you put on your server for retrieval. The way there, including the IP, is irrelevant.
These people have no clue how to get around these DNS filters.
But not thanks to the virtue of some effective blocking but just a lack of knowledge of the average user…
I have used several of those cheap routers over the years. And they simply can’t block you from using encrypted DNS (unless they want to create giant blocklists and want to play wack-a-mole with DNS servers…).
So all they usually do is very low tech like ignoring the DNS you set in the router configuration and reroute it (or not providing such configuration in the first place). But they can effectively ony do so with unencrypted DNS.
With encrypted DNS they could at best try to block the default port used by DNSoverTLS but that still leaves DoH. And they can’t block that because it’s just regular encrypted HTTPS traffic (with the DNS quesry inside).
Iirc even Windows allows easy configuration of DoH nowadays (and for much longer if you were ready to edit the registry) where you can simply chose between unencrypted, DoH only or encryption preferred if available.
The only thing they can realistically harcode is the DNS server their router’s DHCP provides.
Just configure devices to not use that setting, also use DoH or DoT (which you should do anyway, not just to circumvent your router’s settings).
make sure all of your devices are secure using encrypted DNS and encrypted traffic
Which is so easy it really should be the default nowadays yet sadly isn’t.
Cool… if they won, is there now some money to invest in infrastructure or personal to prevent flatpak fuckups?
In light of recent events I’m referencing bullshit like just uninstalling nvidia drivers as part of a messed up upgrade. And the fact that they finally solved it yesterday resulting in download speeds of ~5kb/s for a 100+mb file because everyone and their grandma tried to finally fix their systems at the same time.
Take a look at the config file (/etc/radicale/config). It’s extensively commented. Although you barely need to change any defaults for regular use.
Just create an htpasswd file (with htpsswd, apache-tools or just any of the one million available online generators) and edit two lines under [auth] to read type = htpasswd and htpasswd_filename = <the location and file you created>.
And you can start (and enable) Radicale via the systemd service usually included in the installed package. (Or for early testing just start the server manually… radicale starts it with the defaults from the config file. You can also configure everything with parameters but that’s an insanely long list (radicale --help if you are interested in seeing them)…)
The webinterface to login will be available (by default settings) under http://localhost:5232/.
All you have to do then is change the config so Radicale listens on the server’s IP instead so it’s available in in your network. (Plus the usual stuff of making it available from the outside if you need that like for any other sevice)
And any calendar/contact software will bring a wizard that guides you through the process of sync’ing, usually just asking for an address to reach your server, as well as user and password.
EDIT: I looked up the defaults and you can skip all the autehntification stuff in the beginning. By default just anyone can access the webpage at port 5232. So you can just test it and only bother with authentication later (definitely when you plan to make it available from the outside, for example to sync phones).
With radicale, do I need to install some other somewhere in order to use it?
No, you just need to install Radicale. That’s it. calDAV and cardDAV are widely used formats available as an option with basically any calendar.
Can a self hosted calendar still send and receive invites to other calendars?
Oh, I see your problem. You don’t host your calendar. You host a service that is used to synchronise all the regular calendars you already use over different devices.
Or are you at the moment using Google’s calendar in browser only?
I am so terrified of a future where people
havehallucinate their own perfect AI companions and no longer understand that they need any actual human friends.
But those Arc cards actually look good (for the low budget segment they are in that is…) and are mainly held back by lackluster drivers. So I get the decision.
Would be nice if this was the only (or one of just a few) Realtek chips that are a fucking mess…
There might a common problem with those Realtek devices but I fail to find it. 😅
I would assume people running a modern kernel on an orignal 32-bit first generation Pentium machine don’t need such an excuse as they have to do it constantly already…
I’m pretty sure the unmodified/-optimized kernel doesn’t even fit the RAM of 1990’s Thinkpads.
But our corrupt politicians are right-wing so they stand obviously above the law (and any form of consequences)…