#forgefed — Public Fediverse posts

@evan @klml

#ForgeFed is an #ActivityPub extension that is developed as an open standard. It forms a protocol in itself: specifications for #forge federation.

In the poll above it should've been listed. It might replace 'Git', because that is not a protocol for forge federation. Git is a protocol for distributed version control systems (DVCS).

ActivityPub is more a framework than something you can use out-of-the-box. Arguably ForgeFed might even replace ActivityPub in the poll.

AP is a protocol for developing interoperable social networking solutions. It has no knowledge at all about code forges. It is based on Linked Data.

ForgeFed is a protocol for federating code forges. It is based on ActivityPub.

Btw, active ForgeFed projects:

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

- (on roadmap) https://codeberg.org/forgejo-contrib/federation

@evan @klml

#ForgeFed is an #ActivityPub extension that is developed as an open standard. It forms a protocol in itself: specifications for #forge federation.

In the poll above it should've been listed. It might replace 'Git', because that is not a protocol for forge federation. Git is a protocol for distributed version control systems (DVCS).

ActivityPub is more a framework than something you can use out-of-the-box. Arguably ForgeFed might even replace ActivityPub in the poll.

AP is a protocol for developing interoperable social networking solutions. It has no knowledge at all about code forges. It is based on Linked Data.

ForgeFed is a protocol for federating code forges. It is based on ActivityPub.

Btw, active ForgeFed projects:

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

- (on roadmap) https://codeberg.org/forgejo-contrib/federation

@silverpill @0xllx0 @general

Yes, indeed. I found this the other day, and have queued it up for inclusion at https://delightful.coding.social/delightful-fediverse-development

I also found the ongoing work on the #ForgeFed implementation, which is mighty interesting. Great work. Also queued up, but for inclusion at https://delightful.coding.social/delightful-fediverse-experience

@silverpill @0xllx0 @general

Yes, indeed. I found this the other day, and have queued it up for inclusion at https://delightful.coding.social/delightful-fediverse-development

I also found the ongoing work on the #ForgeFed implementation, which is mighty interesting. Great work. Also queued up, but for inclusion at https://delightful.coding.social/delightful-fediverse-experience

Forgejo demuestra que el Fediverso va mucho más allá de las redes sociales 🛠️

Mediante el protocolo ActivityPub (vía ForgeFed), Forgejo lleva la federación al desarrollo de código: puedes seguir repositorios, comentar issues y colaborar entre servidores sin tener que crear una cuenta en cada uno.

¡El Open Source decentralizado y soberano en acción! 🌐💻

#Forgejo #Fediverse #ActivityPub #ForgeFed #OpenSource #DevOps #SelfHosted

Anyone knows the state of federation/ForgeFed in Forgejo rn?

I want to migrate away from github, maybe to a selfhosted Forgejo, maybe to git.gay, maybe to codeberg and I wanted to be able to star/PR/issue repos in other forges. Not that I do anything relevant, but I wanted to be able to receive stars/PRs/issues in my stuff too even if I decided to self host!

@forgejo @Codeberg @forgefed #Forgejo #Codeberg #ForgeFed

Anyone knows the state of federation/ForgeFed in Forgejo rn?

I want to migrate away from github, maybe to a selfhosted Forgejo, maybe to git.gay, maybe to codeberg and I wanted to be able to star/PR/issue repos in other forges. Not that I do anything relevant, but I wanted to be able to receive stars/PRs/issues in my stuff too even if I decided to self host!

@forgejo @Codeberg @forgefed #Forgejo #Codeberg #ForgeFed

Konform Browser 140.13.0-100 has been released and users are encouraged to upgrade.

https://codeberg.org/konform-browser/source/releases/tag/140.13.0.100

This includes all security fixes from Firefox 140.13.0esr as described in https://www.mozilla.org/en-US/security/advisories/mfsa2026-70/.

Fixes for half of the related CVEs were are included in Konform Browser 140.12.0-104, released last week. Users are still advised to upgrade to latest versions before opening untrusted content. See release notes for details.

Last week also brought in a few improvements and streamlining of settings UI, like making settings related to cross-origin refer(r)ers more complete and understandable.

In other news, Konform Browser sources and build-tooling repositories are now also being mirrored via P2P Radicle Network (@radicle ) for redundancy. If the primary mirror on Codeberg is ever having issues, this more decentralized alternative can hopefully fill in the gaps. Patches and issues can also be submitted via Radicle without need to register account with any particular provider.

konform-browser source: rad:z4D6gZLANjQKHNPdKRSCREnkM8Y4g
konform-browser bsys: rad:z4DPNRhfcgw11WiBVL8HUAHaRT4NW

All commits on releases are signed with same PGP key and verifying these signatures is encouraged before building from these, especially as Radicle is still relatively experimental.

These announcements can be filtered using #konform_release hashtag.

#konformbrowser #konform_release #browsers #mozilla #firefox #opensource #privacy #security #radicle #p2p #forgefed

Konform Browser 140.13.0-100 has been released and users are encouraged to upgrade.

https://codeberg.org/konform-browser/source/releases/tag/140.13.0.100

This includes all security fixes from Firefox 140.13.0esr as described in https://www.mozilla.org/en-US/security/advisories/mfsa2026-70/.

Fixes for half of the related CVEs were are included in Konform Browser 140.12.0-104, released last week. Users are still advised to upgrade to latest versions before opening untrusted content. See release notes for details.

Last week also brought in a few improvements and streamlining of settings UI, like making settings related to cross-origin refer(r)ers more complete and understandable.

In other news, Konform Browser sources and build-tooling repositories are now also being mirrored via P2P Radicle Network (@radicle ) for redundancy. If the primary mirror on Codeberg is ever having issues, this more decentralized alternative can hopefully fill in the gaps. Patches and issues can also be submitted via Radicle without need to register account with any particular provider.

konform-browser source: rad:z4D6gZLANjQKHNPdKRSCREnkM8Y4g
konform-browser bsys: rad:z4DPNRhfcgw11WiBVL8HUAHaRT4NW

All commits on releases are signed with same PGP key and verifying these signatures is encouraged before building from these, especially as Radicle is still relatively experimental.

These announcements can be filtered using #konform_release hashtag.

#konformbrowser #konform_release #browsers #mozilla #firefox #opensource #privacy #security #radicle #p2p #forgefed

@michael

For the #ActivityPub and #ForgeFed implementation the #Forgejo contrib organization on #Codeberg has a separate repository and a roadmap they keep up-to-date. See:

https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md

@michael

For the #ActivityPub and #ForgeFed implementation the #Forgejo contrib organization on #Codeberg has a separate repository and a roadmap they keep up-to-date. See:

https://codeberg.org/forgejo-contrib/federation/src/branch/main/FederationRoadmap.md

On en est encore au stade expérimental, mais ForgeFed soulève une vraie question :
Et si l’avenir du Git ressemblait davantage au Fediverse qu’à une plateforme centrale ?
Une infrastructure plus résiliente, plus distribuée, mais aussi plus complexe à concevoir. 🤲🦊

🔗 𝗙𝗼𝗿𝗴𝗲𝗙𝗲𝗱 : https://forgefed.org/

#ForgeFed #Fediverse #OpenSource #Git #SelfHosting
(6/6 - FIN)

On en est encore au stade expérimental, mais ForgeFed soulève une vraie question :
Et si l’avenir du Git ressemblait davantage au Fediverse qu’à une plateforme centrale ?
Une infrastructure plus résiliente, plus distribuée, mais aussi plus complexe à concevoir. 🤲🦊

🔗 𝗙𝗼𝗿𝗴𝗲𝗙𝗲𝗱 : https://forgefed.org/

#ForgeFed #Fediverse #OpenSource #Git #SelfHosting
(6/6 - FIN)

@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

@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

Projects like:
👌 #ForgeFed (https://forgefed.org)
👌 and #OpenCloudMesh (https://nlnet.nl/project/OpenCloudMesh/) show what the internet could be: open and federated, not locked in.

But if public organizations don’t support and invest in this, who will?

A city thrives on connections. But imagine a city owned by 1 company, where residents are customers it would resist building roads to competing cities.

The digital world is no different.

Public institutions must demand, build and use neutral & open infra‼️

Projects like:
👌 #ForgeFed (https://forgefed.org)
👌 and #OpenCloudMesh (https://nlnet.nl/project/OpenCloudMesh/) show what the internet could be: open and federated, not locked in.

But if public organizations don’t support and invest in this, who will?

A city thrives on connections. But imagine a city owned by 1 company, where residents are customers it would resist building roads to competing cities.

The digital world is no different.

Public institutions must demand, build and use neutral & open infra‼️

I have been using GitHub (https://github.com/steinbring) for a long time, and I have been seeing a lot of people dunking on it lately (e.g., https://mitchellh.com/writing/ghostty-leaving-github) because of its many failings. I don't think that something like Codeberg (https://codeberg.org) or Bitbucket (https://bitbucket.org) is the answer because there is still a central point of failure and hosting bills to pay. I like the fact that things like ForgeFed (https://forgefed.org) and tangled (https://tangled.org) exist to at least federate comms.

I really don't know what the answer is.

#Github #ForgeFed #Tangled #Git #SourceControl

I have been using GitHub (https://github.com/steinbring) for a long time, and I have been seeing a lot of people dunking on it lately (e.g., https://mitchellh.com/writing/ghostty-leaving-github) because of its many failings. I don't think that something like Codeberg (https://codeberg.org) or Bitbucket (https://bitbucket.org) is the answer because there is still a central point of failure and hosting bills to pay. I like the fact that things like ForgeFed (https://forgefed.org) and tangled (https://tangled.org) exist to at least federate comms.

I really don't know what the answer is.

#Github #ForgeFed #Tangled #Git #SourceControl

With GitHub falling apart and everyone migrating off, some sort of federation between forges seem super important. Sadly it doesn’t seem like much has been happening with #forgefed lately?

With GitHub falling apart and everyone migrating off, some sort of federation between forges seem super important. Sadly it doesn’t seem like much has been happening with #forgefed lately?

@virtualpierogi @sri @jsalvador @ben @michiel @nlnet

Yes, I've noticed that in #FOSS realms there's a rapid change to the development processes that are followed. Where projects no longer allow people to just contribute PR's.

In many github projects for instance you should first start a Discussion and get dev team's consent to create an Issue, which you may then create a PR for. Any other direct contributions are either disallowed or immediately closed.

There was also this Vouch reputation system that got popularity real quick. And there'll be more changes like that I think.

https://github.com/mitchellh/vouch

https://news.ycombinator.com/item?id=46930961

I've been looking at #ForgeFed and how it is set up. Currently it models very much the application model of what constitutes a typical "Code forge", but this is restrictive and going from lowest common denominator between forges. There's opportunity here to focus on the domain of "Software development" and the (social) coding processes between all stakeholders.

@virtualpierogi @sri @jsalvador @ben @michiel @nlnet

Yes, I've noticed that in #FOSS realms there's a rapid change to the development processes that are followed. Where projects no longer allow people to just contribute PR's.

In many github projects for instance you should first start a Discussion and get dev team's consent to create an Issue, which you may then create a PR for. Any other direct contributions are either disallowed or immediately closed.

There was also this Vouch reputation system that got popularity real quick. And there'll be more changes like that I think.

https://github.com/mitchellh/vouch

https://news.ycombinator.com/item?id=46930961

I've been looking at #ForgeFed and how it is set up. Currently it models very much the application model of what constitutes a typical "Code forge", but this is restrictive and going from lowest common denominator between forges. There's opportunity here to focus on the domain of "Software development" and the (social) coding processes between all stakeholders.

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

@virtualpierogi @sri @jsalvador @ben @nlnet

When it comes to #interoperability there is no way around having consensus on what you interoperate on, and there must be alignment on some kind of Video related domain model that is robust and consistent.

If there were a robust #ActivityPub extension mechanism as well as good development practices and processes for the creation of extension into new business and application domains, then this mechanism can still facilitate app-specific extension on top of such a Video domain specification. It is very common for protocol design to have all kinds of extension points, look e.g. at #ATProto or #CloudEvents.

And more specialized domain extensions can also facilitate further extension in their design. Look e.g. at #ForgeFed AP extension, which allows custom forge-specific metadata collections to be sent with a federated Issue or PR.

@thisismissem @eyeinthesky

I just responded in the other thread about #ForgeFed way of dealing with Issues and PR's, emphasizing the actor model in the #ActivityPub specs.

Guess it depends on the nature of your extension and its desired functionality how you model things, but ForgeFed chose to have a dedicated actor, a TicketTracker, to manage the collection. Big advantage is that it become a truly encapsulated service with its own business logic, fronted by an AP actor for interoperable network communication.

https://social.coop/@smallcircles/116096769625606025

@thisismissem @eyeinthesky

I just responded in the other thread about #ForgeFed way of dealing with Issues and PR's, emphasizing the actor model in the #ActivityPub specs.

Guess it depends on the nature of your extension and its desired functionality how you model things, but ForgeFed chose to have a dedicated actor, a TicketTracker, to manage the collection. Big advantage is that it become a truly encapsulated service with its own business logic, fronted by an AP actor for interoperable network communication.

https://social.coop/@smallcircles/116096769625606025

@thisismissem @deadsuperhero

I was looking at #ForgeFed which is a very sizable #ActivityPub extension (constituting the "Code forge" app domain in app-centric view, but arguably "Software development" top-level business domain in a service-oriented fedi).

The way that things are modeled here adheres more to the actor model where there's a Factory actor, which in turn creates resource actors that expose various sub-domains. For instance for the management of Issues and PR's there's a TicketTracker actor to obtain via a Factory actor on a forge instance. Though I'm not sure whether I'd modeled that in similar fashion, it is a fascinating direction where we focus much more on good protocol extension design.

All in all AS/AP offers a very granular foundation that allows for very interesting architectures, if only we dare explore them and do not dogmatically stick to some engrained notion how "social media" ought to be. I see #SocialMedia as but a small subset of #SocialNetworking.

@thisismissem @deadsuperhero

I was looking at #ForgeFed which is a very sizable #ActivityPub extension (constituting the "Code forge" app domain in app-centric view, but arguably "Software development" top-level business domain in a service-oriented fedi).

The way that things are modeled here adheres more to the actor model where there's a Factory actor, which in turn creates resource actors that expose various sub-domains. For instance for the management of Issues and PR's there's a TicketTracker actor to obtain via a Factory actor on a forge instance. Though I'm not sure whether I'd modeled that in similar fashion, it is a fascinating direction where we focus much more on good protocol extension design.

All in all AS/AP offers a very granular foundation that allows for very interesting architectures, if only we dare explore them and do not dogmatically stick to some engrained notion how "social media" ought to be. I see #SocialMedia as but a small subset of #SocialNetworking.

Another Microsoft #GitHub outage, another reminder that over half of the projects I use / contribute to are hosted on and exclusively available on this proprietary forge.
It's time to factor this into decisions whether to use software, points-- for GitHub.

Stuff I tried accessing today:
#NixOS nixpkgs repo (can't update my computer)
#Flathub manifests
#Niri wayland compositor
#Tauon music player

Would love to see more migrations to free forges, and excited for #ForgeFed to make this easier!

Another Microsoft #GitHub outage, another reminder that over half of the projects I use / contribute to are hosted on and exclusively available on this proprietary forge.
It's time to factor this into decisions whether to use software, points-- for GitHub.

Stuff I tried accessing today:
#NixOS nixpkgs repo (can't update my computer)
#Flathub manifests
#Niri wayland compositor
#Tauon music player

Would love to see more migrations to free forges, and excited for #ForgeFed to make this easier!

Are there any #forgefed people at #fosdem today? I’d like to pick your brains!

Are there any #forgefed people at #fosdem today? I’d like to pick your brains!

It seems like @forgefed's grant funding ran out and the entire project has just been left hanging, unfinished. This is a potentially important project, so this is really frustrating.

But really, anything important enough to get grant funding probably ought to keep going after the grant funding ends. Maybe grant-making orgs could provide some kind of support for projects transitioning out of funded work sprints, back into volunteer-driven coordination?

#ForgeFederation #ForgeFed #GrantMaking

It seems like @forgefed's grant funding ran out and the entire project has just been left hanging, unfinished. This is a potentially important project, so this is really frustrating.

But really, anything important enough to get grant funding probably ought to keep going after the grant funding ends. Maybe grant-making orgs could provide some kind of support for projects transitioning out of funded work sprints, back into volunteer-driven coordination?

#ForgeFederation #ForgeFed #GrantMaking

GitLab is dropping plans to pursue federation features like distributed merge requests. Sad, but not very surprising to me.

https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358

However, @forgefed and related specifications are still a thing and @forgejo is still working on supporting that, see https://codeberg.org/forgejo-contrib/federation and https://forgefed.org/!

#forgefed #ForgeFederation #gitlab #forgejo #federatedGit #git

GitLab is dropping plans to pursue federation features like distributed merge requests. Sad, but not very surprising to me.

https://gitlab.com/groups/gitlab-org/-/epics/260#note_2910231358

However, @forgefed and related specifications are still a thing and @forgejo is still working on supporting that, see https://codeberg.org/forgejo-contrib/federation and https://forgefed.org/!

#forgefed #ForgeFederation #gitlab #forgejo #federatedGit #git

🍵

Oh, wait, that won't do it this time!

🫖

Hm, you know what?

🥂

Yeah, that feels right.

Another week after my last update on #Anvil. With two more days to go.

📝 Checking the milestones I can attest that the latest update to the demo instance made great progress.

After logging in I can now browse issues and pull requests (a special form of issues) as well as comment on them. Therefore the requirement to log in.

Oh, and you can now turn on and off issues and PRs. From what I understood, PRs are only available when there are files uploaded in the code tab (which makes sense when you think about it).

Since working alone can feel boring, I also implemented the ability to create teams and add people to it. You'll need to know the username of the collaborator. The teams have admin permissions when created this way because I learned that #ForgeFed treat teams as a means to deliver notes to the right people. Access Management was meant to be done through OCAP (object capabilities). Similar to what you can expect from Spritely Institute. ALAS that's not implemented.

So what's left are notification polling, desktop notifications and OAuth login with Vervis. Since Vervis' development was suspended this is effectively off the table.

I plan to write up documentation in the remaining time.

🎢 Of course this week was an adventure in itself. Let me share some learnings!

First, I wrote a small script that populated my user table on the local #Forgejo instance with those from the Big List I shared last time. Among them funsies such as „search” or „undefined”. Let me tell you that this brings debugging to a new level :neocat_laugh_sweat:

🔍️ On the upside I can now handle the pagination when searching for „search”. Yay.

⏲️ As I also run into some long running requests (because the backend was slightly overwhelmed by the number of incoming requests) I added a timeout for API requests (set to five seconds). Still long, but the majority of calls should make it through.

I played around with the team permissions in Forgejo. An area I rarely investigated in the past. As mentioned, by default I went with Admin permission as it is the least hassle. Best practice is following the principle of least privilege. I wasn't able to figure out the right knobs from the API alone so I looked at the web UI. For example, if you turn one privilege to „read”, several others change. Okay … What's the logic behind here? When reaching out to @pere I learned about the purpose of Teams. Okay … so I added a note to the implementation and left it there. It's defo a construction place to get back to. 🚧

Toggling TicketTracker and PatchTracker were easy enough (pendant to Issues and PRs in Forgejo).

💬 There's a rudimentary implementation of comments in Anvil now. It works. I can even show reactions! Speaking of: Svelte-Octicons lack some icons here (say, a laughing emoji). Reactions are underspecified in ForgeFed, but given that comments are #ActivityPub Notes I looked at #GoToSocial for informing myself how to describe a reaction. They're tags there that have an icon go along. But … Forgejo only has emojis for reactions. As in: Unicode. So … shall I use a MIME type of text/plain here? I sense that this could blow up other services …
Do we have a #FEP on the subject? (I haven't browsed …)

Since Pull Requests are Issues in disguise, commenting there was easy, too. I have a superficial understanding of the different pieces that make up a Patch in ForgeFed. So I'm displaying … something? The error handling here is not great. Forgejo is responding with meaningful information but since I long left design specs behind I felt lost on how to handle them. @mray Halp!

When you try it out, take a close look at the URL. I usually go with your profile but the work often happens in organisations. So a manual adjustment might be needed.

🗺️ Navigation is something that would go into an extension of the grant but we reached the end of the road here.

I'd argue it's time to celebrate!

🍻 Cheers!

#Forgejo federation can't come fast enough for you? Have you ever wished to help out, but specifications are too scary and you don't know where to start?

In that case, I have the perfect task for you (yes, you!): https://codeberg.org/forgejo/forgejo/issues/9282

#ForgeFed #federation #Codeberg

#Forgejo federation can't come fast enough for you? Have you ever wished to help out, but specifications are too scary and you don't know where to start?

In that case, I have the perfect task for you (yes, you!): https://codeberg.org/forgejo/forgejo/issues/9282

#ForgeFed #federation #Codeberg

The reason why I keep a mirror of xtream on #GitHub is because I suspect their users won't bother creating an account on #Codeberg in order to open an issue, so they have that option.

So the #ForgeFed project working on a federated #Forgejo is a nice thing that could solve that. I'm not sure if GitHub would ever federate, though...

The reason why I keep a mirror of xtream on #GitHub is because I suspect their users won't bother creating an account on #Codeberg in order to open an issue, so they have that option.

So the #ForgeFed project working on a federated #Forgejo is a nice thing that could solve that. I'm not sure if GitHub would ever federate, though...

Forgejo Federation (#ForgeFed):

« It's a bit like e-mail, except the data sent is JSON objects (i.e. structured computer-readable data), and not only humans have inboxes where they can be contacted, but also repositories and issue trackers have inboxes through which they can be remotely and safely interacted with. »

https://forgefed.org
6/4

@forgejo My personal highlight of this release: You can now use your #fediverse handle in #markdown documents and it will be marked up as a link to your user profile (or group, etc.).
https://forgejo.org/2025-07-release-v12-0/#redirecting-fediverse-handles
I'm excited about the future, when mentioning fediverse handles will actually be federated and will send notifications everywhere!
#Forgejo #Federation #forgefed

@forgejo My personal highlight of this release: You can now use your #fediverse handle in #markdown documents and it will be marked up as a link to your user profile (or group, etc.).
https://forgejo.org/2025-07-release-v12-0/#redirecting-fediverse-handles
I'm excited about the future, when mentioning fediverse handles will actually be federated and will send notifications everywhere!
#Forgejo #Federation #forgefed

okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3

or should i skip codeberg, and go full forgejo? :)

#git #githosting #gitforge #notabug #codeberg #forgejo #forgefed

okies, decided, today's the day... gonna start moving my repositories to codeberg... notabug.org's too consistently inconsistently available. n_n a little sad. mmmmmmuch fondness for notabug.org. ... i wonder, if i leave the repository off the end of the url in codeberg's migration tool... does it allow migrating everything in one go? :3

or should i skip codeberg, and go full forgejo? :)

#git #githosting #gitforge #notabug #codeberg #forgejo #forgefed

Crisis averted, #GitLab reopened the epic on #ActivityPub / #ForgeFed implementation. :)

They made it clear, though, that they're not going to do it themselves in any foreseeable future, their "current focus isn't in this area", so it's up to the community to implement it. As I mentioned in the issue, I won't be able to come back to it until I'm done bootstraping the business I'm working on, so anyone who wants to see it done faster should feel free to jump in.

https://gitlab.com/groups/gitlab-org/-/epics/11247#note_2603598572

press F to pay respects for #ForgeFed federation in #GitLab

https://gitlab.com/gitlab-org/gitlab/-/issues/30672#note_2597293301