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

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.

We don’t know if it’s actually her in the image. While the likeness is similar, it’s not 1:1 and the injuries make it even harder to tell.

Police, sure, but it probably needs to come from instance admins who will have all of the information on the bots sending the image.

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.

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.

did you not read your link?

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

They “work” (sometimes), but usually get it from somewhere upstream like Intelius.

The “progress bar” is not real. It’s designed to get you to dedicate enough time to the search so that you’ll be more likely to pay up when you hit the paywall.

A work around, sometimes, is to search for their opt out forms. These do not typically have that BS, and allow you to remove the relevant listings.

Oh yeah, I totally forgot about that - mine does do this, and the LED is right in the bottom middle, and it’s super bright.

It probably doesn’t need to be - but it was required to set up. Before I had my shield, I allowed local connections for local streaming, but you are correct, it’s probably no longer necessary.

So, I use regex to block all Roku domains on my network via pihole:

(ads|logs|cloudservices|image|images|web|prod.mobile|wwwimg|captive|customer-feedbacks|amoeba|amoeba2|sr|giga.sb|cs).roku(.admeasurement)*.com$

Then, possibly overkill due to the above, I used OpnSense firewall rules to block all traffic from my Roku tv. I think I just got fed up with seeing Roku spam in my pihole, as the above regex seems to completely “break” Roku.

After that, I set up FLauncher (following the method #2 instructions on the gitlab page) on my shield. This makes it so I only see the Roku launcher for a few seconds while the shield starts up, and then I’m dropped straight into flauncher. I chose flauncher because it’s very simple and barebones, so you might want to explore other options if you want more advanced features. I don’t really need those features since I’m usually using an app anyway.

Note that I did all of that after the tv was configured and set up, YMMV if it’s a brand new tv as it may need to call home to do the initial set up.