-

2026-10-16 12:53:29

silverpill@mitra.social

User not found: Validation Error: forgefed.NodeInfo: Field node.SoftwareName contains the value mitra, which is not in allowed subset [forgejo gitea mastodon gotosocial]

@forgejo we can do this the easy way or the hard way

2026-10-16 13:49:41

CaohuaK ❄️

caohuak@moon.lonewolf.zone

@silverpill @forgejo They had already done it this way when they implemented the federation feature.

https://codeberg.org/forgejo/forgejo/commit/3bb6ed8f19eff99728656d1cfb1ac9e22782de2b

However, I tried changing nodeinfo.software on my Mitra end (test instance), and it ran fine, so they can definitely allow some software. Even if there are warnings like [W] Failed authentication attempt from 45.38.xx.xx:0.

2026-10-16 13:53:38

xwyqi

xwyqi@mitra.xwyqi.org

@caohuak @silverpill Provided a screenshot for reference.

Version: Forgejo 17.0, Mitra 5.11.0.

2026-10-16 15:39:53

silverpill

silverpill@mitra.social

@xwyqi @caohuak Changing software name was enough for me as well. Forgejo identifies itself as Gitea/17.0.0+gitea-1.22.0 so Mitra can simply change its NodeInfo response based on this user agent string.

or the hard way

2026-10-16 16:19:22

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@silverpill @xwyqi @CaohuaK ❄️ But it can't be a solution for the whole Fediverse to change its user agent strings to Forgejo, Gitea, Mastodon or GoToSocial just to be able to federate with @Forgejo. Especially seeing as (streams) and maybe also Forte are probably the only server applications where admins can do this without hacking into the source code.

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Streams #(streams) #Forte #Forgejo

2026-10-16 14:39:59

CaohuaK ❄️

caohuak@moon.lonewolf.zone

@silverpill Hmm unfortunately your account have banned by floss.social admin, they couldn't see your post.