In the Green Zone
- 0 Followers
- 0 Following
- 8 Posts
How's South Africa These Days?
Huh...I guess they're not all bots. Some of them might just be freelancers LARPing for pay.
Every TV show or movie with a story about rich people doing weird, messed up stuff is probably happening IRL to rednecks in some poduck shitberg town on a smaller scale.
Every TV show or movie with a story about rich people doing weird, messed up stuff is probably happening IRL to rednecks in some poduck shitberg town on a smaller scale. - Lemmy Today
I grew up in a shitberg redneck town. Succession? Could be Bobby Dave’s HVAC Empire. Beast In Me? Country-ass redneck issues in NYC. It goes on and on. As with Greek tragedies, very little separates the shepherd and the king.
What's up with Google Earth Pro in OpenSuse TW? Is this a common occurrence?
What's up with Google Earth Pro in OpenSuse TW? Is this a common occurrence? - Lemmy Today
Hi all, I’m doing my first round of distro hopping, looking for something stable and falls into the “just works” category. I’m not looking to tinker. Trying to see if something will tempt me away from Mint, and would like the added security of a rolling release. I’m testing out OpenSuse TW in VirtualBox and the second thing I tried to install was Google Earth Pro, which I do use regularly enough that it’s maybe not a dealbreaker, but it’s a check point for testing out a distro. Short version is that it’s a mismatch of repos and libraries and the flatback says no-go because of a bad executable stack. I’ve spent days off and on trying to reinstall and fix in a way that works based on rare and meager instances years ago of people running into the same problem. Nothing works and I’m apparently not advanced enough of a Linux user to wrap my head around how to approach this other than stumbling down a few paths that don’t work. Is this something to be expected with TW? Or is this somehow unique to Google Earth Pro? Or is this a VirtualBox issue? (it shouldn’t be). Any help is appreciated.
Turkey Tonkatso Ramen. When the leftovers are better than the first run.
Understanding _nomap and the Wifi Positioning System
Understanding _nomap and the Wifi Positioning System - Lemmy Today
Based on a recent post now deleted from [email protected] [/c/[email protected]] [https://lemmy.ml/c/privacy], which was itself based on this article [https://www.amoses.dev/blog/wifi-location/], it sounds like there’s some misunderstandings and misconceptions about how Wifi Positioning (WPS) works, and how to mitigate it to the best of one’s ability. First off, Apple and Google are the primary culprits here. Every time someone who has not adjusted their settings on their phone and has location data on connects to a wireless access point of any kind, Apple and Google collect that data and location data. This is 100% different than wardrivers, who go around scanning and mapping SSIDs and BSSIDs. After research from the University of Maryland [https://www.cs.umd.edu/~dml/papers/wifi-surveillance-sp24.pdf] showed how deep the WPS database goes, they suggested the following ways to mitigate having your wifi mapped: -Rename your network to end with _nomap, so like “FBISurveilanceVan_nomap” would be how to do that. Larger WPS operators honor it as an opt‑out because these are automated systems. This cuts you out of many crowdsourced location DBs. This is not foolproof, but it will handle 99.9% of any use cases from anyone here. -> This doesn’t prevent wardrivers from indexing your wifi. This prevents your Mother in Law or cousin that has their iPhone or Android phone with all the original settings and bloatware from letting either company index you by using the location data on their phones. Next… -Turn off SSID broadcast if you can. This cuts down on lazy wardrivers scanning unhidden SSIDs. -Change the name of your SSID and router’s MAC/BSSID regularly. -> This doesn’t prevent sophisticated wardrivers from indexing your wifi. It prevents lazy ones from indexing it, as well as any personal devices that index wifi signals based on simply seeing the broadcast SSID, which is a thing. If you plan on hosting family for the holidays, now is a great time to do this. This NOT a 100% invisible wifi network solution. This is a “best as we can get” solution. If you want truly invisible internet connections, get shielded RJ45 cable like you live in a radio blackout zone. How to check if your wifi has been indexed? https://wigle.net/ [https://wigle.net/] is a good starting point. I’ve never had a wifi network appear on there, so apparently I’m doing something right.
While in Ghana I commissioned local artists to make a Buffy poster. They did not disappoint.
I'm ready to move from Mint and do some Distro Hopping. What's your suggestions on how to best do this from stock Mint 22.2?
I'm ready to move from Mint and do some Distro Hopping. What's your suggestions on how to best do this from stock Mint 22.2? - Lemmy Today
Screenshot of my partitions. Partition 1 if EFI, Partition 2 is Mint Boot sector I believe. Partition 3 is everything else. [https://lemmy.today/pictrs/image/6e1e5d35-87b8-46a8-a9f1-ede959a5e6a8.png] I’m looking to give OpenSUSE TW and Fedora a try specifically. HD is encrypted from install, and I didn’t know to put /home on its own partition. Plenty of storage space to play with. How should I approach hopping with the least amount of pain and cleanup when I finally figure out where I want to land?