this post was submitted on 30 May 2026
212 points (99.1% liked)

Selfhosted

60048 readers
785 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

  4. Don't duplicate the full text of your blog or git here. Just post the link for folks to click.

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
212
Where did the dust settle on Syncthing Fork? (lemmy.ca)
submitted 3 weeks ago by psycotica0@lemmy.ca to c/selfhosted@lemmy.world
51 comments fedilink hide all child comments
 

Hey folks! I know a while back there was a kerfuffle because syncthing-fork for Android went dark, and then a new person showed up and claimed everything was cool and they'd been privately given the keys or something, and people were concerned. I pinned my fdroid version to the at-that-time-current release until we got clarity.

Well, it's been a while and I just noticed I'm still on that old release. So... how'd it turn out? Do we like the new person yet? Is there a promising fork y'all are using? Or is the project dead? I'm sure I could just go look at the repo, but I'm also sure the repo would tell me "yeah, we're all cool" no matter what, so I'm curious what the community feelings are. Have there even been any useful new releases since then?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] psycotica0@lemmy.ca 4 points 2 weeks ago

Yeah, like other people covered, it's unfortunate but also very important. It's easy to tie "visible wifi networks" to "surprisingly precise location on globe" in many places, so the permission is named for the worst case scenario. Yes, the app might just be looking for a wifi, but it also could use that same information to locate you, so it's the location permission. Sensible.

If they wanted to support just this one feature without requiring a location permission, they could maybe have an API that is "are you currently connected to this opaque token" API where the app can ask "am I connected" and is just told "yes" or "no". That's probably safe enough. And then I could register the app with my wifi without the app even knowing what my Wifi is, it just gets a unique but random string.

The same is true of bluetooth. If I can list nearby bluetooth, I can see that speaker and this TV and guess location. But there could be an API that hides that, there just isn't currently