this post was submitted on 06 Mar 2025
38 points (91.3% liked)
Programming
18679 readers
116 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think it's an interesting idea, and I'd see it as fine for simple host + fetch. But as soon as you start interacting, I see it as far worse.
A personal support email may work, but as they write by the end, ticket tracking and collaborating on a platform with a shared web interface is much superior for information sharing and but also iteration (they talk about back and forth emailing earlier).
Self-hosting yet another platform/forge with its own account system is not viable to me either. (I'm still hoping for forgejo federation for a centralized account. Until then, GitHub seems like the best choice purely because it's the biggest and everyone has an account and can contribute and post without account barriers.)
The idea that it could be a hosted repo with an integrated mailing list (and potentially bug tracker) is interesting, but ultimately, almost/actually a full forge then anyway.
Saying it's "an interesting idea" makes it sound as if git wasn't intended to be used like this from the start. But it was intentionally designed to allow posting patches to the Linux kernel mailing lists. It even has commands for producing email directly from the command line.
Sites like GitHub are the "idea".