Thanks! Luckily it has been pretty quiet since the bot issues and security issues. At this point it’s occasionally checking for Lemmy and server updates, and keeping an eye on server storage. One of the recent Lemmy updates fixes the database storage ballooning though so it will probably be a while before storage is an issue.
Split beam torque wrenches are where it’s at, especially for home use where it’s going to sit for long periods of time. Split beam is easier to set, and you don’t have to leave it at 0 when not in use. I have ruined many traditional clickers because I forgot to set it back to 0 for storage, then it sits like that for months.
They aren’t as cheap as a traditional clicker, but they are so much better.
Some satellites and rovers have used Radioisotope Thermoelectric Generators (RTGs), which are very different from a nuclear reactor. They use polonium-210, which generates heat, and that heat is converted to electricity with thermocouples. They are low power and inefficient.
To my knowledge no satellite, with an RTG, has ever used ion propulsion. Few interplanetary satellites have ever even used ion thrusters. Dawn, Hayabusa, and Deep Space 1 are the only I can think of, and they all used solar arrays.
Ion thrusters are super efficient, but produce extremely small amounts of thrust. They aren’t practical for getting large spacecraft to Mars. These proposed nuclear engines produce large thrust while have efficiency somewhere between regular chemical propulsion and ion propulsion.
For large instances pictures is probably the bigger consumer of space, but for small instances the database size is the bigger issue because of federation. Also, mass storage for media is cheap, fast storage for databases is not. With my host I can get 1TB of object storage for $5 a month. Attached NVMe storage is $1 per month per 10 GB.
For my small instance the database is almost 4x as large as pictrs, and growing fast.
If you have open registration you should reduce the account creation rate.
Ah, I understand now. At least 1 person on this instance has to be subscribed to the community on another instance for it to federate and show up here. All the communities that show up in “All” on this instance are ones that have been subscribed to by at least 1 user on this instance. It is one of the downsides of federation on a small instance, you don’t have a very good “All” to see popular content form communities you aren’t subscribed to.
There are some tools out there that will force federation with all communities, but the problem with that is it blows up storage requirements.
There may be some instances that manually defederated during the whole bot situation. I know there was a tool someone made that automatically updates the defederated list, but I already verified we were off that naughty list. So, it would only be instances that manually defederated that we may still be blocked on. In that case we’d have to message the instance owners and ask to be removed from the list.
I’m not sure I’m seeing any less communities though, could just be general federation issues. Any specific instances/communities you think are missing?
It runs /e/OS, which is very much a privacy focussed OS.
I don’t think most people even know honeybees aren’t native to North America. Native bees are the ones at risk, and non-native honeybees aren’t helping.
Been using Zoho for years, cheap and reliable.