0x4E4F

Why make one arm human 🤨?

You should also probably try and see if the same thing happens in a VM. The flash drive might be failing and I don't think Void does CRC checks of files when copying them... definitely not when funning them, like the installer for example.

EDIT: I remember the installer bringing me back to the partitioning setup, but that's because I partition manually, not through the Void installer, so the installer thinks that that step is skipped. No worries though, just go to the end of the installer setup and continue with the provided settings. If an adequate target partition has been set, it will install Void.

Yep, or an eagle of some sort...

libera te tutemet ex inferis

Imagine hearing that shit 😬...

Darn it, won't get anything from pirate santa this year 😔.

And the danger of a lot of people on a single instance is really exaggerated. If things go badly on, say, a Lemmy instance that most people are on, they can just move to another one with the same features, same UI, and similar access to content.

See, for new users, a slow glitchy instance means "fediverse don't work like advertised"... sorry, but if you haven't noticed, the techies are the ones that stayed on Lemmy. Everyone else pretty much left it after the big Reddit migration wave hit it. Glitches, bugs, unstable instances, instances going dark... that's just not for everyone. Yeah, we understand the reasons, so we stayed, but for normies, this was generally a bad sign and just left.

That's why it's advisable to distribute the load, so we don't get into these same problems, which of course just gives the fediverse a bad name.

New York as well I believe 🤔.

Techies will care, most people won't. Niche communities will still be on Reddit. It's just easier and data never gets lost (as has proven to be the case many times in the fediverse).

I repair almost everything and just love to tinker with gadgets and tech in general... repurpose/reuse old things, make beter versions of them, etc.

Simple example, all of my old audio equipment now has Bluetooth, an MP3 player, an aux input, a USB port (for MP3 playback) and an SD card reader (also for MP3 playback)... oh and let's not forget the FM tuner that comes bundled with those thingies 😂. Don't use it, but still, it is a nice option to have at your disposal 😉.

What, they don't offer binaries 🤨?

Well, at least there is one thing that makes building on Void easier. xbps-src works with templates, so you could just write the template or write on GitHub for help from someone in the Void community. I've asked for help many times and people are usually very helpful ☺️. Once you have the template, updating the VST is a matter of just chaging a few things in it (version, hash, etc.) since things like UI dependencies or libraries don't change that often in releases, those are major changes and usually come with a prior warning by the developer. Meaning, you could just make the template and just change the version numbers and hashes, recompile it and most of the time, that will be just that, bam, you're up to date ☺️. Sure, there are major updates, but let's face it, there are very rare. And, you can share the template with others on the official void xbps-src repo or your own repo, however you like 😉. Hell, you could even share the binaries so that other people don't have to go through the trouble of compiling them manually 😉.

and I will not ask for the meaning of 20047 or the Englishy greenish color 😉

It's NO in ASCII and I'm not a native English speaker... and this thing doesn't have auto correct, underline or suggestions 😒 (Jerboa).

The correct way to share a community on Lemmy (so that apps recognize it as a Lemmy community) is with an exclamation mark, as in your last example. The search in Jerboa (as is with other apps) is broken, doesn't work like it should. Use the web UI search on your instance, you'll find the community.

Just use nofail in the fstab.

Really? Didn't know about this switch, thanks for the info ☺️.

If your fileshare is accessible to you, it is also accessible to malware running as your user. Mounting the share via a filemanager doesn't change this.

It does, it's not mounted on boot.

In general, mounting a netwok lication at boot is a bad idea in any OS, unless you know exactly what you're doing (all of the rigs that mount it are on a separate network, limited internet access through specific ports, none of them have users working them like daily drivers doing whatever on them - bascially, a server cluster is the only scenario that mounting a network share on boot makes sense). Why do you think that nowadays Windows users generally avoid mounting shares as network drives, but instead access them through shortcuts. The exact same reason, except in Windows, the share is mounted on logon (as far as I know, I might be wrong and the share might be mounted at boot, just reports that the share is missing when a user logs in). It's safer if the location of the share is not known at boot, period. When the user logs in and decides to copy something to the share (unknow period of time after the login), that is a different story. Sure, well written malware will find a way to replicate itself and infect other rigs even if you don't mount the share at boot, but at least you're shielding yourself from the badly written ones.