Edit: I was wrong and mixed up passkeys with something else. Passkeys I think are still better than desktop totp apps because at least they work with secure hardware on the platform.
Slightly off topic but desktop 2FA apps kind of kill the point of 2FA.
2FA protects you by ensuring that even if your computer is compromised your account will have a layer of protection in that second factor “aka something you have”.
If you have that on your desktop, you might as well not have it.
If you find 2FA off of your desktop annoying I recommend looking into passkeys. Open standard and less annoying. Just not well supported.
I want to make a distinction between scraping and archiving here.
You don’t need to do anything to ensure your content is “scrapeable”. Just post your content on the fediverse and it is available to scrape. Anyone can do it. This being said unless someone goes out of their way to save what they scrape eventually as your content ages the only copy will be on the server that it originates from. I believe all posts are stored on the instance where the community lives. I believe all comments are the same the difference being that your instance also stores a local copy of your comment. I could be wrong there though.
Archiving is different. Archiving is providing a long term store of your content. That is harder. If you run your own instance the comments you put on the communities that live on your instance are safe. Anywhere else, you are subject to that instance just dying or selling out. You would need a specialized tool to take a “snapshot” or something. Maybe adding the post thread to archive.org could work. It’s messy in any case.
I hate to break it to you, but federated services are basically impossible to protect from scraping. The whole idea is openness and federation.
The only reason why places like Twitter and Reddit try to prevent scraping is so they can sell the data for profit.
If you post stuff publicly anywhere it will be scraped. On the fediverse it will be scraped via the open and federated APIs. On proprietary platforms it will be scraped via the proprietary paid APIs.
I just use the Eddie GUI. It works well for me and is simple to use. If I wanted anything more complicated I would just download ovpn profiles and use raw OpenVPN.
Just think of the NAS like a desktop that you ssh into. The only difference is that you install the server version of the distro. If you know how to use a desktop Linux box and configure it via the command like you can do so with a server. It will be the same except over ssh.
Hardware wise, normal desktop parts are good enough to build a NAS. You don’t need to buy anything special that is NAS specific. The only exception might be the case. If you want a lot of storage the case should be able to accommodate that. Some desktop cases don’t have 3.5” drive slots anymore.
I would think that any immutable linux distribution would be suitable. Just configure it with the services that you want. Is there any special need that you specifically need?
NFS over WireGuard is probably going to be the best when it comes to encrypted file shares without the need to set up Kerberos. Just set up the WireGuard tunnel and export over those ips.
Good but slow. Zypper has nice features but for some reason it can only download one package at a time. There is a GitHub issue about this that has been around for years.
Before anyone says UK I’m going to say they’re too bulky to be worth it. A usb charger for a UK plug is just so big and bulky that it’s not worth it. The Schuko plug falls into the same category.
If we are allowing future potential plugs I would argue for IEC 60906-1. It’s basically the same as Swiss type J but with very minor changes.
In addition to what other people are saying there are additional factors like minimum layer time. If you find that layers with less material are being done slower it might be because of this.
In general a well tuned profile will prioritize quality over speed. You can bump things up or use a more aggressively tuned profile but your results may vary.
You could preemptively write the policy if you know the context and policies you want to apply. I just don’t think it’s worth the time when you can generate a policy with two commands.
Fair. But audit2allow makes it really easy to add support for apps without policies. For custom in-house apps I use this to spit out some nice policies that can be rolled out.
You’re right. Yah. Still at least those use “secure element” equivalents at least.