February is a short month, and unfortunately, much of the Fediverse was attacked this month, leaving many server admins with a costly bill now that the crisis is over.
If you're enjoying your Mastodon, Misskey, Sharkey, Pixelfed, or other platform, perhaps consider making a donation this month.
There needs to be apps for #iceshrimp, #misskey, #sharkey, #catodon, and any other misskey forks that support reactions and full push notifications on iOS. While the webapp im using on my iceshrimp instance is okay, it cannot be a permanent solution.
Or, it would be great if @IceCubesApp supported push notifications for iceshrimp/misskey forks, but i'm guessing its a server side issue :P
Ich werde jetzt immer mal wieder die Firefish Instanzen mit aufnehmen, die ein aktuelles Update eingespielt haben.
Bei https://firefish.fediverse.observer/list kann man die übrigens daran erkennen, dass unter Ausführung (Version) 0.0.0.0 angezeigt wird. Scheinbar kann der Observer nicht damit umgehen, dass es zwei Arten von Versionsnummern gibt.
Hello again #Fediverse, I may need your #fedihelp. So, here's a list of the Fediverse software I'm about to make temporary accounts for to test all the features and differences:
So, did I miss anything noteworthy? Does anyone have any tips or recommendations before I choose a server for any one of these? I'll probably be going for the most popular server on each for improved federation and maintenance.
Note: I'm using #Sharkey right now and Misskey forks are already overrepresented, so that's why it's not included.
Is there an option on #IceShrimp where I could hide all boosts on a timeline? Or create a new timeline where it could only show posts and replies and not boosts?
I'm having a bit of a difficulty going through my timeline especially when pinched in time so I'd like to read all non-boost first.
@zotan what's the motivation for using C#/.NET for the re-write of #iceshrimp ? I'm not knocking it; I'm just curious, and the matrix/knowledge base require an account to view.
It seems like there's a rivalry brewing between #Sharkey and #Iceshrimp on which one's gonna be the definitive "Western #Misskey" of the #fediverse :sagume_think:
One could even say that there's a.. cold war going on between them 🥁:laughing_cirno:
Alright, I think we now have a better idea of what's happening with #Firefish, so I might as well give a small update. Kainoa quit, and left the project to naskya, who is a person I appreciate very much, as they've always been kind and polite and willing to help. I also think they're very devoted to Firefish, and basically were the last person actively caring about the project. As far as I know, they intend to keep maintaining and developing Firefish, and a new stable version will finally soon be released. This is great news, as you don't need to worry that your server is running unmaintained and vulnerable software. So, alarm off everybody, no need to abandon ship.
As for us, we're standing by our decision to rebase #Catodon to #Iceshrimp. The changes we want to do are long term plans, but we've started redesigning some things and, whenever we are ready, I hope we'll show you something worth your attention. So yeah, firefish, iceshrimp and catodon are all alive and valid options (the first two to be precise, for the time being). All projects share code fixes and I think we're on very good terms, here in our corner of the fediverse. Enjoy the ride.
If Firefish is going to come back, Kainoa won't have a hand in it. They quietly handed over the keys to the repo to a maintainer... who has publicly stated they aren't a programmer and are just looking after commits. Not exactly a signal things are starting back up.
Unless there is an announcement soon about someone taking up development again, I think it's safe to say Firefish is over as a Fedi platform.
Optimism wants to say that someone will, but at this point even if someone does it'll be playing catch-up to the current state of affairs. It isn't possible for someone to come off of the street and say "I'll do it" and go back to the pace that was happening last summer immediately. (But it's not impossible for me to be wrong and six months from now someone does. I'm just not banking on it happening. Even the Firefish name itself might be too damaged in reputation to even take back up.)
#Iceshrimp, #Sharkey, and #Catodon are #Misskey derivatives who are continuing onward with things. All three of them have disassociated with FF completely so it seems Misskey still has a future with non-Japanese users. (Iceshrimp even spent time on a new non triangular logo to further separate from Firefish.) Server admins who wanted to consider a Firefish instance but shied away from the drama last fall may want to follow those projects instead.
If your fedi server is still on Firefish, don't be surprised if an announcement "were taking signups on our new Plombus server, in X months Fleeb will be decommissioned" comes down sometime soon. Internet services without recent updates are asking for trouble from exploits and vulnerabilities. Also, without an active FF developer to fix standing issues (or a skilled DB admin on your instance's behalf to whittle the database and schema to fit the new system as well as possible) a cut-over migration where users don't lift a finger isn't in the cards like the Calckey to Firefish migration last September. It likely will be up to you to decide to either move your account Mastodon style (no post migration, just your follower lists and a link back to the prior server) or to just start fresh.
I completely missed that #IceShrimp was doing a .NET rewriting. That's quite exciting, there wasn't a lot of .NET #ActivityPub implementation so far, and I'm curious to see how they will tackle some of the tricky parts of the protocol.
Recently I've seen posts that #Firefish project is in trouble? Its flagship server being unavailable, and people are impatient about new releases. Sad if true, though I hope its death is slightly exagerrated. Anyhow, I've learnt that people are migrating to other Misskey forks (mainly #IceShrimp, #Sharkey, and #Catodon) And Iceshrimp devs are rewriting the JS backend on C# 😯
It's almost time. We're super-excited. #FediGroups is entering public testing now, before a full live launch.
Many of us have used other Boosting Groups, but they only work well if you follow from Mastodon accounts. We know there is a wider fediverse. FediGroups works with all the favourites, including #Mastodon, #Firefish, #Iceshrimp, #Catodon, #Sharkey, and more. One big happy family 👪
🆕 blog! “Rebuilding FourSquare for ActivityPub using OpenStreetMap”
I used to like the original FourSquare. The "mayor" stuff was a bit silly, and my friends never left that many reviews, but I loved being able to signal to my friends "I am at this cool museum" or "We're at this pub if you want to meet" or "Spendi…
@Edent Knowing you can't see likes or replies on the location posts, let me report that both my accounts can see photos and parse the alt-text correctly.
It appears neither can handle the location in the way you intend though. I'll use your form of words from the Mastodon Issue to pop one on the #IceShrimp repo if that's OK.
Kinda big day tomorrow as catodon.social's getting updated to our latest dev version, since our announced rebase to #Iceshrimp is finished, which means that, if everything goes well, after tomorrow catodon.social will have all of the performance improvements of Iceshrimp, including full Mastodon API support. It took us back a few weeks but we think it was worth it, and now we can resume development towards our first release. #Catodon
Ehrlich gesagt, ich selber habe die Option @firefish im #Fediverse noch nicht ausprobiert aber der @mho hat darüber berichtet und der @crossgolf_rebel eine ausführliche Anleitung dafür geschrieben. Für mich ein sehr guter #Input und erweitert mein #Wissen über das #Mastodon weiter hinaus.
Ob dem nun so ist wie ich es wahrnehme, muss ich mich mal damit auseinandersetzen. Die Unterschiede im Detail interessieren mich und sind wahrscheinlich auch Argumente für diese #Fediverse Anwendungen. Weshalb ich darauf komme und Details siehe oben.