@aliceif @kurimu turns out that also had minimal checks on such things. I don't recall anything other than checking the domain names of Package Names. That's the ecosystem. Today, does or any other app store even check this?

@growse @guardianproject @signalapp @fdroidorg That would be nice, but sadly, no. That APK contains proprietary libraries from Google and maybe others.

@pixelcode @kkarhan I have followed their over the years, they never actually reproduce the whole thing from source, just the easy parts. Last I checked, all their native code is just pulled in as binaries when using their reproducer setup. Plus, they can't reproduce the proprietary Google libraries github.com/signalapp/Signal-An

and rebuild everything from source.

@pixelcode @kkarhan has gone to great lengths to try to standardize the definition of "open source", including filing trademarks. Including proprietary libs fails their definition of For this reason, many are now using the term for things like Signal.

@signalapp As a supporter of , it is important to point out a key detail: Signal's own code is , but Signal uses multiple libraries from . Those cannot be scrutinized since the source code is not open. We believe Signal should offer an actual open source version, and are ready to help. This exists already in the fork fosstodon.org/@MollyIM Also, apps like are , and have on @fdroidorg

As you plan your week ahead, don't forget to get your #FOSSY talk proposal in by Monday, April 28 (anywhere on Earth)! You can do it at https://2025.fossy.us/call-for-proposals/ . We are a small team putting this big event together and greatly appreciate your help in making sure everyone in your #freesoftware and #opensource circles knows about the opportunity and deadline! #portland

A Mobile track at FOSSY was just added to the schedule! 🎉

If you have a talk about FOSS on mobile devices that you've always wanted to give, now is your chance 😁

The submission thing is open until April 28:
2025.fossy.us/call-for-proposa

#linuxmobile #fossy2025 #pdx

Show thread

@nemobis thanks for the info, I still wonder why they deleted the comments on the GitHub thread?

wow, just deleted all the comments for people who didn't like that users were objecting to them making it more like :

There are direct links to the comments in:
tech.slashdot.org/story/25/04/

But they are no longer visible on the GitHub issue. Unfortunately, no one got a archive.org capture before that happened.

@neil @fdroidorg Thanks, that would be very useful! Shall we just reach out to you via decoded.legal? Or we're reachable at team@f-droid.org

We are not lawyers, nor our alter egos play as such on the Internet. Ergo in the face of legal challenges we are only rusticos.

If you feel ad idem and want to lend a hand, or head, to #FDroid pro bono and bona fide, you can help in our ongoing efforts ad infinitum.

Quaeritur right here: f-droid.org/2025/04/16/strengt

#Mozilla #EFF #SFLC #OpenTechFund

is supposedly the "privacy company" but apparently those sweet dollars are just too irresistable, so they are expanding their ad business:

techradar.com/pro/apple-rebran

@KazukyAkayashi that means that Droid-ify is using the index-v1.jar, which has a weak SHA1 signature. They should upgrade to index-v2. We have libraries for apps like Droid-ify to do that with. If I were a user, I'd file an issue to make them aware.

@KazukyAkayashi Actually I see the bug now: it only shows up in older versions of the index (index-v1.json and index.xml). We'll look into fixing that.

Which client app are you using?

@KazukyAkayashi if you look at the repo metadata, you can see the name is "F-Droid" f-droid.org/repo/index-v2.json so it looks like it is a problem with your client app?

If you're thinking about , consider that less than 30% of the adult population voted for .

Debian MountainCamp will happen in Innsbruck, Austria - 16–18 May 2025. Come and meet fellow Debianites, hack on Debian, have fun! wiki.debian.org/DebianEvents/d #debian

Show more
image/svg+xml Librem Chat image/svg+xml