@𝓒𝓱𝓻𝓲𝓼 I'm not a coder, so I can't answer this more precisely.FediDevs was designed to latch onto Mastodon's profile fields, Mastodon's database field...

2026-10-11 04:55:15

adminsforum@hubzilla.org

𝓒𝓱𝓻𝓲𝓼 wrote the following post Sun, 11 Oct 2026 04:55:12 -0700

starterpacks

The feature to create and share starterpacks is an interesting one

there is

https://fedidevs.com/

and also direct in a Masto account they can create such lists

Unnaturally this all seems to work NOT with Hubzilla channels they can´t be added to such lists

Firefox_Screenshot_2026-10-11T09-33-39.058Z.png

Is there anything which could be done about it?

2026-10-11 05:36:56

Harald Eilertsen

harald@hub.volse.no

@Hubzilla Support Forum

Is there anything which could be done about it?

Sure, we could implement the fields, and possibly API's needed to conform to whatever they are looking for. Looks like it could be just some profile fields in the webfinger response.

2026-10-11 23:56:51

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

The website is called Fedidevs, but it used to be built against only Mastodon. Not the Mastodon client API, but Mastodon's very specific inner workings.

The issue wasn't just that starter packs only worked on Mastodon. It was also that starter packs could only contain Mastodon accounts, and only Mastodon users were even able to join the site because the technical process of joining explicitly looked for features that are only present on Mastodon and nowhere else.

It was blatantly obvious that the maintainers of this site firmly believed that the Fediverse is only Mastodon when they built it, and that they refused to accept the truth when someone pointed out that there's more to the Fediverse than Mastodon later on.

Eventually, after quite a while of operation, they added specific code for certain Fediverse server applications. They added specific code so that Misskey accounts could be added to starter packs. They added specific code so that Pleroma accounts could be added to starter packs. And so on.

The whole thing is not built against any API, much less against ActivityPub. It's built against the inner workings of specific Fediverse server applications. Changing that would require a complete rewrite of the entire backend.

So in order for Hubzilla channels to be added to starter packs, the FediDevs maintainers would have to add specific code to FediDevs so that it supports Hubzilla channels.

2026-10-12 00:55:20

𝓒𝓱𝓻𝓲𝓼

chris@im.allmendenetz.de

Jupiter Rowland wrote:

So in order for Hubzilla channels to be added to starter packs, the FediDevs maintainers would have to add specific code to FediDevs so that it supports Hubzilla channels.

so what code... can you make suggestions ?

2026-10-12 01:21:14

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@𝓒𝓱𝓻𝓲𝓼 I'm not a coder, so I can't answer this more precisely.

FediDevs was designed to latch onto Mastodon's profile fields, Mastodon's database fields and Mastodon's inner workings.

When enough people begged for it to also support e.g. Misskey, the developers had to add code that would latch onto Misskey's profile fields, Misskey's database fields and Misskey's inner workings.

Same with Pleroma. Same probably with Friendica. And so on.

So if FediDevs wants to support Hubzilla, it would have to dig into Hubzilla, latch onto the profile fields in Hubzilla's public profiles, it would have to latch onto database fields that probably only Hubzilla has, it would have to latch onto Hubzilla's very specific inner workings. And that'd be a whole lot of work because Hubzilla is more different from Mastodon than Misskey is.

Then, and only then, will FediDevs be able to support adding Hubzilla channels to starter packs.

2026-10-12 00:58:01

𝓒𝓱𝓻𝓲𝓼

chris@im.allmendenetz.de

I was talking about tow different things
1) starterpacks by fedidevs.com
2) Collections by Mastodon