-
1
We now have multiple options for source-code hosting, but I don't think we have a conventions for workflow files (CI/CD). Would to see a `.forge/` convention (or something else) to make repo multi git server compatible.
As of today we have .github, .forgejo, .gitlab and now .tangled12 0Jul 5, 2026 -
2
Indeed, very annoying especially if the whole point of the Atmosphere is to federate many apps, therefore users are seeing this 2FA flow quite often..
And I don't think email based 2FA is that popular in the non-tech consumer products market3 0Jul 5, 2026 -
3
-
4
@leaflet.pub catches my eye more and more ! The only thing that doesn't please me is the speed, especially for textual content only
pagespeed.web.dev/analysis/htt...2 1Jul 5, 2026 -
5
Yeah that's bad, same for Forgejo. And there is no easy solution for this. Maybe the workflow / actions definitions can self describe their supported runtime
For textual contents like CODEOWNERS or FUNDING.md this can work I guess
Will ftm keep the .github and .tangled in my repos 🫠2 0Jul 5, 2026 -
6
-
7
That's nice ! In a perfect world would love "forge workflows" to be easily runnable locally. ftm I'm using a lot "act", but this is more a workaround solution.
Maybe it shouldn't even be a forge related folder to be runtime agnostic. ex: `.meta` or `.config`1 0Jul 6, 2026 -
8
-
9
-
10
Interesting ! I've been thinkering on a similar system a few years ago, hashed of resources are the way to go.
Could save a ton of bandwidth at the global scale.1 0Jun 28, 2026
