How unfinished is Iceshrimp.NET? CW: long (over 1,500 characters), Fediverse meta, non-Mastodon Fediverse meta
Artikel ansehen
Zusammenfassung ansehen
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
