@pootriarch
@poptalk.scrubbles.techI've tried Magic Earth a handful of times, but each time I dumped it because it marked a street as closed or wrong-way, creating a circuitous detour. There's no such issue in OSM; it simply hallucinated something.
I was testing it so I knew where I was going, but I'm reluctant to rely on it when I really need nav. Have I been supremely unlucky?
https://flathub.org/apps/app.organicmaps.desktop
Free offline maps for everyone
https://www.openstreetmap.org/#map=19/37.79111/-122.40412
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
https://github.com/SimpleMobileTools/General-Discussion/issues/241
https://www.reddit.com/r/SimpleMobileTools/comments/187w64x/simple_mobile_tools_bought_by_zipoapps/
I had reimaged my old Samsung on LineageOS as it seemed to be the only alternative that supported my model. It was fine until I installed OSMAnd, which couldn't get a location. Shame on me for not noticing that I would need microG for that. Not feeling comfortable with all the rooting and flashing needed to shoehorn microG into an existing image, I figured I'd try LineageOS for microG.
Having loaded a lot onto this phone already, I wanted to try a dirty flash first, knowing full well it might not work. The first prerequisite is to use an image of LOS/µG that is dated higher than the image in the phone. I had just updated, so I needed to wait for the next one.
The docs say that LineageOS for microG will be updated "a couple of times a month". But the latest LOS/µG image has remained at 11/2/23. This means I haven't had an opportunity to try the dirty flash, but it's also a security warning sign for me—LOS updates weekly like clockwork. Irregular and slower-than-promised updates make me a bit nervous for this aspect of device safety. It's not just my model either; most of the images are backdated more than two weeks.
https://download.lineage.microg.org/
(Yes, I know my boot loader is unlocked, and no, Calyx and Graphene don't support me, so I made my choice between physical insecurity and Google insecurity.)
The Molly fork of Signal now has a variant that supports UnifiedPush, but it requires a helper called Mollysocket to be installed on a server somewhere. I can't get my head around the (we'll call them 'lean') docs, and I've never encountered such a helper for other UP apps. They just ask what to attach to, and they attach.
Has anyone fought through this?
https://github.com/microsoft/vscode-python/issues/22176
Type: Bug It just doesnt work anymore 1.Its in windows7, codium https://github.com/Alex313031/codium/releases if you want logs i can provide ModuleNotFoundError: No module named 'jedi_language_serv...
A few updates ago Pop started nagging me to accept firmware updates. My layman's reading of the release notes is that it's a Microsoft package that can block boot based on an ever-increasing number of packages they don't like.
Is it safe to take an update like this? Unlike a kernel change, I don't know how to recover if this goes wrong.
Chromium derivatives like Vivaldi and Brave decried the Google Web Environment Integrity… um, 'feature', at varying volumes, back in the summer when it became widely known.
But can any Chromium-based browser actually avoid implementing this? Have there been more recent statements?
Since the integrity environment gunk, I've switched all boxes over to use Firefox as primary. This took a lot of configuring, as Firefox out of the box brings… a lot of stuff I don't want.
One of those things is telemetry — whatever that means to Mozilla — that was tamed only with a combination of an enterprise profile (hi sudo!) and user.js hacks.
However, the policy and user.js changes don't work on the Ubuntu box, where I've installed Firefox from the PPA to get it out from under Snap (and thereby usable with a password manager). The policy locks down and disables the right configs and the configs all have the right settings, but it keeps pinging incoming.telemetry.mozilla.org. Two Macs and a Pop!_OS box don't ping Mozilla at all with these settings.
No harm no foul, I just blocked them in NextDNS and laugh in their general direction. I just wonder what else is different in the PPA.