home.social

#slophub — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #slophub, aggregated by home.social.

fetched live
  1. @dmathieu @jaredwhite @Codeberg I totally agree with you, and reading of ppl leaving codeberg because of some downtime was pretty annoying. And for this reason I started a recurring small donation to them. I was looking at the membership, and maybe i'll switch to it in the future. But yeah i'm just done porting my main projects to #codeberg, and they will still there. Don't want to go back to #slophub (aka github).

  2. @dmathieu @jaredwhite @Codeberg I totally agree with you, and reading of ppl leaving codeberg because of some downtime was pretty annoying. And for this reason I started a recurring small donation to them. I was looking at the membership, and maybe i'll switch to it in the future. But yeah i'm just done porting my main projects to #codeberg, and they will still there. Don't want to go back to #slophub (aka github).

  3. Since everyone now is posting that they are going back to #slophub (aka #github) because of this downtime, i'm going to stay with #codeberg
    Yeah the downtime is frustrating i know, but they are not a multibillion #slop companiy with unlimited power. It is a non profit organization, still struggling to cope with all the attention and received in the last few months.
    So i'm going to stay on #codeberg and going to donate few euros to them.

  4. Since everyone now is posting that they are going back to #slophub (aka #github) because of this downtime, i'm going to stay with #codeberg
    Yeah the downtime is frustrating i know, but they are not a multibillion #slop companiy with unlimited power. It is a non profit organization, still struggling to cope with all the attention and received in the last few months.
    So i'm going to stay on #codeberg and going to donate few euros to them.

  5. Announcement time:
    FInally today i managed to complete the migration of the #osdevnotes project from #slophub (ops i meant #github) to codeberg.

    The old repository will remain active as a mirror for now, but any further updates of the books will be carried on #codeberg
    So the new url of the project is now: codeberg.org/dreamportdev/Osde (just replace github.com with codeberg.org)

    #migration #codeberg #osdev #programming

  6. Announcement time:
    FInally today i managed to complete the migration of the #osdevnotes project from #slophub (ops i meant #github) to codeberg.

    The old repository will remain active as a mirror for now, but any further updates of the books will be carried on #codeberg
    So the new url of the project is now: codeberg.org/dreamportdev/Osde (just replace github.com with codeberg.org)

    #migration #codeberg #osdev #programming

  7. Self-inflicted pain over at #SlopHub. Seems like number of commits is the new Lines Of Code.

    My sympathy level: somewhere between Zero and Fuck All.

  8. @mttaggart
    Don't be misled by the corp-speak nonsense; this was just a trial balloon to calibrate where, how, and how often they can deliver ads through #SlopHub. Ads *WILL* return, just maybe not in PRs.

    The only correct response is to move the hell off SlopHub.

  9. @mttaggart
    Don't be misled by the corp-speak nonsense; this was just a trial balloon to calibrate where, how, and how often they can deliver ads through #SlopHub. Ads *WILL* return, just maybe not in PRs.

    The only correct response is to move the hell off SlopHub.

  10. I told y'all fuckers to leave #SlopHub the day Microsoft bought them, but ya didn't listen, did ya?

  11. I told y'all fuckers to leave #SlopHub the day Microsoft bought them, but ya didn't listen, did ya?

  12. @harrysintonen
    It's a mystery to me how any open-source project can still be using #SlopHub

  13. @harrysintonen
    It's a mystery to me how any open-source project can still be using #SlopHub

  14. @ploum
    I think it's that SlopHub's workflow is designed to keep people hooked on using #slophub To do anything, you have to do it on their website, and that's good for their "engagement metrics" (or some such bullshit).

    As you point out, the git-email workflow creates a (mild) barrier-to-entry, and sometimes (imho) a small barrier to entry can be a good thing.