Join Sharkey dot Org has been OFFLINE for over 2 months. The reason given was hosting issues, and this was before the whole Hetzner drama. Join Sharkey dot Org is supposed to be the gateway for people to learn about Sharkey and how they can join.
The Documentation Page (Wiki) is still up, using the subdomain, Doc dot Join Sharkey dot Org, but the URLs are broken. I have repeatedly reported the broken URLs for over 2 months (both in the Git and on their Discord Server). No one seems to want to address that.
They have a private copy of GitLab located at ActivityPub dot Software, that you cannot find via a search looking for Sharkey (DuckDuckGo, Bing, Google). That is where you can report code changes and fixes, but you would likely not know that unless you stumbled upon the URL somewhere (or someone gave you that URL).
Sharkey raised a lot of money so they can host their own content, safely, and securely. They now own their own physical server and lease the space to have that server housed (hosted) remotely. And while the lead developer promotes that server partially as a minecraft server, Join Sharkey dot Org still remains, OFFLINE.
I have pulled funding from Sharkey and will not be supporting it further until they get their act together. It is a good software, and it is my preferred method to use the Fediverse, but you would assume they would want their website working.
No matter, how you connect to the Fediverse, be if, for example, Misskey, Sharkey, Ice Shrimp, Mastodon, PeerTube, Pixelfed, Kbin, or by other means, the Fediverse instance you're using cost money. In the real world, web hosting, bandwidth, and storage space cost, money. And the more members who use and join your Fediverse instance (server), the more resources and the most it cost.
I earned by badge, by reaching out to my administrator, and helping them by donating. And while if it was not required to make a donation or regular contribution, I like using the Fediverse. It is ad-free and decentralized, meaning, someone like Elon Musk, cannot change things for everyone, everywhere, solely on their latest mood swing. So I made the choice to help fund my corner of the collective social media network, known as the Fediverse.
This noob is testing the interconnectivity of the #Fediverse:
The word out there on the Fediverse make it seem as if all the different tools (Mastdn/P-tube/Lemmy/etc.) can interact with one another. But this is not the case, as some work both ways, whilst others only one way, or at all.
I know that such a file has to exist because emojos.in works correctly for void.rehab but I don't know enough #Rust to figure out where they're getting the path out of the server instance.
Et pour avoir accès à toute les fonctionalités, on a souvent recours au multicompte.
Pourquoi ne pas avoir une seule appli qui crée un compte maitre sur notre ordi et syncronise tes posts, tes abonnements, tes filtres ? Si l'instance tombe en raison de son budget, problème technique on conserverait nos données et on pourrait migrer facilement.
Cette meme appli pourrait gérer les alias. Et également cross-signer notre identité sur les appareils utilisés ?
Qu'en pensez-vous ? Ya des projets en ce sens ? Quel en serait le risque ou les limites ?
Pour moi l'oblectif est de faciliter la sauvegarde et l'exportation des données.
@Aakerbeere
Ich habe die Lichter sämtlicher Accounts bei Meta und "X" ausgeschaltet und bin nur noch im Fediversum unterwegs, und das sehr gern. 💯 Das war für mein persönliches Social Media Online Leben das Beste, was ich bisher getan habe. #mastodon#iceshrimp#pixelfed#fediversum
Présentement en train de faire un thème clair pour #Misskey / #Iceshrimp.
Finalement je m'éloigne un peu de la base dont je me suis inspiré :pikasmilesweat:
single line replies in timelines for iceshrimp, firefish and potentially other derivatives. see quoted post for how it looks. extremely hacky and might mess up. will not work in sharkey or other "modern" misskey instances
requires a browser with nyative nested css and :has (so, literally anything from the last year or so)
I am sure that having a separate search process / vm like Mastodon has with Elastic Search helps in some use cases, but I still LOL at #Iceshrimp just saying fuck it, we will do full text search in Postgres.
i am considering moving our social instance to mastodon (shutting this one down, warning users for about 1-2 months to migrate over, etc.) for a better mobile experience. I don’t like mastodon’s web UI, but i can make a ton of changes there if needed. i want to hear your opinions and takes #fediverse#mastodon#iceshrimp#misskeyy
i do like iceshrimp rn tho, and i don’t want to break what works. but there needs to be a better mobile solution, and i do kinda miss my push notifications + a dedicated mobile app
I promised I'd be giving updates on #Iceshrimp's #dotnet C# rewrite -a brand new fedi platform really- so here's where we're at at the moment! The backend's basic functionality is more or less finished, although there will undoubtedly be stuff to fix and improve during beta. So theoretically you could use it, but we don't have a frontend yet so you could use it only with masto apps atm. However, the frontend is where the focus is going now, and we plan to have a basic/working frontend soon so that we can release our first beta in a couple of weeks or so!
We expect performance and server requirements to be comparable to #Akkoma. Things are about to get exciting!
I kinda wish #iceshrimp and/or #sharkey had a tumblr-style queue, I have a ton of unrelated Thoughts but don't want to spam the timeline with them.
It could work if there was a Iceshrimp/Sharkey compatible external client and if they had support for the post scheduling APIs (or just ran in the cloud).
Just curious, with the recent demise of #Firefish -- are the forks like #Catodon#Iceshrimp etc viable / sustainable alternatives? Do they share a common base, so one could expect updates into the future if they to cease to exist?
Alright, I know I haven't given many updates on #Catodon, because frankly there's not a lot to say. We're reorganizing, reprioritizing etc. Things are going slow. I haven't given up on the project, I think we have an interesting approach which is worth exploring, but we're short on human resources atm. Hopefully this will change and things will get exciting again, but we're not there yet. I'll let you know.
However, I wanna talk about another project I'm also sort of involved in lately - #Iceshrimp! So Iceshrimp also started as a #Firefish fork but they are currently rewriting the whole thing on .net/C#! Both the backend and frontend are being rewritten in C# - the frontend on Blazor. AFAIK this is the only fedi project written on .net and I'm really curious for the result!
This has been announced many months before, and Iceshrimp-js is in feature freeze, to allow all efforts to concentrate in the rewrite. Many people were skeptical because it's a huge project - which is true. So let me tell you that finally #Iceshrimp's rewrite will be entering beta soon - meaning, probably before the month is through!
This will practically be a brand new fedi platform, with a UX similar to Firefish (at least initially), with great Mastodon API support for compatibility with existing apps, hopefully with much better performance and a cleaner codebase. I'll keep you posted on how things progress!
Testing the Fediverse's interconnectivity between apps and protocols
One thing that would have been nice to know as a newbie on the Fediverse:...