Does anyone know why full text search is not working on #firefish. Search is returning only hashtags. Antenna feature picks up on all keywords so I know it's possible.
@FortunateFool I just launched a reindex. I don’t know for sure what is wrong, but the search engine appears to be running. It’ll take a few hours to complete.
So I am a bit confused over this ability to search. While the search function in #Mastodon has been very limited I have just repeated the same search on #Friendica and #Firefish and got lots of results compared to the same search on Mastodon.
These results have not been from posts that I have liked, boosted or commented on.
Have Friendica and Firefish always had a better search functionality than Mastodon?
Do they respect the option to not be included in searches?
Sooo dann möchte ich den Interessierten mal den S3 Anbieter vorstellen, den ich entdeckt habe. Ich dachte bei dem Namen "Xaweho" erst an eine chinesische Firma, jedoch ist es ein deutsches Unternehmen mit Sitz in Xanten (das liegt bei Essen / Düsseldforf)
Die Vorteile sind fast schon einzigartig:
-keine Traffickosten egal welche Richtung
-nur 3,79€ pro TB im Monat
-so viele Buckets, User, ACL wie man möchte
-keine Bandbreitenlimitierung.
Damit ist das Angebot sogar noch besser als das von Contabo
Das Ganze wird sehr einfach erreicht: Man bekommt seine eigene MinIO Instanz auf deren Servern. Alles ist redundant angebunden.
Ein extrem faires Angebot und ich nutz es nun für meine Backups. Ich möchte noch Mastodon darauf umstellen. Interessant dürfte das für jeden größeren Instanzadmin sein, da ja auch Firefish, Lemmy und auch Misskey ein S3 Backend anbieten.
Feditext only supports instances that have a Mastodon-compatible API.
that includes Mastodon and forks like Glitch that extend the Mastodon API (though i haven't tested against Hometown, Fedibird, or Treehouse). it also includes GotoSocial, which is targeting API compatibility up to Mastodon 4.1 where it makes sense, and Akkoma, which has long used an extended Mastodon API based on, i think, either late Mastodon 2.x or early 3.x, but it's close enough for our purposes. i have not tried snac yet.
it doesn't include Misskey, which doesn't have a Mastodon-compatible API at all, or Calckey, which started building one but didn't reach usability until the Firefish rebrand. Firefish and Iceshrimp still have a little way to go but they're pretty close; i've sent in a few small patches myself to help that along.
Are there any #fediverse platforms that don't compress or others ruin image uploads? #mastodon reduces many images to under 2000 pixels in either direction, usually in the 1600-1800 range from what I've seen.
The flagship #Misskey instance is experiencing growing pains, but is also discouraging #Fediverse residents in #Europe (or rather the #EuropeanUnion 🇪🇺) from signing up due to #GDPR issues.
👉🏾 Misskey (https://misskey.io) signing up 20,000 new users per day
👉🏾 After consulting lawyers, Misskey.io will now discourage Europeans from signing up
👉🏾 #Firefish could fill in the vacuum in Europe
@osma Thanks for that link. I will show it to the #Misskey (https://misskey.io) admins, as it may allow them to retain data under #Japan’s 🇯🇵 laws without violating #GDPR laws.
@osma@darnell I believe the concern is the right to be forgotten hasn’t been tested in court for many if any federated platforms but people have used this rule to try and get their accounts deleted.
On mastodon deleting an account still keeps some identification for security and platform reasons and deletes when federated are extremely lossy - probably only about 85% effective and there is no assurance that remote post and account deletes guarantee a delete on the remote system when you can land on any type of fedi implementation.
I had two people try and claim GDPR right to be forgotten but ironically to protect myself I had to move their accounts to another system to track compliance of requests and cover my butt for any legal pursuers. They were running a fraud scheme.
Wenn ich mit #Fedilab versuche zu einem procial.tchncs.de Account zu verbinden erhalte ich den Fehler: Fehler beim Laden der Client ID
Mit federation.network scheint das zu funktionieren. Beide laufen auf #Firefish Version 1.0.3.
Woran könnte das liegen? Vielleicht habt Ihr einen Tipp? @milan@apps
It seems there is an issue with the Mastodon API on this instance (I don't know how it works though).
But for example a simple public API call on calckey.word gives:
@apps mmh still sadly couldnt find a clue as to why this happens.. searched quite a while again now... @kainoa, perhaps if we frame that issue differently based on this finding (also added to the gitlab discussion), it might become valid? @fexplorer@mrwslpro@hippokratius
The #Firefish word #trademark is registered for NICE classes 9, 41, 42, i.e. computer software and services etc., for the whole of the European Union (and I believe for the UK too, not checked). Server admins in those jurisdictions, you may want to avoid domains containing the word or at least get legal advice before deploying a server with such a domain - this could potentially be costly otherwise.
@choyer@sin@fediversenews to add one more example: gmail.pl was registered to some person and hosted a website for book lovers (that translated into gmail acronym). Court in Poland denied the claim to this domain and Google eventually paid him.