State of the Iceshrimp, December, 2025
-
How unfinished is Iceshrimp.NET? This unfinished:
Iceshrimp.NET appears to have no support for conversations. At all. I'm not just saying it has no support for enclosed conversations like on Friendica, Hubzilla, (streams), Forte, Facebook and every last blog out there, not to mention FEP-171b "Conversation Containers".
I'm saying it has no concept of threads. It has no concept whatsoever of a message having a parent or children in a thread.
All it seems to know is stand-alone messages. Iceshrimp.NET only shows you single messages, and it gives you no way at all to access even only what these messages reply to. This is even worse than Mastodon, and that has to say something.
Also, Iceshrimp.NET seems to use some exotic, home-brew message format that must have little to do with the W3C ActivityPub standard, even taking FEPs into consideration. It's impossible to use Hubzilla's search to import an Iceshrimp.NET message onto your stream.
And: iceshrimp.net redirects to the Iceshrimp.NET code repository. Which, in turn, contains a link to an iceshrimp.net website at the top. Another to-do that isn't even on any to-do list. Yeah, I know that (streams) and Forte have no websites either, but Mike doesn't pretend they have websites, and especially (streams) has very good reasons not to have an official website.
Let's just hope that it has overcome the *key-inherent federation issues by having been rewritten.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Iceshrimp.NET #IceshrimpNET -
How unfinished is Iceshrimp.NET? This unfinished:
Iceshrimp.NET appears to have no support for conversations. At all. I'm not just saying it has no support for enclosed conversations like on Friendica, Hubzilla, (streams), Forte, Facebook and every last blog out there, not to mention FEP-171b "Conversation Containers".
I'm saying it has no concept of threads. It has no concept whatsoever of a message having a parent or children in a thread.
All it seems to know is stand-alone messages. Iceshrimp.NET only shows you single messages, and it gives you no way at all to access even only what these messages reply to. This is even worse than Mastodon, and that has to say something.
Also, Iceshrimp.NET seems to use some exotic, home-brew message format that must have little to do with the W3C ActivityPub standard, even taking FEPs into consideration. It's impossible to use Hubzilla's search to import an Iceshrimp.NET message onto your stream.
And: iceshrimp.net redirects to the Iceshrimp.NET code repository. Which, in turn, contains a link to an iceshrimp.net website at the top. Another to-do that isn't even on any to-do list. Yeah, I know that (streams) and Forte have no websites either, but Mike doesn't pretend they have websites, and especially (streams) has very good reasons not to have an official website.
Let's just hope that it has overcome the *key-inherent federation issues by having been rewritten.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Iceshrimp.NET #IceshrimpNET@jupiter_rowland@hub.netzgemeinde.eu Iceshrimp.NET lets you access reply-tos if
a: you have an account on the server
b: the server uses a proper frontend, like that port of the pleroma frontend someone made
c: you use a client that allows pointing to an arbitrary server's mastodon compliant API (e.g. Phanpy) -
@jupiter_rowland@hub.netzgemeinde.eu Iceshrimp.NET lets you access reply-tos if
a: you have an account on the server
b: the server uses a proper frontend, like that port of the pleroma frontend someone made
c: you use a client that allows pointing to an arbitrary server's mastodon compliant API (e.g. Phanpy)@jupiter_rowland@hub.netzgemeinde.eu please look at this demonstration of option C:
post on the iceshrimp server: https://not-brain.d.on-t.work/notes/af6ed8e0xrsfrv0p
post as seen through phanpy: https://phanpy.social/#/not-brain.d.on-t.work/s/af6ed8e0xrsfrv0p?view=full -
@z6Mki5zHriQp1MrWfAtMNN2WZC43uRZMquT68U4B6dptNcY1/actor" rel="nofollow noopener">Johannes Oschlies Das, was man da mit YH installieren kann, ist aber nicht die .NET-Version, sondern die alte Firefish-Fork-Version aus dem Dezember 2023.
-
How unfinished is Iceshrimp.NET? This unfinished:
Iceshrimp.NET appears to have no support for conversations. At all. I'm not just saying it has no support for enclosed conversations like on Friendica, Hubzilla, (streams), Forte, Facebook and every last blog out there, not to mention FEP-171b "Conversation Containers".
I'm saying it has no concept of threads. It has no concept whatsoever of a message having a parent or children in a thread.
All it seems to know is stand-alone messages. Iceshrimp.NET only shows you single messages, and it gives you no way at all to access even only what these messages reply to. This is even worse than Mastodon, and that has to say something.
Also, Iceshrimp.NET seems to use some exotic, home-brew message format that must have little to do with the W3C ActivityPub standard, even taking FEPs into consideration. It's impossible to use Hubzilla's search to import an Iceshrimp.NET message onto your stream.
And: iceshrimp.net redirects to the Iceshrimp.NET code repository. Which, in turn, contains a link to an iceshrimp.net website at the top. Another to-do that isn't even on any to-do list. Yeah, I know that (streams) and Forte have no websites either, but Mike doesn't pretend they have websites, and especially (streams) has very good reasons not to have an official website.
Let's just hope that it has overcome the *key-inherent federation issues by having been rewritten.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Iceshrimp.NET #IceshrimpNET -
How unfinished is Iceshrimp.NET? This unfinished:
Iceshrimp.NET appears to have no support for conversations. At all. I'm not just saying it has no support for enclosed conversations like on Friendica, Hubzilla, (streams), Forte, Facebook and every last blog out there, not to mention FEP-171b "Conversation Containers".
I'm saying it has no concept of threads. It has no concept whatsoever of a message having a parent or children in a thread.
All it seems to know is stand-alone messages. Iceshrimp.NET only shows you single messages, and it gives you no way at all to access even only what these messages reply to. This is even worse than Mastodon, and that has to say something.
Also, Iceshrimp.NET seems to use some exotic, home-brew message format that must have little to do with the W3C ActivityPub standard, even taking FEPs into consideration. It's impossible to use Hubzilla's search to import an Iceshrimp.NET message onto your stream.
And: iceshrimp.net redirects to the Iceshrimp.NET code repository. Which, in turn, contains a link to an iceshrimp.net website at the top. Another to-do that isn't even on any to-do list. Yeah, I know that (streams) and Forte have no websites either, but Mike doesn't pretend they have websites, and especially (streams) has very good reasons not to have an official website.
Let's just hope that it has overcome the *key-inherent federation issues by having been rewritten.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Iceshrimp.NET #IceshrimpNET -
wäre ja schön, wenn es die neue Version vlt. auch einmal über yunohost gäbe, zum mal ausprobieren.@z6Mki5zHriQp1MrWfAtMNN2WZC43uRZMquT68U4B6dptNcY1/actor" rel="nofollow noopener">Johannes Oschlies Hätte Dir jetzt am liebsten von Iceshrimp.NET geschrieben, wenn denn Dein Forte-Kanal dort zu finden wäre. Da versagt der Dienst aber.
Registrierungen erlaubt z.B. #^https://shrimp.social/ (wo ich einen Test-Account habe@DerPepe@shrimp.social).
Bis jetzt kaum wirklich nutzbar... nach meinem Empfinden. -
How unfinished is Iceshrimp.NET? This unfinished:
Iceshrimp.NET appears to have no support for conversations. At all. I'm not just saying it has no support for enclosed conversations like on Friendica, Hubzilla, (streams), Forte, Facebook and every last blog out there, not to mention FEP-171b "Conversation Containers".
I'm saying it has no concept of threads. It has no concept whatsoever of a message having a parent or children in a thread.
All it seems to know is stand-alone messages. Iceshrimp.NET only shows you single messages, and it gives you no way at all to access even only what these messages reply to. This is even worse than Mastodon, and that has to say something.
Also, Iceshrimp.NET seems to use some exotic, home-brew message format that must have little to do with the W3C ActivityPub standard, even taking FEPs into consideration. It's impossible to use Hubzilla's search to import an Iceshrimp.NET message onto your stream.
And: iceshrimp.net redirects to the Iceshrimp.NET code repository. Which, in turn, contains a link to an iceshrimp.net website at the top. Another to-do that isn't even on any to-do list. Yeah, I know that (streams) and Forte have no websites either, but Mike doesn't pretend they have websites, and especially (streams) has very good reasons not to have an official website.
Let's just hope that it has overcome the *key-inherent federation issues by having been rewritten.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Iceshrimp.NET #IceshrimpNET