Conversation

Notices

1. Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 20:42:04 JST Izuru Yakumo (八雲 出流)

   federated forges were already a thing.... whatever
   
   RE: https://floss.social/users/forgefed/statuses/112461860928000500

   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 20:44:30 JST Izuru Yakumo (八雲 出流)

     in reply to

     • 41402

     @a1ba@suya.place literally email (mailing lists), but people love to reinvent things I swear

   • 41402 (a1ba@suya.place)'s status on Saturday, 18-May-2024 20:44:31 JST 41402

     in reply to
     @yakumo_izuru like how?
   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 20:47:03 JST Izuru Yakumo (八雲 出流)

     in reply to

     • 41402

     @a1ba@suya.place alas, git is already decentralized by design
     
     obviously everyone uses GitHub or GitLab, there are always monopolies for everything

   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 20:52:44 JST Izuru Yakumo (八雲 出流)

     in reply to

     • 41402

     @a1ba@suya.place about sending patches? I did that a few times, and I even improvised other ways to relay them, it is certainly not convenient for most people, but I am no one to dictate how they should do stuff

   • 41402 (a1ba@suya.place)'s status on Saturday, 18-May-2024 20:52:45 JST 41402

     in reply to
     @yakumo_izuru I will literally fight you over how mailing lists aren't federated forges. Did you ever tried this workflow and can you call it convenient?
   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 20:54:23 JST Izuru Yakumo (八雲 出流)

     in reply to

     • 41402

     @a1ba@suya.place no, because I never needed to, I would only do that very sporadically if anything

   • 41402 (a1ba@suya.place)'s status on Saturday, 18-May-2024 20:54:24 JST 41402

     in reply to
     @yakumo_izuru ok, another question.
     
     Have you tried develop anything in collaboration with another people relying only on Git's decentralized nature?
   • Izuru Yakumo (八雲 出流) (yakumo_izuru@misskey.m544.net)'s status on Saturday, 18-May-2024 21:30:28 JST Izuru Yakumo (八雲 出流)

     in reply to

     • 41402

     @a1ba@suya.place not everything has to be activitypub, period.

   • 41402 (a1ba@suya.place)'s status on Saturday, 18-May-2024 21:30:29 JST 41402

     in reply to

     • 41402
     @yakumo_izuru and and at this point you're telling me
     >people love to reinvent things I swear
     while also admitting yourself that
     >it is certainly not convenient for most people
     
     It's not "reinventing" when the goal is to make everybody's life better.
   • 41402 (a1ba@suya.place)'s status on Saturday, 18-May-2024 21:30:30 JST 41402

     in reply to
     @yakumo_izuru it's not inconvenient for most people. It just outright sucks.
     
     Sure, it's OK for throwing patches at maintainer, especially if you don't want to make yet another centralized forge account. Sure, it enforces some development culture.
     
     But it's all comes at the cost of headache of:
     * Relying on mostly unreliable mail servers. I literally had my emails lost because of some insane anti-spam filters.
     * Most mail clients are also fucking broken. You either have some bullshit that randomly enforces HTML and breaks patches, either some unix weenie vi-like bullshit that nobody ever used and had no real user feedback.
     * Not having a real way to iterate over your changes. When you're sending a new revision of your patchset, all comments that was made for all previous revisions get lost (as they were replies to the older thread). I hate GitHub but look how it implements code review. It remembers the review comments were made even after rebasing.
     * Most mailing lists are DEAD. Sometimes, the only way you can actually make somebody review your changes is to directly ping them in IRC or Matrix because nobody fucking reads ton of mails coming from centralized mailing list. As a generic contributor you can't really filter out everything you're not interested in. And, no, Cc'ing maintainers with a crappy perl script from Linux kernel doesn't always work.
     * If maintainers didn't set up some kind of public archive (love mailing list archives that are walled behind cloudflare) or Patchwork you're screwed. Because the only people who have the patches you're interested in are those who were in To and Cc fields when OP sent their patchset.