Thanks, that’s a bit more meat. Should probably look for their publications.
Thanks, that’s a bit more meat. Should probably look for their publications.
Paywalled.
Latest Nature explains it was not superconductivity.
Thanks, good info. Never had any problems with pfsense or opnsense with Intel server NICs personally. Other than being fried.
I had no problems communicating a higher limit. They are not AWS but you can get 100s of instances.
Happily, I’m abnormal that way. I also dabble in PV DIY. Building houses from scratch, no. Servicing a modern car is also not worth it. Sadly, no open source EVs yet available.
HA for personal MTA is way overkill, just run a second instance with higher MX record value. Antispam is a given, backups are snapshots, maintenance is just system updates. Of course, you could just run an appliance which does it all for you. I’d say it’s way easier than in 1990s.
Email in the 1990s and email in 2020s is the same if you’re running your own MTA.
Your profile contains your post history to many of your communities.
I’m pointing out that if you’re going to the trouble of hosting your own instance you could as well allow some convenient number of random users to register. It would erase most of your signal and help distribute the load and exposure to specific legal compartments.
Your profile is also public. An instance with few 10 subscribers erases much of the information.
It should be not part of Lemmy’s server side code. Actually even integrating current image support is ill advised. It should have been an optional microservice.
Many are waiting for their data takeout requests to complete before doing the same. And to follow up with GDPR requests/GDPR deletion requests.
All to improve their quarter numbers pre-IPO.
Lineage OS user. Don’t care.