Still in bed but today I’m off work so plan to work more on porting over the Akkoma fronted to the *key API(Sharkkoma). Made some good progress and want to keep interating to get it fully working.
Ich habe hier einen #RasPi 4 und eine große SSD bereitstehen. Gerne würde ich eine eigene #Fediverse-Instanz aufsetzen, gäbe es nur irgendwo eine praktikable Anleitung, z. B. für #akkoma
Was ich finde, ist entweder nicht #Raspbian-geeignet, veraltet oder nutzt unverständlicherweise #docker.
no matter what safeguards you try to build to help internet users, the modern web is enough of a cesspool that some asshole is going to come up with something like this.
I've been using Dissenter web browser, but sadly it became abandoned/obsolete, so I was forced to use Brave. However I noticed a problem with CDRomTokyo: it gets blank, same problem at the android phone. And I get so many issues at MiniDisc Tokyo too. Why?
Should I use another web browser?
Please recommend me a good web browser for Linux and android so I could use those sites that I like so much.
If this "privacy setting" for #quoteposts is implemented with it enabled by default, the result will be disastrous. :reisensweat: Since there is no other way to enforce this setting other than #defederation, we are going to see Mastodon servers strong-arming those software developers who are "non-compliant" by threatening a #fediblock. :reisensweat: Developers of the -key and -oma families will suddenly have to scramble to make their implementation of #quotetweets compatible with Mastodon's "privacy-friendly" implementation. :satsuki_sadge: This way of "extending" the fediverse is not acceptable, and everyone who has opposed #Facebook joining the fediverse due to #EmbraceExtendExtinguish should also oppose this issue which just eventually leads to the same result.
"This document is dedicated to all citizens of planet Earth. You deserve freedom of communication; we hope we have contributed in some part, however small, towards that goal and right."
@phpmacher Meine Alternative ist, nicht mehr Mastodon zu nutzen, sondern #Akkoma, wo ich das Zeichenlimit auf 100.000 gesetzt habe und Posts formatieren kann (z.B. mit Markdown, HTML oder BBCode). Blöderweise werden die meisten Formatierungen von Mastodon wieder entfernt.
Dieser Text ist fett.
Dieser Text ist kursiv.
Ich
bin
eine
Liste.
@natenom ist auf der Mastodon-Instanz von digitalcourage, die den Default-Parameter fürs Zeichenlimit erhöht haben. Das ist von Mastodon im Upstream leider nicht vorgesehen und muss jedes Mal wieder händisch zurückgepatcht werden.
Fuck yeah! it is possible to backfill posts from Akkoma into Sharkey when doing an inplace migration! I need to smooth it out, but successfully pulled posts from my first test migration over. Still planning a more indepth full scale test2 this weekend.
As it is, the timestamps on the post are the time of import. My initial test account didn't have many posts to verify with, but that's fine. That's what the full scale test this weekend is for. The core works though, which is fucking cool :apartyblob:
Do you have a solo #mastodon or #akkoma#instance? Is it worth it? What are the drawbacks & benefits in your opinion? Is it painful to setup and/or maintain?
Ich muss da leider heute noch ein paar Tests mit den Gruppen-Providern
gup.pe
und
chrip.social
machen und bitte um euer Verständnis.
Ich habe da erhebliche Probleme, überhaupt die Gruppen-Inhalte darzustellen. Auch mit der Einrichtung dieser Gruppen gibt es erhebliche Probleme, insbesondere mit #Firefish und #Friendica. Damit habe ich überhaupt nicht gerechnet, dass das alles so schwierig werden würde.
Am besten funktioniert das mit den beiden Providern alles noch mit #Akkoma und #Mastodon, womit ich auch nicht gerechnet habe, dass ich diese Dienste da jetzt zum Korrekturlesen benötige.
Zum Verständnis meines Usecases für Interessierte dieser Testserie, verlinke ich einmal meine neue Firefish-Nutzerseite zu diesem Problem. Wenn ich keine zufriedenstellende Lösung finde, werde ich nach einer Friendica-Speziallösung suchen. Die Friendica-Gruppen funktionieren ja nun leider auch wieder ganz anders.
@jakob Das könnte ein #Akkoma-Problem sein. Der editierte Beitrag wurde in diesem Fall jedenfalls nicht zu meiner Instanz propagiert, selbst wenn ich ihn aktiv aufrufe, danach suche, den Browser-Cache lösche etc. Das ist interessant. Mal gucken, ob bereits ähnliche Probleme der Software bekannt sind.
There are now 5 Turtle Island instances to choose from.
Extremely configurable individual user themes
5000 character posts (configurable to even more)
Plain text, HTML, Markdown, BBCode, MFM posts
Quote posts
Local only posts
Bubble timeline
A lot of reactions, emoji, animations
A: You can limit who can send you DMs/PMs! You can also limit notifications!
B: You can also block a site entirely for yourself.
See attached pics for how.
2: Instance administrators:
If you don't want to block threads.net entirely, consider these options for your userbase's safety:
A: Between "Full federation" and "Suspend" there is LIMIT, which hides content from an instance unless a user either follows the user posting it, or searches for it.
B: There is also "Reject media," which means you never cache a remote site's attachments. This de facto makes all such content sensitive ("unavailable"), requiring an additional click to view.
If people running other software could reply to this showing how to do similar actions on other platforms such as #Misskey#Akkoma#FireFish and so on, that would be very helpful.
What’s the difference between #Mastodon and #Firefish? They both seem to be microblogging platforms in the fediverse. Are they able to talk to each other? I’m a bit ignorant on this atm.
They all have their specificity but they can all communicate (via Activitypub). For example, Misskey and its forks (Firefish and Iceshrimp) can make emoji reaction on posts or even use animations in posts like this. For Mastodon users won’t see them but that doesn’t impact on the communication.
In brief, they are all microblogging services with their own characteristics and UI :akko_thumbup:
Sussy Akkoma logo