@ololduck@vit.am @Gina @ololduck@frogue.vit.am @jelte @DigitaleOverheid @forgejo @forgefed @elle

The default is "All rights reserved" where the creator is the copyright holder.

Since there are now 3 projects implementing #ForgeFed it might be great to test #interoperability between the projects, as a good means to improve the specification.

(Btw, I noticed your README to say "ForgeJo", but it is "Forgejo", an Esperanto word for Forge. You pronounce is as "For jay oh 😮", not "Forge yo 🤘" :)

@Gina @ololduck@vit.am @ololduck@frogue.vit.am @jelte @DigitaleOverheid @forgejo @forgefed

Indeed interesting, thank you for posting.

I notice that you are asking for help, but the software looks unlicensed, which technically makes it proprietary. Would you consider adding a license?

In terms of #ForgeFed implementations, other than the #Forgejo impl I mentioned above, the other active project I know about is by @elle also in #Rust..

https://codeberg.org/activitypub-rs/activityforge

I think there are enough people interested to bring https://forgefed.org to a higher level. But doing so requires a ton of work, that is daunting to just volunteer for. Ideally there should be funding to dedicate to that, but the funding landscape favors creating code, not creating good open standards and their broad adoption. Unfortunately.

Regarding your point about ForgeFed, i think we need real implementations active in the world in order to improve #ForgeFed. To my knowledge, https://frogue.vit.am is the only "working" (tests pass, two instances successfully communicate with each other) ForgeFed forge online. If you know of any other i would love to be made aware of it.

There's a #ForgeFed irc channel with 22 silent users in it.

Frogue is also an #ActivityPub server, so if you want news about it you can subscribe to @ololduck@frogue.vit.am

Sorry for butting in, i realize that this message does give the impression of tooting my own horn, but that is not the case. What i'm trying to convey is that as a ForgeFed dev/user, i'm feeling quite a lack of interest in bringing the spec to life.

CC: @tomootes@codefor.nl @jelte@mastodon.nl @DigitaleOverheid@social.overheid.nl @Gina@fosstodon.org @forgejo@floss.social @forgefed@floss.social

@tomootes @jelte @DigitaleOverheid @Gina

To those not aware I would like to point out two relevant @forgejo locations where contributions can be readily made..

The delightful #forgejo curated list, where #FOSS contributions can be added via a PR or by creating a new issue in the repo's issue tracker:

https://delightful.coding.social/delightful-forgejo/

And the forgejo-contrib organization, where among others the #ActivityPub based forge federation project is taking shape:

https://codeberg.org/forgejo-contrib/federation/

Related to the latter, I'd also like to give attention to the #ForgeFed ActivityPub protocol extension, which is really promising but needs an impetus from the community to bring the specifications to a higher level of maturity, and get good reference implementations to help open standard adoption:

https://forgefed.org
cc @forgefed