





Nvidia doesn’t support vaapi, so when I still had an nvidia card I needed to install a compatibility layer like this. You might have more problems if you want to use a Chromium based browser though
Jujutsu (which is compatible with git) has a nice conflict resolution flow that doesn’t break you workflow.
Conflicts are encoded into the commits, so that there is never a weird in between state that you have to deal with immediately before being able to do anything else.
Then you can use Jujutsu’s easier history manipulation to resolve the conflict in the conflicted commits.
https://steveklabnik.github.io/jujutsu-tutorial/branching-merging-and-conflicts/conflicts.html
And you could always jj undo if you did something you didn’t want to.
With Jujutsu (which is compatible with git), you can just
jj undo
That’s VSCode
I thought the main reason was that they changed the license


For .de you don’t need any of that domain privacy stuff. .de domains don’t reveal anything over whois except the company you registered the domain at (and DNS servers, but domains are useless without that). You have to do some special request to get more than that. Idk how hard it is to make such a request though
https://webwhois.denic.de/?lang=de&query=example.de
https://www.denic.de/service/whois-service/anfragen-dritter-zu-inhaberdaten/


Misskey and Akkoma have had them for years


It says it IPv6 ready but doesn’t even have any AAAA DNS records.
It does use TLS 1.3, but only AES 128 bits for me.
deleted by creator


But apparently btrfs can get corrupted if it unexpectedly loses power?
Afaik this is only a problem if you use RAID 5 or 6. Otherwise it’s as solid as other CoW filesystems like zfs.
https://btrfs.readthedocs.io/en/latest/btrfs-man5.html#raid56-status-and-recommended-practices


The Wikipedia page doesn’t sound too bad, but IANAL.
The regulation linked from the wiki article only includes the word “age” three times and actually states:
[…] this prohibition should not lead the provider of the online platform to maintain, acquire or process more personal data than it already has in order to assess if the recipient of the service is a minor. Thus, this obligation should not incentivize providers of online platforms to collect the age of the recipient of the service prior to their use.
Haven’t looked at it any more than that, but it sounds like it’s already been in effect for ~2 years?


It’s a European Citizens’ Initiative. If it gets enough signatures, the European Commission has to discuss it and make a decision what to do about it.


Same entire thread on Mastodon: https://grapheneos.social/@GrapheneOS/114670995130379882
Nothing wrong with that of course. There are advantages to making your own things.
FanFicFare isn’t perfect either. For cloudflare it supports using FlareSolverr, but from what I heard it doesn’t always work well. Alternatively it can open the pages in your browser and grab the content from the browser cache.
I mainly like that it’s available as a Calibre plugin and that it supports just about any fan fiction site.
Is there a reason you wrote your own instead of using FanFicFare? Just curious


They renamed it on other platforms (apple) in September 2024 https://www.neowin.net/news/microsoft-is-renaming-its-remote-desktop-app-on-certain-platforms-and-people-are-livid/