ubergeek77

ActivityPub doesn't just push everything on a server to every federated instance like a fire hose.

I'm pretty sure Lemmy does? I run my own instance and that's how it works.

Is Mastodon different?

This doesn't solve the problem of sending Threads a copy of absolutely every bit of activity that happens on the instance. If I'm on an instance that federates with Threads, even if I put them out of sight/out of mind, they still get a copy of everything I do. A lot of people are on the fediverse for privacy reasons, yet here we are with people begging to hand Facebook this data on a silver platter.

"But why hide information that's public? They could just scrape it."

Yes, they could. But a real-time feed of activity is more complete, easier to manage, and doesn't require them to go and build a scraping tool just for this.

If I don't want Threads to have any of my data sent to them, I should be able to choose without needing to leave an instance I've been on for potentially years.

Hi :)

If you're already running an instance, you're not going to have a good time of this on the same server unfortunately. The webserver config I ship assumes a single instance, and all of the handling assumes only one domain. You would have to basically modify my entire script to support something like this.

You can take a look at my advanced configuration page to figure out what files you can edit, but this would be a very manual process for what you want to do.

Apologies, but you would be better off deploying a new server.

CalyxOS (and the supported devices) expose you to a classic “evil maid attack” applied to phones.

As usual if you’re looking to have any security (Verified boot) GrapheneOS + Pixel phone is the only options. I really don’t get it how come people(...) are okay with having a phone with all their personal data and logins without verified boot. Stolen / lost phone and game over.

But CalyxOS focuses on verified boot too?

I don't have the same issue. Fennec from F-Droid runs at 120Hz even with tabs open

The indicator does flicker between 60 and 120 while the page is loading, but it's not perceptible. However, if what I'm seeing means the FPS goes down to 60 while the app is busy, this may be some kind of performance throttling done to keep resource usage low. If you have lower end specs, this may be the explanation. I'm on a Pixel 6 Pro.

Not sure what you mean. I'm not trying to use an external monitor, I just want to use AR glasses I already own. There's no adapter for that, it's just a USB C cable.

I really hope this will let my AR glasses work. I was bummed they didn't work with my Pixel 6 Pro, and half the reason I went for an 8 Pro were the initial display out support news from July.

When this workaround was reported to not work, I was pretty bummed, but this seems like a good sign. I'll be building my own ROM anyway, so I can easily set this property enabled by default with no need for root.

0.12kg over four years??

How is that not within the margin of error?

More like guesswork/assumptions than reality

Sorry to be blunt, but you're not a developer and it shows. Android's build system was purpose made to be reproducible. Electron was not.

There is so much going on in an Electron build, most of which is out of Signal's control unless they maintain an entire fork of the Electron build stack. That is an enormous engineering effort for basically zero benefit.

It probably is functionally reproducible, apart from checksums differing due to build dates baked into the artifacts somewhere. It's not as easy as you think.

If you think it's as easy as "building it in a Docker container," then by all means, try.

The person you replied to is being downvoted, and yes, expecting support from Google is a meme, and Google deserves 100% of the negativity they're receiving in this regard.

But, in their defense, they have always kept their word on keeping Pixels updated, and in some cases, have added on an additional year of support when not originally planned, including an extra full Android update for older devices.

So while they eventually kill every new software product they make, they've always kept their word on Pixel updates. I think the Pixel team has a lot more resources than the rest of Google, so I'm inclined to believe them for now, but I'll be one of the first people grabbing a pitchfork if they don't keep their word.

There have been a few RCE's for Android 11 and up impacting both Bluetooth and the Baseband.

Bluetooth:

https://www.malwarebytes.com/blog/news/2022/12/update-now-google-patches-android-vulnerability-that-allows-remote-code-execution-over-bluetooth

Baseband:

https://www.malwarebytes.com/blog/news/2023/03/update-android-now-two-critical-vulnerabilities-patched

Of course, Android 11 is still supported as of right now, so if you have been getting security updates when available, then you are good. I just know there are phones running 11 and below that don't even get security updates, so those are the people that need to watch out. You can check your Security Patch Level in settings to be sure.

If you haven't been getting security updates, I would definitely consider getting a new phone. Especially if you are not one that stays home a lot. The people who will try to exploit things like Bluetooth will be out and about, not walking up to your home.