Hmm sinon je vois que sur la PWA de #Iceshrimp y a le même bug que sur celle de #Firefish, (Firefox/Fennec) qui est que quand on va sur Partager ça prend en compte un clic sur ce qu'il a en dessous c'est hyper chiant ... :pikaneutral: y en a d'autre qui on se problème ou c'est juste avec Fennec/Firefox ??
A lot of people get annoyed by #Mastodon because of its lack of features.
I get annoyed because alternative #Fediverse software gets shafted when it comes to apps and other services.
Sure, these alternatives can integrate the Mastodon #API but that means, if they have more features than Mastodon, they will get bottlenecked when it comes down to the Mastodon apps.
Take #Iceshrimp, a fork of #Firefish in the #Misskey lineage, it (like the other Misskey forks) has a lot more bells and whistles than Mastodon, such as the Drive (for better attachment and file use) and MfM (Misskey-flavoured #Markdown).
If I want to take advantage of any of that, I either have to go to the PWA of my instance, which is not the best on mobile, or find one of the few native Misskey apps on #iOS.
I would much rather not Mastodon have a monopoly on the Fediverse but hey, it already seems to considering all the fucking articles by the major online news sources not even blinking at the mention or focus of alternatives, bar Meta Threads and Wordpress.
It is turning into or already has turned into centralisation by proxy due to the one single lead in a sea of creativity and untapped potential.
We are all in this together, we need to build better infrastructure for other software.
#Pixelfed, as a photo-based social platform, isn't affected by this issue. This goes for any of the other types of software besides #Microblogging.
I'm kinda tempted to move this instance over to #iceshrimp due to the better Mastodon API compatibility, I can't get Icecubes to work on here but on infosec.town which is currently running Iceshrimp it works like a charm and there are lots of noticeable performance upgrades on Iceshrimp too.
While it doesn’t have all the same features, the #Plemora installation I’m testing seems to work better overall, between the speed and the ability to use the Mastodon app on my phone. Still hoping I can figure out how to update from #Calckey to #IceShrimp as that would be best of both worlds…
As seen in the first image, handles are broken when there are full stops in the username part of the handle.
The second image is what it looks like on #Mastodon. I'm not sure what's causing this, but it's a little concerning as it means that #Iceshrimp users can't mention people on Wordpress / BridgyFed or any other platform that uses this format.
The handle is mentioned fine when sent from a Mastodon account, but the link hasn't worked on my Iceshrimp account.
I can still follow the user, I just can't mention them.
Currently the interface is very similar to Misskey and Firefish, but through time, as this promising fork grows, we will update the Wiki with Iceshrimp specific articles.
After testing Sharkey on my homelab, it seems that Sakurajima Social running it runs a lot smoother than Firefish (also the local timeline actually loads quickly without erroring out).
While I do have to set up Meilisearch in the near future, things are pretty good, although things from Misskey will look different compared to Firefish.
If any Firefish servers want to take the plunge, I did kept a copy of all the steps that we needed to take in a text document. I can publish it in a blog post if there are those who are interested.
please, sea creature key forks, stop sending my viewport down a page when i click the context menu button on a post (usually to get to the source instance)
and yes all three of them (that i know of) do that and it's a pain, misskey doesn't #firefish#sharkey#iceshrimp
I think MissRirica is the best Misskey app on iOS. I use it with my Sharkey accounts at ambrosia.moe & transfem.social and can't wait until blahaj.zone moves over to Sharkey so I can use it again. It's essentially the PWA in a wrapper and it has support for antennas, the Deck UI, and multiple accounts - all features which I absolutely must have access to.. These options don't exist in Kimis, the app Firefish had planned to fork for its own app. MissRirica used to work with Foundkey & Firefish accounts, but the app devs dropped support of the older version of Misskey that they and Iceshrimp fork from.
So maybe instead of more forks that focus on rolling out new features, could the devs of Foundkey, #Firefish, #Iceshrimp, et al work on your architecture so that even a relatively small (in comparison to some of the Misskey and Mastodon servers) 1500 user server, let alone a 4000 user one can function without falling over, suffering extended timeouts, having server costs blow out thanks to database performance issues, and then decimate it's community when folks are forced to migrate, and then those folks struggle to get their data exported.
So much front end work and not enough backend is the present legacy of the pre-Misskey v 13 forks.
Sakurajima Social is moving to Sharkey from Firefish. They similarly cite increasing slowness as they scaled, with mention of blahaj.zone planning to move away from Iceshrimp. to Sharkey The future is Misskey v13 if you run a *key server that wants to affordably scale.
15-20 minutes to load last batch. As I mentioned before, one gots to be patient. Lol.
Slow search is not unique to iceshrimp in the fediverse. I have experienced similar things on a large friendica server.
I wonder how iceshrimp's search capabilites would hold up on a server 1000 users or more. Would iceshrimp even want to have software that supports such server size?
Just a note, iceshrimp may have only started to get slow for me after I loaded dozens if not hundreds of results initially.
been trying out #iceshrimp on a very nice instance - so far the differences might be too subtle for me to really recognize, but it does work very (maybe a little moreso than firefish) smoothly.
We had quite a bit of this here at blahaj.zone back on #Calckey 14 when our MAU rose considerably. A move to #Iceshrimp didn't help. Trying to cut down costs by moving hosting introduced more unforeseen issues. We've lost a fair few people but we're more stable now. We're looking at moving to the #Sharkey fork of #Misskey v13 (which itself is a major revision & rewrite and not compatible with FF/IS) which seems to scale well by the looks of the massive instances that run it. But all this has been a big downer, and a lot of downtime. The reality is English-language forks of Misskey have never been tested at scale and when things go wrong trying to any documentation is difficult and most likely in Japanese. They've usually just commenced with a small single instance with some non-stock features added. I hope our eventual move to Sharkey doesn't come with a similar surprise, but seeing it sticks closely to upstream Misskey I think it might be ok.
:iceshrimp: Nouvelle MàJ 2023.11.1 Stable d’#IceShrimp !
Changement d’UI/UX
La mise en page «Centré» a été supprimée
La liste déroulante de choix de mise en page a été remplacée par un bouton qui fait alterner entre défauts et Deck.
Dans le style de TW «moderne», les boutons prennent la largeur de la zone cliquable.
La page de connexion OAuth a été entièrement retravaillée pour n’afficher que les informations essentielles.
Les infobulles ne sont plus affichées lors de la saisie sur écran tactile.
L’icône pour «marquer toutes les notifications comme lues» a été changée en ph-checks pour mieux refléter l’action.
Une nouvelle catégorie de préférences nommée «Bien-être» a été ajoutée pour permettant de masquer certains éléments addictifs de l’interface utilisateur.
Les posts en «Local seulement» ne sont plus affichées pour les visiteur·ice·s sans compte.
Les canaux ne sont plus visibles pour les visiteur·ice·s sans compte.
#IceShrimp, a fork of #Firefish will switch it's API authentication from MiAuth (a custom authorization scheme) to OAUTH. This will increase compatibility with various Mastodon apps. Currently out in a pre-release version.
olalala fuat que j'aille dormir, je suis retombé dans le rabbit hole de la customisation
j'ai changé totalement de thème en m'inspirant en partie de kwak.cab, jai redesigné les hashtags, mentions et URL et quelques autres trucs d'accessibilité (vrai thème opaque notamment)
j'essaie d'avoir quelque chose de cohérent, lisible et simple