Could have just used class E addresses, at least then it would look intentional insead of brainless.
- 2 Posts
- 289 Comments
The instance I’m using (
programming.dev) offers five custom UIs and they are mostly available under subdomains by the first letter of the UI name:
Tesseract (t.programming.dev)
Photon (p.programming.dev)
Alexandrite (a.programming.dev)
Mlmym (old.programming.dev, because this one tries to mimic old Reddit UI)
Voyager (v.programming.dev)Makes sense to use a lower level domain for that, I think.
TwilightKiddyto
Linux•Why call it full-disk encryption when the EFI partition has to be unencrypted?English
1·23 天前If you do this, be sure to make an image of your EFI partition and/or keys and keep it somewhere safe along with whatever is needed to restore the partition. Because if something tempers with it, your computer will stop booting because sighed hashes no longer match the ones calculated and you’ll be locked out of your own system without some sort of way to restore the partition to a safe state.
TwilightKiddyto
Linux•Why call it full-disk encryption when the EFI partition has to be unencrypted?English
7·23 天前As bad as secure boot is, that’s exactly the use case for it. Frankly, you can both swap the CD and solder a new BIOS flash if you are really interested in boot poisoning, the latter is just a tiny bit harder to do without some sort of trace.
TwilightKiddyto
Linux•Why call it full-disk encryption when the EFI partition has to be unencrypted?English
11·23 天前Mainly because then the manufacturer decides on how your stuff is encrypted, no likie.
TwilightKiddyto
Linux•Why call it full-disk encryption when the EFI partition has to be unencrypted?English
6·23 天前Well, something has to be. You can have your EFI partition on a separate drive and then the actual drive will be fully encrypted. It’s just as good as we can get, the algorithm for decrypting the data obviously can’t be encrypted.
I think there are implementations with encryption logic stored in the BIOS or on a separate chip, but don’t quote me on that. And even then, the decryption logic itself will be unencrypted, because, as it happens, computers can’t run encrypted code.
So, you just want a prebuild? Just as with consoles, you still need to do maintenance. Yes, you can neglect it for a couple of years, but then you start noticing that your thermal interface is not as good anymore or that your heat exchangers are now more dust than metal. And I find full-sized computers easier to maintain, as they are so easy to disassemble, contrary to consoles.
Also, if you want VR and have the money for it, it’s probably a good idea to buy a beefier machine. VR is a bit hungry for system resources (depending on the title, of course), standalone headsets don’t provide nearly as good of an experiece as a proper PCVR.
What is a PC for you, though? Steam Frame is a full on computer running Linux, as well as Steam Deck. Nothing prevents you from running basically anything on them. But the same could be said about your MacBook that you already own.
May be this could help?
https://lvra.gitlab.io/The LVRA Discord also consists of a lot of very helpful people.
Yes, but the latter is easier to read. I know what the former is, but my colleague could definitely use additional brain cells. And if they don’t understand it, I’ll be the one explaining. That’s also the reason for not using abbreviations besides the most common ones in variable names. Always assume your code will be read by a typewriter monkey.
Well…
for ((;;)) do # stuff done
TwilightKiddyto
Japanese Language@sopuli.xyz•I Made a Super Fun, Open-source Platform for learning JapaneseEnglish
3·30 天前Well, I’m a LibreWolf + uBlock hard mode guy, but that’s, I think, the first time one of those anti-bot systems just outright crumbles without any even potential way to fix it. When requesting a challenge the server responds with a 708 code, which is not a standard one, so, I have absolutey zero idea on how to make it happy.
If you can’t fix it, I propose you replace it with something like anubis.
Another funny way to combat bots that does not disrupt the user is honeypotting bots with a hidden link on the page that just blacklists the IP address of anyone touching the endpoint.
TwilightKiddyto
Japanese Language@sopuli.xyz•I Made a Super Fun, Open-source Platform for learning JapaneseEnglish
4·1 个月前¯\_(ツ)_/¯

From what I understand, the purpose of the community is to find discounted games. Even if the developer/publisher is posting about a discount on their own product, they are contributing to this exact purpose. Making them work for the ability to post will probably only turn them away. Also, this system may encourage people to create throwaway accounts for posting their own games.
Making it a public poll also feels bad. Obviously there are more non-developers here who won’t be very considerate of what such a change means for the developers.
Current Reddit version of the rule practically boils down to “disclose yourself, engage at least a little bit, don’t flood”, which more or less tries to prevent any harmful behavior. The proposed change instead turns it into a rule that forcefully makes developers work for the community they are already contributing to.
On the other hand, if you want to discuss @[email protected] specifically, they already broke the rule. This account was clearly created to post promotions for their game exclusively and does not engage with any community they post to nor openly discloses who they are (should be fairly obvious judging by the username, but still).
And there is another point to be made. Rules are not accessible fully on Lemmy and you need to know that this is a copy-paste community from Reddit to know the rules. Instead of changing them, I think it’s a good idea to make the rules fully accessible here first.
I think this image is over 10 years old by now. It was created before “vibe coding” was a thing.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
No problem! I can just kill the process in the…shit.
It says in the description that this is a version with minimal changes that exists because uBlock is not available in China. It looks like the source is located here: https://codeberg.org/lanticy/cBlock
I wouldn’t use it if you have the ability to use the original uBlock, but if you have no other choice, this looks plausable.
Yes! We should have swapped the names for Iceland and Greenland so long ago!








Stop teaching people how to scream, please.