this post was submitted on 20 Oct 2024
787 points (99.4% liked)

Selfhosted

40767 readers
1151 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 posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

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

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
787
Syncthing Android app discontinued (forum.syncthing.net)
submitted 2 months ago by chaospatterns@lemmy.world to c/selfhosted@lemmy.world
206 comments fedilink hide all child comments
 

Announcement by the creator: https://forum.syncthing.net/t/discontinuing-syncthing-android/23002

Unfortunately I don’t have good news on the state of the android app: I am retiring it. The last release on Github and F-Droid will happen with the December 2024 Syncthing version.

Reason is a combination of Google making Play publishing something between hard and impossible and no active maintenance. The app saw no significant development for a long time and without Play releases I do no longer see enough benefit and/or have enough motivation to keep up the ongoing maintenance an app requires even without doing much, if any, changes.

Thanks a lot to everyone who ever contributed to this app!

you are viewing a single comment's thread
view the rest of the comments
[–] majestic@sh.itjust.works 6 points 2 months ago (2 children)

I think it was made by mistake. They will more likely remove that dependency

[–] 486@lemmy.world 9 points 2 months ago* (last edited 2 months ago) (2 children)

Perhaps the hard dependency was a mistake, but not them moving more and more code to their proprietary library. It appears that their intent is to make the client mostly a wrapper around their proprietary library, so they can still claim to have an open source GPLv3 piece of software. What good is that client if you can only use it in conjunction with that proprietary library, even if you can build it without that dependency?

[–] nadir@lemmy.world 8 points 2 months ago

Instead of open core I’ll call this popular approach “open skin”.

[–] dan@upvote.au 2 points 2 months ago* (last edited 2 months ago)

mostly a wrapper around their proprietary library

I'm not familiar with exactly what Bitwarden are doing, but Nvidia are doing something similar to what you described with their Linux GPU drivers. They launched new open-source drivers (not nouveau) for Turing (GTX 16 and RTX 20 series) and newer GPUs. What they're actually doing is moving more and more functionality out of the drivers into the closed-source firmware, reducing the amount of code they need to open source. Maybe that's okay? I'm not sure how I feel about it.

[–] ammonium@lemmy.world 5 points 2 months ago (1 children)
[–] catloaf@lemm.ee 5 points 2 months ago (1 children)

That says that it is a bug.

[–] ammonium@lemmy.world 3 points 2 months ago (1 children)

It says the build error is a bug, not the inclusion of proprietary code.

[–] sugar_in_your_tea@sh.itjust.works 4 points 2 months ago (1 children)

To be fair, the project page says this:

The password manager SDK is not intended for public use and is not supported by Bitwarden at this stage. It is solely intended to centralize the business logic and to provide a single source of truth for the internal applications. As the SDK evolves into a more stable and feature complete state we will re-evaluate the possibility of publishing stable bindings for the public. The password manager interface is unstable and will change without warning.

So there are two ways this can go:

  • they complete the refactor and release it as FOSS
  • they complete the refactor and change the clients to be proprietary

I'm going to stick with them until I see what they do once they complete the refactor.

[–] ammonium@lemmy.world 1 points 2 months ago (1 children)

To be fair? Nowhere are they even suggesting they would release the SDK as FOSS, but they do say their password manager is open source. It seems like they just want a FOSS shell so they can claim it's open source for but keep their business logic closed source.

[–] sugar_in_your_tea@sh.itjust.works 1 points 2 months ago (1 children)

That's the second way it could go. But given their track record of being FOSS when everyone else was proprietary and keeping the source code available, I'm willing to give them the benefit of the doubt and see what they do. For now, "we'll re-evaluate it again once it's stable" tells me it's still on the table.

[–] ammonium@lemmy.world 1 points 2 months ago (1 children)

Stable bindings doesn't mean open source, so I don't see how that tells you it's still on the table

[–] sugar_in_your_tea@sh.itjust.works 1 points 2 months ago (1 children)

They're moving a lot of code to this internal core, which means this core is unstable. It's pretty common for projects to hold off on making code public until it's reached a certain level of stability. I'm guessing they're not interested in accepting patches, due to the high level of churn from the dev team. Once that churn dies down, there's a chance they'll reconsider and make it FOSS.

I've seen this in a number of FOSS projects, and it's also what I do on my own (I don't want help until I'm happy with the base functionality).

So that's why I hold out hope. We'll see once the churn on that internal SDK repo dies down.

[–] ammonium@lemmy.world 2 points 2 months ago

Why go through all the hoops if they are instead just could refuse patches? Open source doesn't mean open to contributions, look at SQLite for example.

If they had the idea to release this open source they would have said so in clear words by now. They didn't so I don't have much hope, unless maybe if they get enough negative publicity to change their mind.

Why does VC need to ruin everything...