I try to respond to every genuine engagement. I block trolls, contrarians, and provocateurs because life is too short.

  • 0 posts
  • 43 comments
Joined 1 year ago
Cake day: January 29th, 2025
  • Yep. Its honestly mild as hell.

    Essentially legislation that says:

    • app stores have to have age categories to silo children, teens, and adults.
    • OSes have to have a field to collect this data from users when they set up their login, so it can be sent to app stores via API.

    Its just a standardized system that should have been done ages ago, but was not a priority for standards orgs, so none stepped up - so legislation appeared.

    I strongly argue that it should only apply to commercial OSes and app stores though - as they’re the ones that primarily cause issues these laws intent to address.

    Linux and FOSS have been caught in the crossfire in a privacy and personal data battle they were not involved in.

  • If you believe the AI hype there won’t be any programming jobs soon - so those that do (believe) think they need to become highly-proficient AI-wranglers to maintain employability.

    I too think it’s the wrong approach, but it’s hard to say what hirers will be looking for in the medium to long term, and devs whom adapt to ‘the new thing’ faster have typically been more hirable.

    Personally hoping the big players crash and burn asap because the benefits just haven’t been anywhere near worth the costs across various domains.

  • ^ See this is a great example of completely misunderstand FOSS. The vast majority are personal projects.

    The whole point of making them open source is to share the software they’ve created for others to enjoy/use, and share the code for others to learn from or utilize in their own projects. Its not to “open the door to let outside help in” as though they’re the ones gaining from the arrangement, lol… the vast majority of FOSS code on npm for example has a single maintainer. Open Source Security Foundation discussing npm stats of almost 60% of all projects having a single maintainer, here: https://github.com/ossf/tac/issues/101

    That you read my comments and focus on compensation, as though I haven’t spent 90% of the commentary on other aspects is weird. I’m done responding, but feel free to shout into the void.

  • Who said they were victims? I said I don’t see any harm in devs being mildly abrasive as long as it helps keep their passion for the project alive.

    How many projects do you pursue in your free time for no compensation that benefit strangers all over the world, whom can file complaints about your project, asking you to remedy or change it?

    FOSS dev work is not a victim-generating machine, it’s just entirely misunderstood and underappreciated. They make a project for them, then they m0ake it free to all… and the code, and the support. But, you ask them what they dislike the most - it’s the support. The endless poorly-filled tickets, the duplicate tickets the submitter didn’t search for, the user errors that are explained clearly in the documentation. That part is thankless work. That burns people out. But if they use a joke tag on a support ticket when they close it, it’s suddenly “omg, devs are so rude”.

    […] include that type of work on a resume, which is sort of turning that work into future earnings if it helps you get a high paying job.

    Ah yes, FOSS work should be its own reward because they can say they did it. Sort of like how interns should work for free at big companies ‘for experience’, and young artists/techs/small businesses should help influencers for free because they’re ‘working for exposure’. Now that attitude is a cop-out.

  • I’ve seen this on a few repos and it never came across too harsh, the posts tagged with it were deserving. Wish I’d noted the repo names…

    I’m fine with it tbh. FOSS devs need to squeeze every bit of enjoyment out of working on the project to keep motivated. If they (or mods) can drop a helpful reply and close an issue as ‘skill issue’ and get a little chuckle while they give their time for free answering poorly-written queries or bad bug reports then that’s a reasonable trade to keep them from burning out.

  • Yeah DuckDNS gave me many false positive outages where its resolution failed, for multiple half-days every year I used it (5yrs+).

    I moved to the afraid.org and its been solid, if anyone’s looking for another free service - only cost is you have to log in once every six months to validate your account is not dormant. They have a paid tier which gives more features (that most home users will never need), and that allows the guy running it to fund a very reliable service.

  • Update from Simon aka imsodin, Syncthing Maintainer

    tl;dr for android users: No need to switch apps at this time, the current install continues to work and is safe. If you can disable app auto-updates, please do that for now to be on the safe side.

    Good news: Had a good chat with @nel0x. He is a collaborator on researchxxl’s repo and just marked those releases as “pre-release”, which prevents the obtainium auto-upgrades. So we are back to no immediate risk for users and we can take it slowly, trying to establish communication and more context. It’s still possible and imo likely that nothing nefarious is going on, just a very suboptimal handover that needs clearing up. There’s no need to go dig for repos on github, the technicalities of continuing to publish an app are not an issue - the open/relevant points are about a possible direct continuation of the existing app (or not), the time/effort that needs to be volunteered to publish an app and the trust in whoever does that. Hopefully we can work something out. If you are interested in helping maintain the app, let us know, other than that imo nothing to do here except if you are a user, to do the above in the tl;dr and every now and then check-in on the status (now and then being more like every week than every hour 😉 ).

    https://forum.syncthing.net/t/does-anyone-know-why-syncthing-fork-is-no-longer-available-on-github/25661/58