I heard some people say theyre the same thing, but others are adamant that they have different meanings. Which is it?
I actually do have glasses, I just never bothered learning about any of the technical details behind my lenses. Optometrist measured my eyes, I chose the cheapest frame the store offered, came back a week later to pick up the glasses and that's about it.
yes, it's that.
This post reminds me of those "attack helicopter" jokes from 2016, except this time it's actually funny and not hurtful
It's true what you say about volatility. It's not just the internet, it's everything digital, even offline storage.
A few months ago I was about to sell/give away a bunch of old childrens books that I had, my reasoning being that I will never want to read them again, and even if did want to for whatever reason, I could always find ebook versions of them.
Ultimately I decided to keep the books -- what if, sometime in the future, I wanted to share these books with my (potential) children? Would all of these books have been preserved in digital form? Would I rather be giving my children a physical copy that I owned and read personally, or emailing a PDF? Physical media holds real value.
I've seen some niche bands release (free) official torrents of their music on a certain piracy website. It's kind of surreal. Just goes to show that piracy is and always has been about sharing culture
The trick is to give up and just shuttle files from computer to printer via usb stick
You can lock your password database with a key file (this is a standard feature in keepassxc) and transfer the key file once between devices via sneakernet (microsd or usb drive). That way even if someone intercepts your database file, AND knows your password, it is still virtually impossible to crack. Should be a good enough solution, unless you are quantum-tier paranoid
Marginally better than using discord itself as your password manager (also a true story!)
I mean he's not wrong about paper being more secure than password manager (provided you have good physical security and trust the people you live with)
Transcript:
DANGER
DO NOT OPERATE
THIS EQUIPMENT, SWITCH, VALVE, MACHINERY,
REASON Fucked.
Open your eyes, have a think about it
look
SEE ALSO OTHER SIDE
I've just been playing around with https://browserleaks.com/fonts . It seems no web browser provides adequate protection for this method of fingerprinting -- in both brave and librewolf the tool detects rather unique fonts that I have installed on my system, such as "IBM Plex" and "UD Digi Kyokasho" -- almost certainly a unique fingerprint. Tor browser does slightly better as it does not divulge these "weird" fonts. However, it still reveals that the google Noto fonts are installed, which is by far not universal -- on a different machine, where no Noto fonts are installed, the tool does not report them.
For extra context: I've tested under Linux with native tor browser and flatpak'd Brave and Librewolf.
What can we do to protect ourselves from this method of fingerprinting? And why are all of these privacy-focused browsers vulnerable to it? Is work being done to mitigate this?
Fun fact: Torx screwdrivers are compatible with Torx Plus screws, but Trox Plus screwdrivers are only compatible with Torx screws that are one size larger
Context: LaTeX is a typesetting system. When compiling a document, a lot of really in-depth debugging information is printed, which can be borderline incomprehensible to anyone but LaTeX experts. It can also be a visual hindrance when looking for important information like errors.
Context for newbies: Linux refers to network adapters (wifi cards, ethernet cards, etc.) by so called "interfaces". For the longest time, the interface names were assigned based on the type of device and the order in which the system discovered it. So, eth0, eth1, wlan0, and wwan0 are all possible interface names. This, however, can be an issue: "the order in which the system discovered it" is not deterministic, which means hardware can switch interface names across reboots. This can be a real issue for things like servers that rely on interface names staying the same.
The solution to this issue is to assign custom names based on MAC address. The MAC address is hardcoded into the network adaptor, and will not change. (There are other ways to do this as well, such as setting udev rules).
Redhat, however, found this solution too simple and instead devised their own scheme for assigning network interface names. It fails at solving the problem it was created to solve while making it much harder to type and remember interface names.
To disable predictable interface naming and switch back to the old scheme, add net.ifnames=0 and biosdevname=0 to your boot paramets.
The template for this meme is called "stop doing math".
I don't mind people making and sharing AI pictures for fun, but if you sell those pictures, that's kinda cringe tbh.