Makes me wonder… is it really worth it to launch a flagship server for public use?
Instead of new users getting distributed, and communities decentralised, majority are flocking to the flagship server… and also wants a centralised community located on the flagship instance.
hackbyte (friendica)
in reply to ♾️ Yuki (유키 雪) 🇵🇭 🦣 • •@♾️ Yuki (스노 雪亮) 🐬 🦣 Hrm... In short. Yes.
But we don't need just one new flagship server... We need a tiny series of flagship instances popping up, for several fediverse services.
So that we finally get a sane way to assimilate all the newcomers from twitter, instagram, reddit and others.. ;)
♾️ Yuki (유키 雪) 🇵🇭 🦣 reshared this.
♾️ Yuki (유키 雪) 🇵🇭 🦣
in reply to hackbyte (friendica) • • •@hackbyte Ah! Yes, “tiny series of flagship instances” can help. Something like mastodon.social and mastodon.online, if I understood correctly?
Maybe something like a cooperative wherein the coop is used to set up and manage flagship servers. Each server has a certain limit (maybe user registrations), and before reaching that limit, they open a new flagship server (with the same limits).
hackbyte (friendica)
in reply to ♾️ Yuki (유키 雪) 🇵🇭 🦣 • •♾️ Yuki (유키 雪) 🇵🇭 🦣 reshared this.
♾️ Yuki (유키 雪) 🇵🇭 🦣
in reply to hackbyte (friendica) • • •@hackbyte Ah. The big flagship servers will serve as a testing ground for new users to familiarise themselves.
Then they can move on to a new server of their choice once they are ready. (With perhaps, bringing their content with them if that feature becomes available).
porn-alt
in reply to ♾️ Yuki (유키 雪) 🇵🇭 🦣 • • •It has more to do with the human mind seeking familiarity in a new environment. Each Fediverse instance will eventually develop a unique approach to the user experience and interface that will naturally attract a particular demographic. Gmail users are Gmail users because of the featureset. Yahoo Mail users and Bing users are the same. They do a lot of things similarly; they do a lot of things differently, too.
And here's the fascinating thing about this, I'm on a Fedia.io kbin instance and you're on c.im and here we are, discussing this anyway!
♾️ Yuki (유키 雪) 🇵🇭 🦣
in reply to porn-alt • • •@porn-alt But it doesn't answer if it is worth launching a flagship server for public use.
;)
It can not be compared to Gmail or YMail because no one else can launch a GMail or a YMail on their own, the source code for those two products are not publicly available.
A flagship server of a software product is a server that serves as the carrier of the software's brand.
For example:
Mastodon's flagship servers are:
* mastodon.social
* mastodon.online
Calckey's flagship server is:
* calckey.social
Kbin's flagship server is:
* kbin.social
Pixelfed's is:
* pixelfed.social
BookWyrm's:
* bookwyrm.social
And so on.
However, as we've seen in the past, and this year, flagship servers are the primary target for bots. As well as, massive registrations whenever there is a wave of mass migrations. Which only takes away the precious volunteer time of the software developer away, to focus on getting the flagship server ba
... show more@porn-alt But it doesn't answer if it is worth launching a flagship server for public use.
;)
It can not be compared to Gmail or YMail because no one else can launch a GMail or a YMail on their own, the source code for those two products are not publicly available.
A flagship server of a software product is a server that serves as the carrier of the software's brand.
For example:
Mastodon's flagship servers are:
* mastodon.social
* mastodon.online
Calckey's flagship server is:
* calckey.social
Kbin's flagship server is:
* kbin.social
Pixelfed's is:
* pixelfed.social
BookWyrm's:
* bookwyrm.social
And so on.
However, as we've seen in the past, and this year, flagship servers are the primary target for bots. As well as, massive registrations whenever there is a wave of mass migrations. Which only takes away the precious volunteer time of the software developer away, to focus on getting the flagship server back in working condition.
There are #fediverse software that doesn't have flagship servers. At least not publicly.
Maybe, what we truly need is a demo server. In a demo server, there is a constant reminder that it is a demo server, and every 8 hours it will reset to its pristine state.
Part of the constant reminder is for the user to choose their home instance.
There can still be a flagship server, but it is not open for public registrations. It can be for the dev and their team's use only.
Also this way, the dev team doesn't have to worry too much if the flagship's dev branch update encountered issues, as the users in it are not public users. (Although yes, there are non-flagship servers using dev branches, but they upgrade usually after the other instances did.)