all 12 comments

sorted by: hot top controversial new old
[–] 22 points 11 months ago (10 children)

Any ideas why this happened?

  • source
  • hideshow 10 child comments
  • [–] 4 points 11 months ago (9 children)

    Coding is "illegal" now, remember?

  • source
  • parent
  • hideshow 9 child comments
  • [–] 20 points 11 months ago (8 children)
  • [–] 7 points 11 months ago (6 children)

    Looks like it's just random commenters taking random guesses because those have happened before.

    What is a “repository reset”? One commenter writes:

    There was a temporary similar “outage” back in July with rewritten history, apparently something inappropriate was recorded in the repo history they wanted cleaned out. The repo came back after that. I have no idea if this is the same thing, or if they just got tired of maintaining it.

    Seems strange to me. You can prep locally and then force-push. I don't see why rewriting history would require taking the repository down.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 4 points 11 months ago (3 children)

    If he pushed something he shouldn't have online then taking it offline immediately makes a lot of sense.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 11 months ago* (2 children)

    It makes sense, but once it's pushed there is no way to know if it's been cloned or kept somewhere else. The only real mitigation is to rotate the keys or password that was leaked.
    If it's something else you can't rotate, you're screwed.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 11 months ago (1 child)

    Plus won't the forks on GitHub keep the history before the "reset"?
    Afaik, forks on GitHub are basically the same underlying repository, just a branch associated with another user. They won't be able to really purge anything from these other branches.
    Plus anyone who has a local copy of the repo or an automatic mirror somewhere else, will have the changes available.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 11 months ago

    Yes, forks remain as they are. Yes, the fork network has a shared data repository on GitHub.

    Consequently, rewritten history will break history compatibility, possibly requiring manual fixups on forks or work based on it.

  • source
  • parent
  • [–] 14 points 11 months ago

    Oh shit. What do now.

  • source
  • 29 comments in c/opensource@lemmy.ml view that post
    [–] 27 points 11 months ago* (last edited 11 months ago)

    https://github.com/syncthing/syncthing-android/releases

    This ones a little old, but seems fine in Obtainium?

    Right, as the next commentor says; it's deprecated, and won't get updates. Interesting that they basically are saying "move to a different service"?

    This looks to be an active fork: https://github.com/RoootTheFox/syncmeow

    🤷‍♂️

    Update: The Syncthing-Fork source is still available here: https://f-droid.org/packages/com.github.catfriend1.syncthingfork

  • source
  • [+] 44 points 11 months ago (12 children)
  • [–] [S] 35 points 11 months ago (9 children)

    "2025-08-11"
    that is from 3 months ago. I think that was another repo.

    this repo I included had update until today.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 40 points 11 months ago (8 children)

    yeah catfriend1 was technically in charge of syncthing-fork before the original syncthing stopped being developed. catfriend1 in other words essentially just continued development on their fork on their own, which kept syncthing alive.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 14 points 11 months ago* (6 children)

    F-droid still has the most current builds available for the catfriend1 syncthing-fork.. But yeah, this isn't good. Damn. Was hoping if they needed to step back from maintaining a project like this, they'd at least have a call for a volunteer, or let the project languish until someone forked it again and took charge.. To shut it down completely, not great for anyone.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 20 points 11 months ago* (last edited 11 months ago) (5 children)

    Well, as OP mentioned, and others have speculated in the official syncthing forums, apparently catfriend1 did a repository reset where they wiped everything and started over something like three times last year. So that's still a possibility. I'm going to wait until more information comes out or until catfriend1 doesn't come back after a month or two before I start worrying about the future of the project. Worth finding anyone who had backed up the most recent version of the repository though, just in case.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 29 points 11 months ago* (1 child)

    Thats.. An odd way to do software development. You can pretty much do whatever with git, its a very powerful tool. Shouldn't need to destroy and create repo's regularly..

    Worth noting, if the repo never comes back, syncthing tray seems like they added android support per this message.

    And it seems like you can install syncthing from termux and just use the webGUI, per that previously linked forum thread.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 15 points 11 months ago

    Does F-Droid keep a backup of the apps' repo? Anyone has a backup of https://github.com/Catfriend1/syncthing-android ?

    Maybe I should start having my own github mirror..

  • source
  • [–] 14 points 11 months ago (8 children)

    The android development always just seemed... off, idk, I just got weird feelings about it and the fork. So I switched my family to use termux and termux:boot to run syncthing instead, it works fine.

  • source
  • hideshow 8 child comments
  • [–] 2 points 11 months ago (2 children)

    At that point why not use rsync?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago (1 child)

    I have no idea what you mean. I just had to set this up once on my parents' phones and now it works all the time, even when they change networks, no port forwarding or any interaction required on their part. Rsync is a cli that requires an existing network connection between two devices, both online, and doesn't watch files or create a file version history. It is an entirely different tool.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 11 months ago

    Ahh, makes sense for your use case, then.

    Rather than ST I used to use rsync+ssh, and just had a Docker SSH container running with users in the ENV.

    I've switched to WG in all devices since then, though.

  • source
  • parent
  • [–] 1 point 11 months ago (1 child)

    The android development always just seemed… off, idk, I just got weird feelings about it and the fork.

    Could you elaborate at all?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 11 months ago

    Yeah, it's odd to me that the syncthing repo makes a point of not officially supporting android, and not making any promises about its continued maintenance. It's a large part of their user base, but it seems, for some reason, this developer that went dark never spent time to coordinate with or join the core team.

  • source
  • parent
  • [–] 12 points 11 months ago

    And I was wondering why I was getting an error 404 in Obtainium 😒

  • source
  • [–] 8 points 11 months ago* (last edited 11 months ago)

    No one knows what the story is yet?

  • source
  • [–] 4 points 11 months ago

    it now redirects to a different github account, researchxxl. issues are turned off. old pull requests are there so it looks like the repo was transferred

  • source
  • [–] 1 point 11 months ago

    I have forks that are updated every night through a cron for these very reasons. But I didn't ever set it up for Android apps... Time to fork a whole lot more projects. sigh

  • source
  • [–] -1 points 11 months ago* (last edited 11 months ago)

    To be clear, this was announced months ago. Many folks moved to syncthing-fork on android

    EDIT: I was wrong! This is def syncthing fork.

  • source
  • 2 comments in c/technology@piefed.social view that post
    [–] 2 points 11 months ago

    well that's a huge problem for me…

  • source
  • [–] [S] 1 point 11 months ago