irotsoma

Try a few live disks out. See what works best with your hardware and workflows. I like Fedora with KDE Plasma, personally. But I prefer RHEL based to Debian based stuff and I don't like the direction Ubuntu is beimg taken for monetization.

Yes it's defects in the ingress-nginx controller package.

Yes, but punish the government and those who support those governments. The majority of people who live in a fascist country do not agree with the government otherwise fascism wouldn't be necessary.

I live in the US and I don't agree with nor apologize for the anti-trans, anti-women, anti-immigrant, and racist policies the federal government has recently implemented. In fact many policies directly affect me and my wellbeing.

I voted against them, but unfortunately we weren't given an option to vote for something better because of the way things work here. And many of these countries don't even have that. Nor do I think anyone else who lives in or visits the US should be punished for the actions of its government. Same goes for any other country.

And in this case it looks like it may just be someone visited one of those countries sometime in the past, though details are scarce. I get then need to sanction people involved with the bad stuff, but people who just visit or live there with no other connection to the bad stuff is a little extreme. Especially since contributing to this project, for free, is not producing profit for or supporting any government.

I think its just that the language having built in licensing is a newer concept as opposed to just having a companion document. And MIT and Apache are the licenses the pieces of the language is licensed under, so they made those default. That way it's a conscious decision to make it more restrictive.

Yeah definitely makes sense to me in stomach and vagina and similar areas. Just wasn't sure if in was missing something on the face. Maybe in combination with something that was probiotic I guess, but I don't see any of that. So prebiotic without probiotic treatment seems risky.

I think it's unlikely to be enforced for normal use. If you use them for spam or to store a ton of data or some other abusive usage, they might shit down your accounts, but it would be pretty customer-unfriendly to do that for someone with just two accounts and not abusing it. Most privacy respecting services are too young to have gotten to the screw customers, only short-term profit phase of capitalism.

I don't think it's Rust exactly. I think Rust is just newer and this attracts developers with less experience with licensing. It's not really something developers want to think about very much so they often just use the default. Heck, most code on github, etc., didn't have any licenses at all for a really long time until businesses realized they couldn't use the code without them due to copyright laws being applied by default but patents not being default in many countries, etc.

There are consequences to using copyleft as opposed to more permissive libre licenses, and vice versa, that may not be well understood by a lot of developers in general until they get into a situation where it matters. Either their code can't be used by people they wanted to sue it, or companies are abusing the code without proper attribution, etc.

Censorship isn't bad in itself. It's a necessary evil just like imprisoning someone who imprisons others. Both are removing freedom, but one was for the benefit of an individual and the other is for the benefit of everyone else in the society. Regulation of freedoms is always necessary.

Problem is these days the far-right tries to say all regulation is too costly. But if one innocent person loses their rights compared to millions of innocent people losing their lives, its a big difference. Similarly, someone abusing their right to speak losing their right is not the same as someone using their right to speak responsibly, losing it.

Depends on what you're backing up. Is it configs for applications, images, video, etc? If it's application configs, you can set up those applications in a virtual machine and have a process run that starts the machine, restores the configs, and makes sure the applications start or whatever other tests you want. There are applications for doing that.

If it's images or videos, you can create a script to randomly pick a few, restore them, and check the integrity of the files. Usually just a check of the file header (first few bytes of the file) will tell you if it's an image or video type of file and maybe a check on the file size to make sure it's not an unreasonably small size, like a video that's only 100 bytes or something.

All this seems like overkill though in most scenarios.

Last time I checked, it depended on where you live and if the laws in that area require them to allow you to delete certain information. It's on the a cache thing, it's in your account. You can set up a new account, but if you use other Meta applications like Facebook, WhatsApp, Threads, etc, you may have to abandon those as well.

Might be possible to use a VPN or something to pretend to be in a country that they allow to have more detailed deletion of data, but I'm not totally sure if it's just your current location or if the account has to have been created in that location or of you can change your account-level location, etc.

Generally the key fobs have a circuit and antenna inside and the circuit has a code that it broadcasts when it is near the transceiver. Some systems are more complex, but at the lowest level the system disrupts a magnetic field around the transceiver in a certain way to generate the code or is powered up by the transceiver and transmits the code using that power. That way no battery is required and it can fit inside a thin card or fob. Some older ones have a very small battery to increase range or create a more complex or modifiable code or for proximity use rather than touch.

That code is then authorized or not to open the door in the security system. And yes every time the fob is used, it is logged. And depending on if the fob has a battery, it is possible it tracks leaving. If they don't have to touch the fob to a panel and just need to have it on them, then it logs any time they approach the door regardless of entering or leaving. If it requires touching or bringing it close to a panel and they don't have to do that when leaving then it probably doesn't log them by proximity.

Whether or not the log has the person's name or just the code or ID of the fob depends on how old or cheap the system is. But there's definitely some document somewhere that lists the peoples' names and which fob they were assigned if it's not in the system. So it's easy enough to find out.

Any system that has the same code in every fob would be either super old or super cheap and unlikely to be used on secure doors. Having unique codes means that if a fob is lost or stolen it can be deactivated among other things. Which is a no-brainer for security if there is no real significant cost. The only reason older systems didn't is because the tech couldn't create long enough codes on the circuits that existed. And super cheap systems don't want to create too many different codes since it's cheaper to mass produce the same one over and over. Basically why car fobs can often open other people's cars. Either they're old or the car company's too cheap and it's not their security at risk, so they don't care.

I'll take one. Feel free to DM me.