51b7fbea 97fcc582 ebcbd8c8

Goblin’ deez nuts

I don’t have a direct source other than the source code of the software they use: https://github.com/mautrix/signal

When using one of their “cloud hosted” bridges, the bridge software (that connects between Matrix/Beeper and other protocols) has to read all message content. Otherwise, it’s impossible to bridge to another protocol. E2EE becomes end (other users) to bridge (beeper) encryption.

With “local hosted” bridges, E2EE stays intact, but messages can’t be sent/received if the device hosting the bridge is unavailable.

In the future, with MLS (a different E2EE protocol), it could be possible to keep E2EE even when bridging to Matrix on cloud hosted bridges.

Depending on the application you used to alert you of the AirTag, it’s possible that your phone did not send location data back to Apple.

Apple can track AirTags, because iPhones are programmed to listen for them over Bluetooth Low Energy, and send the ID of the AirTag and location data of the device to Apple.

If your Android phone has an application to listen for BLE devices in the background, keeping track (locally) of which devices it saw in what locations, that application can tell you if you’re travelling with an AirTag (or similar device). It might even be able to interact with the AirTag, such as making it beep or reading its ID. If that application doesn’t send your location to Apple, the AirTag was not able to use your phone to make its location known to the owner.

Therefore, to the owner, AirTags are useless unless an iPhone (or other device that sends its location to Apple) is around.

Not just the “lack of APKs”, but the lack of a FOSS build. As you noted, it is possible to instal an AAB by extracting the APK(s) inside, but that doesn’t magically remove non-foss libraries.

The only build is an aab file. This is a Play Store bundle file, not an APK, so not directly installable in Android without the Google Play Store.

The only build being a Google Play release also indicates that non-foss libraries were likely included, such as the FCM libraries, as is common for GPlay releases of otherwise FOSS projects.

As far as I’m concerned, Element X for Android is not available yet, unless either building from source (with modifications to included libraries), or by using a non-FOSS version from GPlay.

Your iPhone 13 syncs slower over USB because Apple decided to stay on Lightning connectors, which use USB 2.0 on the other end. Although FireWire was faster back when it co-existed with USB, the USB standard has surpassed it a long time ago with more power, faster speeds, and better physical connectors.

The source code of a program is like a recipe and list of ingredients. If you buy a coffee from Starbucks, you get a coffee from Starbucks. You can’t easily change the beans used, the brew temperature, etc. With the recipe, you could brew your own with slight differences, or make coffee from scratch knowing everything that’s in Starbucks coffee. With the source code for a game, you could change/mod anything. FPS unlock mods, ports to other platforms, and much more. You could make your own game, and make it better knowing how some systems work in another game.

Some games have their source code leaked, in which case it is illegal to own, redistribute, or learn from the code. Although it’ll usually still happen, it’s much more “underground” than games where the source code was reverse engineered. Reverse engineering is like buying a coffee, tasting it, then coming up with your own recipe. Having your own recipe almost exactly identical to the original still allows you to make changes easily, but it’s not illegal, as you wrote it, and are allowed to share your own recipe. Some older titles like Super Mario 64 have been fully reverse engineered, and ported to every possible platform, with multiplayer mods, FPS unlock mods, etc.

If you can’t see a community, it is likely nobody on your instance is subscribed. On the top right of the page, search for the community (with the instance included), wait a few seconds, then search again. Subscribe to it, and you should be able to post there.

Search with the format !community@instance.tld, example: !196@lemmy.blahaj.zone

Find a community, subscribe to it if you want to be able to see new posts and comments, and select that community when making a post.

The same “rumors” exist about Matrix. According to some, “a lot of metadata is unencrypted”. While somewhat true, there’s literally no way to be able to deliver a message from person A to person B without knowing who the message is from and who it’s going to, especially on a decentralized platform. Most of the (not E2EE) metadata sent with an event in Matrix needs to be read by the homeserver, and thus can’t be E2EE.

Most of these projects are FOSS, so you have two options. Either ask the devs for OpenBSD support (but try installing everything on OpenBSD to see what goes wrong). Or try modifying the program yourself to add OpenBSD support.

Developers of these projects often target Linux, since it is by far the most used server kernel/OS. *BSD is not nearly as common.

The only way to potentially change that industry wide is to have enough people stubbornly use *BSD and help implement *BSD support for Linux specific tools they use.

Official support is often only provided with a docker setup as it standardizes bundled libraries and other needed blobs. This makes it easier to support many Linux distros.

Discord’s been going very downhill for years, and recently made a wider known awful change (although not too impactful). Wonder when they will be going too far with things like “Mee6” and “Nitro”.