LTLのないFediverse志向の汎用Mastodonサーバを動かし始めました。予定している機能はほとんど未実装です。まぁ、プレオープンかな。 https://fedibird.com
HTLとリストとハッシュタグ中心の、同じ鯖に同居している人をまったく気にせずに活動できる、ニュートラルなFediverseの活動拠点を目指します。
やや踏み込んだ運用方針と改造で動かしますので、その点はあらかじめ承知おきください。
◇ Fediverse上のサービスとの連携を志向する（リレー、Prismo他）
◇ Fediverseにマッチするビジネス利用環境を研究する（公益目的）
◇ その他、実験的な仕様・機能を研究する
* 【未実装】除外指定されていない公開投稿を全文検索の対象とする
* 【未実装】Trusted Follower：フォロワー限定の配信を、自分で選んだフォロワーだけに限定する機能
* 【未実装】連合を前提としたグループ・コミュニティ機能
少し強めのサーバ構成になっているので、お試し利用可で、フォローインポート含めて適当に使って頂いてかまいません。
I'm glad that my Mastodon instance supports usage of device-native emoji sets so that UnifontEX emoji are usable
@stgiga@blahaj.zone Except your instance does not run 🐘#Mastodon, it runs 🦈#Sharkey (a fork of 
#Misskey, which itself was developed independently from Mastodon so is not a fork of the latter). If you want a more general, software-agnostic term, then call it a #Fediverse instance.
@silsinn9821@makai.chaotic.ninja It's like how I call X.com Twitter.
@stgiga@blahaj.zone Even #Mastodon is not the original #Fedi software. That title belongs to an extinct software that’s even older than #GNUSocial & #Hubzilla (which both are older than Mastodon). For more details on Fedi history, check this timeline compiled by @youronlyone@c.im/@youronlyone@catodon.social who corrected some of my own misconceptions & wrong thoughts about Fedi stuff.
@stgiga@blahaj.zone @youronlyone@c.im @youronlyone@catodon.social & talking about #Fedi history by the way, since the doc itself says it is a living doc, there are a few notable instances not yet mentioned there that were recently developed by high-profile (or at least notable enough for us) Fedi users & might have verifiable links or posts that can give them a place within the doc’s timeline:
• #Fedibird (#Mastodon fork) by @noellabo@fedibird.com
• #Sharkey (a very popular #Misskey fork) by @Amelia@transfem.social (& others from the @Sharkey@shonk.social project) since 2023
• maybe #IceShrimp (#Firefish fork?), unsure if it’s notable enough for inclusion or if supported by verifiable links (even I don’t know who created it).
I leave it up to @youronlyone@c.im whether certain popular extensions (if not forks per se) like #GlitchSoc (extending Mastodon) & #Soapbox (extending or modifying #Pleroma) can be added to the timeline as well.
Also, I will definitely not suggest for inclusion (or even a footnote mention) a certain #Akkoma fork that was given an obscene name by a fringe group of people (let’s just pretend it never existed, OK?) 
@silsinn9821 I'm trying to think of a way to include forks, but it's so hard to set a criteria.
If we follow Wikipedia's, notability is still subjective. However, by not setting any criteria, it will end up listing everything; and it's already challenging finding the first release dates of projects, especially forks. ^^;;
Maybe popularity? A combination of number of instances in existence + total daily active users?
But, yes, I need help finding the first release date of projects. I usually rely on when it was first forked, and then enter it in web.archive.org/save and archive.ph.
^_^
@noellabo @Amelia @stgiga @Sharkey @youronlyone@catodon.social
@youronlyone@c.im @silsinn9821 @Amelia @stgiga @Sharkey @youronlyone@catodon.social
The release date of Fedibird is 2019-08-17 based on my public post when I opened fedibird.com.
https://fedibird.com/@noellabo/102630319639736459
However, the software has not reached stable release 1.0 yet.
The repository was forked from Mastodon on Github at "created_at": "2019-06-01T12:07:59Z".
curl https://api.github.com/repos/fedibird/mastodon | jq '.created_at' [参照]
