Of course they blame it on Temu and not the orange creature in the white house. Hope they enjoy paying that tariff everywhere else!

Why do LLMs obsess over making numbered lists? They seem to do that constantly.

In the past, when I’ve used SFTP, I just use the openssh docker container with a mount of my filesystem (since SFTP uses SSH). Particularly this image: https://hub.docker.com/r/linuxserver/openssh-server

I can’t speak to sftpgo as I haven’t used it, but from looking it up it seems that some people like it, although it’s a pain to set up. If you want something simple I’d still just go with openssh.

Seedvault worked fine for me when I moved phones last year.

Yeah, Ubuntu is really corpo these days, tons of bloat too. I avoid it like the plague.

Absolutely, and I’m not trying to say they don’t own their infra or have the ability to cut off the Molly users. Luckily, if that were to happen, you could use the automated backups to restore back into Signal, since they’re functionally the same.

Regardless, both apps have reproducible builds. It’s the infra that isn’t reproducible.

They’ve been allowing Molly to continue to function for multiple years. Notably, from Molly’s readme:

Molly connects to Signal’s servers, so you can chat with your Signal contacts seamlessly.

I looked over the terms of service linked there and don’t see anything specifically calling out third party clients. Is that elsewhere in another terms page somewhere or is it just not being specifically mentioned?

Point 2 is mostly not true, in that Molly exists and you can do reproducible builds with either implementation.

I’m not sure how much they dig, but Alexa recently changed to do everything via cloud, including all recordings and voice processing. It’s definitely at least always listening and phoning home.

It’s definitely not legal, especially if your school is funded by the public. That “free internet and power” is paid by someone, and if it’s the public, it’s kind of a dick move.

They can’t see what’s in your ssh or VPN tunnels necessarily, but they can usually see where the packets are originating from and going to. So if you’re say, accessing it from home directly to the server via VPN or SSH, if you’re not doing so using a full VPN service like Mull, they’ll be able to see the origin IP of your SSH or VPN handshakes, and thus your home IP.

Surely US investors won’t harvest data and/or enshittify the product!

Should have just fired the CEO instead, would’ve saved millions and the company in one go.

Just last week, they were posting job listings for DevOps engineers. Glad the CEO’s bullshit stopped me from even considering it.

Sure, but I didn’t mean to say that FOSS couldn’t be insecure. Software itself can obviously be insecure, like we saw with xz. At least with FOSS though, it’s more difficult for it to be hidden.

Apologies, I deleted my comment instead of editing it, but I meant to add that even with the shady workaround, if you have sandboxing it likely greatly reduces this risk.

Be very wary of what apps you install, and in fact, try to only use FOSS.

Yes, it would. Those basically create sandboxes.

So the first line says that it’s for older versions of android before 2022. But the next paragraph says:

For extremely specific use cases such as file managers, browsers or antivirus apps, Google grants an exception by allowing QUERY_ALL_PACKAGES permission, which provides full visibility into installed apps.

So this may still be possible, however sandboxing, especially GrapheneOS’ implementation likely mostly, if not entirely reduce this risk.

I know it’s definitely personal preference, but I’ve never seen the appeal in folding phones. I’ve never needed a bigger screen, and I feel like I would break it very quickly. In fact, if I could get a smaller screen than the standard 9 pro, I would.

did you not read your link?

I’m not sure what you mean.

The reason I’m not switching yet, is that there’s no federated auth. If they had that, I’d switch in a heartbeat.