pootriarch

Sam on Mastodon (linked post) grumbles about the profanity filters on jmp.chat (presumably from upstream providers) and getting messages rejected. I've experienced the same, including having my account blocked if I mistakenly send it twice.

When I inquired, support said they were working on improved "routes" (upstream providers) and that I would be waitlisted for the beta of the new routes. That was months ago and I've heard nothing since.

Has anyone gotten into the beta program, and does it improve the situation? Because sometimes you just don't have two fucks to give.

I might need to switch my phone provider. As much as I've loved having all my messages delivered via #XMPP, jmp.chat's upstream providers decency filter is killing me. I constantly get text messages rejected for using swear words. If you ask they insist that all phone providers do this, but if I copy the same message over to my other provider it sends fine.

Are there any other good VoIP providers (not necessarily with XMPP compatibility, but that would be great) that aren't puritanical?

What is the default chat retention period in Snikket instances provided by JMP? Is it configurable in the admin panel for an instance?

F-Droid just pushed a Molly-UP update that appears to only add a deprecation warning, and that holds the version number below Molly-FOSS.

There are no instructions. The Install link points to the repo, which F-Droid just notes that I already have.

In the past I have completely lost Signal history twice, once from reinstalling Signal itself but it refusing to read the backup, and once from trying to upgrade from Signal to Molly but having a backup versioned in the wrong direction.

Is the safe process for replacing Molly-UP written down anywhere? I would strongly prefer keeping Unified Push, but I feel like I've been told to walk into a dark tunnel.

There's a lot of consternation about the number of services that refuse to register against a JMP number. At the core I suspect it's about information sharing — your carrier will happily give your details to third parties, where JMP doesn't have that information to begin with.

I dealt with this differently. I stopped thinking of my mobile as my 'real' number, but instead as my public one. All personal contacts have my personal JMP number, Signal is registered against my JMP number. Cellular SMS has notifications silenced. When an SMS is important, like when logging into a bank, I know it's coming. No unexpected SMS is welcome.

This works for me because my friends don't use voice, so JMP having metered talk time doesn't matter. But mainly, I don't think of either number as 'real'. I pay for both, and each has its use.

I'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?

Organic Maps is available on Linux! It's on flatpak and several package repos (but not apt). I don't know how long it's been there — I just discovered it.

The splash screen cautions that this Linux beta doesn't have parity with the mobile apps yet, but it's still a huge leap over Gnome Maps. Vector rendering, so you can zoom in as far as you want, and free / open source / not shitty (notwithstanding the big scary EULA, which just contains all the OSS licenses for all the pieces).

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?

i hadn't fired up my python project in an age, probably two vscodium updates. when i did, i had no more syntax checking and the alert window showed errors reaching the 'jedi' server.

downgrading the vscode-python extension to 2023.16.0 was seen as the surefire way to clear this. it worked for me, too - got my syntax error highlighting back and no pesky errors in the alert pane.

they created a new issue against the extension, or the packaging system, or something, which was closed immediately though the problem still persisted. the chatter was about a cache, somewhere, with a lot of 'perhaps' and 'if'. one day i'll try bumping this back up, maybe after vscode-python passes the problematic 2023.18.0 version.

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.