Find the latitude of any place.  

For nikokenoxArt by me

For nikokenox
Art by me

Now I'm wondering again:
Let's suppose I have a series of 3-D virtual world images that have a plain white background because they were intentionally created in front of a plain white background. It's impossible to tell from the images where they were made, and when I post them, it won't matter within the context where they were made.
Any chances that someone out there might still want to know where exactly I've made these images Either someone who doesn't know about these worlds, and who is totally curious about them, or one of those probably fewer than 20 Fediverse users who does know about these worlds, and who wants to know where I've gone to make these images
I can easily spare the few hundred extra characters. The only character limit I have to worry about are the 100,000 characters above which Mastodon probably rejects a post from outside.

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #Inclusivity #A11y #Accessibility



For those

who celebrate it
Hope
received some
good Presents
+
had a nice
Dinner
with your loved ones.
Now time for
next

Another
to
back
Unlike
-23 w/
where wall filled
in
had written their names
There
Daisy's hair

Here w/
Daisy's hair
+
If want to compare

To be fair, these aren't all general Fediverse issues. It isn't like the whole Fediverse has them. They just seem to be general Fediverse isses if all you've ever experienced first-hand in the Fediverse is Mastodon, and if you think the Fediverse is mainly a Twitter-like microblogging platform with YouTube, Instagram and TikTok clones glued on.
For example, the issue of replies is mostly one on Mastodon because of how Mastodon has always tried to ape Twitter. Mastodon doesn't know conversations. Those who only know Mastodon are keen to deny this and say that Mastodon does know conversations. But those who have experienced Friendica, Hubzilla and/or (streams), not to mention the Threadiverse, know what support of conversations in the Fediverse can really be like.
A key element of conversations is the distinction between posts and comments. In conversation models, posts only ever stand at the start of a conversation, and everything that follows is not a post, but a comment. And this exists in the Fediverse. It has been around for much, much longer than Mastodon which does not and doesn't want to distinguish between posts and comments.
Friendica was launched in July, 2010, five and a half years before Mastodon. For as long as Mastodon has been around, it has been continuously federated with Friendica.
But Friendica is not another Twitter clone. It was created as an alternative to Facebook, but better than Facebook and with full long-form blogging capabilites among its features. Now, blogs have a one-post-many-comments conversation model, and so does Facebook. So, logically, so does Friendica.
On Friendica, a conversation isn't post-by-post piecemeal, and it isn't shown as piecemeal. It is shown as a whole with the post at the top, a comment tree below and the comment entry mask at the bottom. Same as on blogs or forums or Facebook etc.
Now here comes the actual kicker: Once you receive a post (remember the distinction between posts and comments), you also receive all comments. From people whom you don't follow and who didn't mention you. Even from accounts on instances which the Friendica node you're on has never heard of. Whenever someone replies to a post you've received in the past, whenever someone replies to a comment on a post you've received in the past, you get that reply onto your list of unread activities.
That's because you don't receive that reply from the replier. You receive it from the original poster who owns the whole thread.
Better yet: This entire system works without mentions. Mentions are only for show if you comment on a comment so that it's clear whom exactly you're replying to. That is, on today's Friendica, even that isn't necessary anymore because Friendica has switched from a strictly chronological comment order to a comment tree.
It's funny how the Fediverse sees this as something between utopic science-fiction and entirely inconceivable. But for the Fediverse, Twitter has always been the gold standard, and everything that works differently is weird, even the much, much bigger Facebook.
Hubzilla has inherited this behaviour from Friendica. After all, it was built from a Friendica fork from 2012 by Friendica's own creator, Mike Macgirvin , and it itself emerged in 2015, still ten months before Mastodon. And again, Mastodon has always been federated with Hubzilla. In fact, when Mastodon introduced ActivityPub in September, 2017, even then it connected to Hubzilla via ActivityPub because Hubzilla had implemented it in July.
The key difference is that Hubzilla added extensive permission controls to the mix. On Hubzilla, a conversation always has the same permissions all over. Comments cannot have different permissions than the post, and the original poster can't change the permissions after posting anymore.
Another step in the evolution is the streams repository which contains a decentralised social networking application that's officially nameless, but commonly referred to as "(streams)" in parentheses. It's a fork of a fork of three forks of a fork of probably another fork of Hubzilla, all forks in this chain and all the way back to Friendica are by the same creator, and it's from October, 2021.
Like Friendica in the meantime, and unlike Hubzilla where conversations are still strictly chronological, (streams) has tree-style comments sections.
About a year ago, the conversation model on (streams) was reworked again into something that was named "conversation containers". Mike explains them in :
(Start quote)
In the microblog model, Francis posts a message and it goes to all his followers. Taylor responds and the response goes to all her followers. Taylor's response is rarely seen by the rest of Francis's followers. They are different conversations with completely different audiences.
In the conversation model, Francis posts a message to all his followers. Taylor responds (only) to Francis, and Francis relays the comments to all his followers.
In this way, Francis has a contained conversation. There is one audience and one set of messages that are part of the conversation. Francis owns this conversation and decides who is a part of it. Taylor's followers aren't involved in any way.
This type of construct is a requirement for providing private groups and circles/aspects in the fediverse - as these features are by definition "contained conversations". It mostly provides a range of interactions that can't really be provided by the microblog model.

(End quote)
Conversation containers have since been turned into an ActivityPub FEP, . A few days ago, Hubzilla introduced them with version 10.
And indeed, both with conversation containers and their predecessor from Hubzilla, the thread starter is the exclusive owner of the whole thread. The thread starter decides who can see the start post and therefore the whole thread. The thread starter decides by channel role and contact roles who is allowed to comment on their posts as well as on comments on their posts, and on Hubzilla, the thread starter may even optionally forbid comments on a new thread entirely.
However, this is limited when software that doesn't understand any of this comes into the mix, especially Mastodon. What does work is limiting the audience of a post and therefore the whole thread. Mastodon understands anything from Hubzilla or (streams) that isn't public as a DM, and it doesn't let you e.g. boost DMs to your own followers.
But Mastodon doesn't know permissions. Mastodon doesn't know enclosed conversations. And Mastodon doesn't know the concept of permissions being defined by the start post. And so it's possible to change the permissions for a reply to a post from Hubzilla or (streams).
Granted, you can't reply to a restricted-audience thread in public because you can't reply to a Mastodon DM in public. But you may be tempted to make a reply to a public post private and believe it actually is private. It isn't.
Also, while you, as the thread starter, can delete comments from your own threads, you can't fully undo them. A deleted comment is also removed from all copies of the thread on Hubzilla and (streams), maybe also on Friendica. But the deletion is not carried out by all the microblogging instances in the Fediverse, whatever they run. And especially, if the bad comment came from e.g. Mastodon, neither Hubzilla nor (streams) can delete the post that became this comment from the commenter's own Mastodon account.
This is not a limitation on Hubzilla's or (streams)' side. It's a limitation on Mastodon's side. And it can only be fixed by Mastodon adopting conversation containers as well as a permission model like on (streams).
I can already predict that this will not happen. Eugen Rochko is too proud to adopt technology from developers of directly competing Fediverse server applications into Mastodon. His devs are brainwashed into "knowing" that Mastodon is superior to everything else in the Fediverse in any way imaginable. Mastodon itself is constantly trying to force its own proprietary designs upon the rest of the Fediverse. It's supported by Mastodon fundamentalists who think that Mastodon is the Fediverse gold standard, and "different from Mastodon" means "broken".
And adopting technology from elsewhere in the Fediverse would require Mastodon to officially acknowledge the existence of a Fediverse outside of Mastodon (plus commercial players), especially one that does certain things better than Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Conversations #ConversationContainers #FEP171b Find the latitdue and longitude of any place I'd really like to do some virtual "photo-blogging" with multiple in-world pictures in each post, especially now that so many Christmas-themed and winter-themed sims are online.
But that's completely out of question if it takes me two days or more to adequately describe one measly image. Adequate image descriptions are increasingly becoming mandatory in posts that may end up on Mastodon.
I guess that even applies to Hubzilla articles although they don't federate through the Fediverse, simply because they're on Hubzilla, and Hubzilla is part of the Fediverse. (That said, articles have the advantage over posts of not being butchered by Mastodon's HTML sanitiser.) I do have a (streams) channel for in-world picture posts, but (streams) doesn't have articles, and so it kind of limits me to the maximum of four images per post that Mastodon allows.
Also, I've yet to find a way and a place to add long descriptions for images in posts in which the images are embedded within the text rather than at the end. Mind you, I'm not talking about the alt-text I know where it goes. I'm talking about the long image descriptions which all my original in-world images get. Something that has grown up to 60,000 characters in length for one single image in the past.
So far, I've always added the long descriptions to the post itself. It's fairly easy to do if there's only one image, and it follows the actual post text with no more post text following the image. In that case, I simply add the long description after the image.
If there are multiple images, that's when things get tricky. I've tried adding each description right after the corresponding image for three images. I only had a wee little bit of actual post at the very beginning in this case. Still, there are over 37,000 characters of image description between the first and the second image. If Mastodon supported embedded images, hardly anyone would ever even scrolled down to the second image, much less the third one.
What seems to have worked better was what I did here and here with two images: First the post text, then the images, then the common image description preamble, then the individual image description parts for each image. The major downside is that there's a lot of text between each image and its corresponding description. And still, the actual post text is above the first image in its entirety.
Especially the third link leads to an image post in which I've "cheated" by reducing the surroundings to a minimum and the necessary image-describing effort along with them. It still took me eight hours to describe and explain both images, not including the alt-texts distilled from the long descriptions. And I still ended up with over 20,000 characters for the whole image description block.
Virtual photo-blogging would be something else. It'd show much, much more surroundings, probably more than in the first image post I've linked to. And it'd mean four images per post. Even if I didn't describe, explain or transcribe anything more than once, describing four images with a lot of landscape and decoration in them at sufficient levels of detail would take me well over a week, mornings to evenings, provided I can actually dedicate such a big chunk of time to nothing but describing images.
Also, the resulting image descriptions would be so massive that if I put them into the post, the post probably wouldn't go anywhere but Friendica, Hubzilla and (streams) because it'd simply be too long. Mastodon, where accurate and adequately detailed image descriptions are a must, rejects all post over 100,000 characters as far as I know, and my post would exceed this limit. Pleroma and Akkoma have a lower limit, and I guess Misskey and its forks have even lower limits.
A while ago, someone suggested to me that I could upload the long descriptions someplace else and then link to them in my posts. That'd shorten and clean up the posts immensely, and it'd work with images embedded in-between sections of post text.
I've actually toyed with the idea and how to carry it out without having to rely on anything outside of Hubzilla. Ultimately, I've pretty much nixed it. Not only because it's untested and unreliable, but mostly because every image description except for the first would grow tremendously in length.
That's because all information that's relevant for all four images would have to be in all four image descriptions. If I have four image description files, each one with its own link below the corresponding image, I can't count on everyone opening the first description first, then the second description and so forth. But if someone only opens the description for the third or the fourth image, I want them to have all relevant information regardless without sending them to the previous descriptions.
Granted, it's probably more inconvenient for the readers than for me. If I need something four times, I can copy-paste it three times. The readers, on the other hand, have to endure largely the same unprecedentedly massive infodump up to four times over in one post. Even more often if a photoblog post continues in comments or other posts to include more than four images.
Still, not only do the readers have to deal with a whole lot of information to be able to fully understand my images, but I have to research and write it in the first place. Three or four photo-blogging posts with four images each, and I won't get to do anything else than describe images for a solid month.
Lastly, I'm not going to cut down the detail level of my image descriptions any further. I know that at least some people enjoy them. And I've hardly ever been criticised by sighted people and never by blind or visually-impaired people, let alone sanctioned by Mastodon's alt-text police, for writing too long and/or too detailed image descriptions. Maybe the alt-text police has yet to notice my image posts.

#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #Inclusivity #A11y #Accessibility
So why does your post render as text in Mastodon Has Mastodon embraced Hubzilla but still reject writefreely

As I've explained above:
Hubzilla saw this as an act of aggression and of trying to exclude Hubzilla content and reacted upon this by switching from Article-type objects to Note-type objects,

Essentially, Mike Macgirvin, creator and then still maintainer of Hubzilla, saw Mastodon's turning Article-type objects into links as flipping the bird at Hubzilla. Mastodon users couldn't read Hubzilla content at all anymore unless they took the extra step to open it at the source. Even comments. This reeked of either intentionally making Hubzilla look broken from a Mastodon POV or trying to sanitise "the Fediverse" from everything that isn't Mastodon.
Thus, Mike switched Hubzilla from sending Article-type objects to sending Note-type objects. The same type that Mastodon itself sends. Mind you, still with all formatting shebang. Even though that's against the spec.
WriteFreely, on the other hand, still sends Article-type objects. WriteFreely doesn't rely on its posts being read in Mastodon timelines. Also, you can't comment from WriteFreely blog accounts.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #WriteFreely #ActivityPub Try Mike Macgirvin's various creations:

Common perks for a writer like you:

Extra perks on Friendica and Hubzilla:

Extra perks on Friendica:

Extra perks on Hubzilla and (streams):

Extra perk on Hubzilla:

Extra perks on (streams):

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #LongForm Eine Suche, die 100% des ganzen Fediverse abdeckt, ist im Grunde technisch nicht mglich.
Entweder hast du dezentrale Suche. Also: Jede Fediverse-Instanz kann alles auf jeder Fediverse-Instanz finden. Klingt erstmal geil.
Das heit aber auch: Jede Fediverse-Instanz mu jede Fediverse-Instanz kennen.
Wenn ich meine eigene -Instanz starte (das ist brigens sehr wohl Teil des Fediverse und mit Mastodon verbunden), mssen zigtausend Instanzen von weit ber 100 Fediverse-Serverapplikationen auf der Stelle wissen, da meine (streams)-Instanz existiert. Woher sollen die das wissen
Mal abgesehen, was jede Instanz fr riesige Datenmengen speichern mte. Im Grunde mte jede Instanz im Fediverse alles an Fediverse-Inhalten von berallher speichern und indizieren. Klingt erstmal geil, bis du fr deine kleine private Mastodon-Instanz einen ganzen Server-Cluster fr einige zigtausend Euro im Monat mieten mut mit terabyteweise Massenspeicher und einer Standleitung im Bereich von einigen hundert Gigabit pro Sekunde.
Genau der Grund brigens, warum es so sagenhaft teuer ist, fr Bluesky einen Relay-WebApp-Stack selber zu hosten.
Oder du hast zentrale Suche. Da wrden diese riesigen Datenmengen nur fr einen Servereigentmer anfallen. Fr den wre das aber erstens schon teuer genug.
Zweitens mte auch dieser zentrale Suchserver alle Instanzen im Fediverse kennen. Also es auch sofort erfahren, wenn irgendwo eine neue Instanz startet. Woher soll der Suchserver das wissen
Und drittens knnte eine zentrale Suche auch mal abgeschaltet oder von Elon Musk gekauft werden. Was ein Hauptgrund ist, warum sich alte Fediverse-Recken schon immer mit Zhnen und Klauen dagegen wehren, da das Fediverse von irgendwas Zentralem abhngt.
Ach ja: Falls du oder irgendjemand anders jetzt sagen wrde: "Dann nehmen wir eben nur Mastodon, alles andere ist doch sowieso scheiegal", dann werden euch so einige Nicht-Mastodon-Nutzer, die ich gut kenne, wegen Diskriminierung aufs Dach steigen. Mal abgesehen davon, da das die Probleme kaum lindern wrde.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Suche That's normal and intentional on Mastodon's side.
Whereas Mastodon sends toots as Note-type objects (the preferred type for short messages), WriteFreely sends posts as Article-type objects (the preferred type for full-blown, fully formated blog posts). But Mastodon "renders" Article-type objects as links to the original.
This behaviour dates back to 2017. In July, Hubzilla (which supports full-blown blogging with all shebang and with no character limits) was the first Fediverse project to adopt ActivityPub. In September, Mastodon became the second. Until then, both had only been connected via OStatus. And they remained the only ActivityPub implementations until after the standardisation by the W3C in 2018.
The difference was: Hubzilla went straight by spec and sent posts, comments and PMs as Article-type objects. In-bound, it supports just about everything.
Mastodon, on the other hand, only went with the spec as far as that was convenient, as far as that didn't clash with old-school, purist, minimalist microblogging. It sent and still sends toots as Note-type objects.
However, it refused to treat Article-type objects as required. Mastodon used an HTML "sanitiser" to rip out all HTML in incoming content and reduce it to plain text. Formatting, tables, lists, embedded images, all deleted. Because content with text formatting and embedded in-line images isn't old-school, purist, minimalist microblogging.
Hubzilla complained to Mastodon about the latter's way of completely butchering Hubzilla content. At first, Mastodon only justified its doing, if it reacted at all.
But for one, this meant that most Mastodon users would never see content from Hubzilla as it was intended on Hubzilla's side. Mastodon users wouldn't know that what they saw was not what they were to see, partly because Mastodon users could only tell that something wasn't from Mastodon itself by its length, partly because next to nobody on Mastodon knew that stuff like text formatting or embedded in-line images existed somewhere else in the Fediverse. So literally nobody would ever be bothered to look up content from Hubzilla on Hubzilla itself to see it in its original glory.
Besides, AFAIK, what Mastodon did was against the ActivityPub spec.
So Mastodon was torn between sanitising Hubzilla content to plain text (which angered Hubzilla) and fully rendering it in all its HTML glory (which wouldn't be old-school, purist, minimalist microblogging).
What they did was pick the third option: turn Article-type objects, which only came from Hubzilla at that point, into links to the original and not render them at all.
Hubzilla saw this as an act of aggression and of trying to exclude Hubzilla content and reacted upon this by switching from Article-type objects to Note-type objects, even though that technically went against the ActivityPub spec. Up until October, 2022, when Mastodon 4 came out, it still completely butchered anything from Hubzilla, and even Mastodon 4 only allows a very limited subset of HTML in posts, still excluding embedded images. But at least Hubzilla content is readable on Mastodon.
But this may change. It's no longer only about hobbyist projects like Friendica, Hubzilla or WriteFreely that Mastodon has to headbutt with. It's commercial players such as Flipboard which demand that Mastodon render their Article-type objects as intended. And it looks like Mastodon will cave in some more.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #Flipboard #ActivityPub

/USDT:

ENTRY ZONE- 18850 , 18200

TARGETS - 19100 , 19400 , 19760 , 20050 , 21000 , 23000 , 25000

STOP LOSS - 17200

LEVERAGE - 20x

Vielleicht sollte man so einen Shitstorm einfach mal riskieren. Das wrde nmlich eindrucksvoll beweisen, da erhebliche Teile der sich sonst so tolerant und allem gegenber offen gerierenden Mastodon-Community zutiefst xenophob sind, wenn es um das Fediverse geht. Und es wrde beweisen, da diese Leute inzwischen aktiv zur Bekmpfung von allem im Fediverse, was nicht Mastodon ist, bergegangen sind.
Bonuspunkte, wenn das live whrend eines Vortrags passiert, der dann auch noch gestreamt und/oder vom CCC aufgezeichnet wird.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #Shitstorm Richtig, das war 2017, als erst Hubzilla ActivityPub eingefhrt hat und dann zwei Monate spter Mastodon. Die beiden waren vorher schon ber OStatus verbunden und monatelang die einzigen Projekte berhaupt, die ActivityPub untersttzten. Aber sie taten und tun das immer noch sehr unterschiedlich.
Hubzilla hat sich an die Spec gehalten und brav alles als Article-Type Objects gesendet. Immerhin hat Hubzilla wie sein "Vorgnger" Friendica keine Zeichenlimits und sehr weitreichende Textformatierungsmglichkeiten.
Mastodon hat derweil alles durch einen "HTML-Sanitiser" gejagt, der alles, was reinkam, knallhart auf Reintext reduziert hat. Textformatierung raus, Bilder raus usw. Egal, was es war.
Von Hubzilla-Seite her kamen dann Beschwerden, da Mastodon Hubzilla-Content so gnadenlos entstellt, zumal das bei Article-Type Objects knallhart gegen die Spec geht. Von Mastodon-Seite her kam erst weitere Verweigerung der Kooperation. Mastodon setzte ja knallhart auf reines, puristisches Old-School-Original-Gangsta-Microblogging la Twitter, und da gibt's keine Textformatierung und keine eingebetteten Bilder.
Irgendwann hat Mastodon dann doch "eingelenkt". Die "Lsung" sah dann so aus, da Mastodon Article-Type Objects berhaupt nicht mehr renderte und kurzerhand statt dessen aufs Original verlinkte. Immer. Auch bei Kommentaren, weil Mastodon zwischen Posts und Kommentaren nicht unterscheiden kann. Mastodon-Nutzer muten jetzt bei allem, was von Hubzilla kam, erst den Link klicken, um es im Original zu lesen.
Daraufhin hat Hubzilla umgestellt von Article-Type Objects auf Note-Type Objects, die Mastodon weiterhin entstellte und bis heute weitgehend entstellt. So ganz allmhlich gibt's aber auch von kommerzieller Seite her Druck auf Mastodon, endlich mehr HTML-Rendering fr Article-Type Objects zuzulassen.
Die Hubzilla-Entwickler weigern sich weiterhin beharrlich, Article-Type Objects zu senden, und sei es optional, solange Mastodon sie nicht vernnftig und spezifikationskonform rendert.
Friendica untersttzt ActivityPub erst seit 2019, hat sich aber eine elegante Lsung einfallen lassen: Standardmig gehen Posts mit Titel als Article-Type Objects raus (die Mastodon nur als Links darstellt) und ohne Titel als Note-Type Objects (die Mastodon entstellt). Was einem erst wie ein Bug vorkommt, ist also Absicht mit Kalkl dahinter.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Mastodon #Friendica #Hubzilla

AAVE/USDT:

ENTRY:-332 -325

LEVERAGE: ( 10x-20x )

1 340
2 355
3 370

STOP-LOSS: 315

Make those miles count with a reliable . When on the hunt for a good one, figuring out which class of e-bike you need is a key decision point.

New entry of AI-generated and added to our :

The : 's


Doch, gibt es. Allerdings fallen die naturgem nicht so "einfach" aus wie Bildbeschreibungen. Die sind keine Momentaufnahmen der Audioaufzeichnung, sondern sie beschreiben sie kontinuierlich.
Die einfachste Form ist das Transkript. Das funktioniert allerdings nur bei reinen Wortbeitrgen, z. B. Podcast-Folgen. Da wird das, was in der Audiodatei gesprochen wird, 1:1 schriftlich wiedergegeben. Manchmal gibt's sogar einen Timecode, damit bekannt ist, wann wer was gesagt hat.
Die komplexere Form ist die Audiobeschreibung. Darin wird alles an Klangereignissen, was im Kontext von Relevanz ist, beschrieben. Wenn es gesprochenes Wort gibt, ist es weiterhin 1:1 transkribiert. Auch einen Timecode kann es geben.
Das ist aus zwei Grnden nicht sehr weit verbreitet. Zum einen postet kaum jemand Audioinhalte direkt auf Mastodon. Dafr hat das Fediverse bessere spezialisierte Anwendungen.
Zum anderen ist es schlicht und ergreifend ein gigantischer Aufwand. Vielleicht kann man einen Alt-Text fr ein Bild in ein paar Sekunden schreiben, wenn's nicht auf Details ankommt. An der Audiobeschreibung einer einstndigen Podcastfolge, die ber ein Transkript hinausgeht, kann man schon mal einen Tag sitzen oder lnger, wenn man darber brtet, wie man gewisse Gerusche so beschreibt, da sowohl taub Geborene als auch Menschen, die ihr Gehr verloren haben, damit etwas anfangen knnen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Transkript #Audiobeschreibung I'm kind of missing the option that factuality doesn't matter as long as the alt-text is entertaining. I think not exactly few blind or visually-impaired people think this way.
Anyway, I'll stick with facts. It's hard enough for me to describe images factually and then distill my long descriptions down to a size that fits into alt-text. I don't want to be required to add whimsy, especially not in the alt-text itself where I simply don't have any room for whimsy.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Also, "image description" and "alt-text" is not the same.
An alt-text is or should be an image description. But image descriptions don't always have to go into the alt-text. Very long image descriptions and/or image descriptions that have to contain information not available anywhere else in the context may also remain in plain sight, e.g. in the post text if it's a Fediverse post.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I can tell you what not to use in alt-text.
For one, don't put line breaks into your alt-texts. It doesn't matter whether Mastodon renders them. A lot of things in the Fediverse that aren't Mastodon don't render them.
Besides, don't use the quotation marks on your keyboard. They may irritate certain frontends from rendering them as " to ending the alt-text prematurely because they take the first quotation mark in an alt-text for the end of the alt-text.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #FediTips

MORPHO/USDT

Leverage: 20-75x
Entry Targets:
2.33
2.27
Take-Profit Target :
1)2.5
2)2.8
3)3.2
4)3.8

Stop-Loss 1.90

Ukraine delivered 200k domestically-produced drones to front-line units so far in December

With equipment from partners, more & more Ukrainian-made weapons are already operating on the frontlines

manufactured drones Kyiv close the gap as they face Russian forces with more shells on

also aims to ramp up the production of -range and

Es gibt da eine Gruppe, die sich irgendwie "FediDevs" nennt.
Die haben unter eine Art Portal eingerichtet, wo man sich registrieren und Starter Packs fr Mastodon anlegen kann, so hnlich, wie es sie auch auf Bluesky gibt. Mastodon-Nutzer knnen dann diese Starter Packs nehmen, um mit einem Mausklick rubbeldiekatz dutzendweise Konten zu folgen.
Problem Nr. 1: Auf kann man sich nur registrieren, wenn man auf einer der Instanzen ist, die FediDevs indiziert. Siehe , da ist eine lange Liste aller indizierten Serverinstanzen. Die allerallermeisten Instanzen sind aber Mastodon-Instanzen, und Pleroma, Akkoma, Hubzilla, (streams) und einige andere werden berhaupt nicht indiziert.
Problem Nr. 2: Es ist ganz offensichtlich technisch unmglich, in den Starter Packs irgendwas einzutragen, was kein Mastodon-Konto ist. Guck dir die Starter Packs an. Nur Mastodon-Konten drin.
Noch besseres Indiz: . Das Starter Pack ist komplett leer. Ganz offenkundig hat der Ersteller versucht, einen Starter Pack mit Nicht-Mastodon-Konten und -Kanlen anzulegen, aber daran dann gescheitert, weil es ganz einfach nicht mglich war, in den Starter Pack irgendwas einzutragen, was nicht auf Mastodon ist.
Problem Nr. 3: Die Starter Packs funktionieren selbst auch nur auf Mastodon. Ich kann sie nicht auf Hubzilla nutzen, du kannst sie nicht auf Akkoma nutzen.
Das Ganze ist also grtenteils absolut mastodonzentrisch und inkompatibel zu allem, was nicht Mastodon ist. Mich beschleicht auch das Gefhl, da die paar wenigen Nicht-Mastodon-Instanzen, die FediDevs indiziert, nur durchgerutscht sind, weil sie an den entscheidenden Stellen hinreichend kompatibel zu Mastodon sind.
Aber trotzdem steht FEDIDevs auf der ganzen Sache drauf.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #FediDevs #StarterPacks Well, it is possible to use the Mastodon client API for features that Mastodon itself doesn't have like text formatting. But, for example, many mobile apps don't support text formatting because Mastodon doesn't, although everything that isn't Mastodon does. They're built only against Mastodon.
And there are things, mostly Web services, that either do the same, use the client API, implement only Mastodon features and depend hard on features that only Mastodon has. Or they skip APIs and build directly against Mastodon, again, requiring the presence of features only available on Mastodon in the required way.
Then they have the audacity to have "Fedi" in their names while being completely incompatible with Pleroma, Misskey, Iceshrimp, Friendica, Hubzilla etc., essentially everything that isn't Mastodon or maybe a Mastodon fork.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonAPI #FediverseDevelopment I guess people who only know Mastodon see this differently from people who actively use something in the Fediverse that is not Mastodon.
The difference is:
If you "implement ActivityPub", it will work with, for example, Mastodon and its forks, Pleroma and its forks, Misskey and its forks, GoToSocial, Friendica, Hubzilla and (streams). As long as they have a reasonable ActivityPub implementation itself.
If you "implement Mastodon", it's only guaranteed to work with Mastodon.
It may or may not work with Mastodon forks, Pleroma and its forks, Misskey and its forks, GoToSocial and Friendica. If it doesn't, it never will because the non-Mastodon Fediverse is not officially supported. In fact, the devs may not even know that there's something in the Fediverse that's federated with Mastodon, but that isn't Mastodon.
It will most likely not work with Hubzilla, which is what I use, and (streams). They, too, are federated with Mastodon, by the way.
But this is the way a whole lot of things in or for the Fediverse are developed.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub #FediverseDevelopment Die Starter Packs von FediDevs sind hart ausschlielich gegen Mastodon gebaut. Nicht gegen irgendeine Mastodon-API, sondern direkt gegen Mastodon selbst ohne irgendeine API.
Nicht nur kann man sie nur auf Mastodon nutzen, sondern man kann zu Starter Packs auch nur Mastodon-Konten hinzufgen.
Untersttzung fr Pleroma, Akkoma, Misskey, die Forkeys, Friendica, Hubzilla usw. mte jeweils einzeln Stck fr Stck ins Backend eingebaut werden, weil das Backend von jemandem gebaut wurde, der entweder nicht wute, da das Fediverse mehr ist als nur Mastodon. Das, oder das ganze Backend mte weggeschmissen und neu gebaut werden, und zwar so, da es projektunabhngig funktioniert.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NichtNurMastodon #FediDevs #StarterPacks The Fediverse itself is diverse. And I'm not talking about various Mastodon apps. I'm not talking about Mona vs IceCubes vs Tusky vs Fedilab vs the official Web interface. I'm talking about vastly different server applications: Mastodon vs Iceshrimp vs Hubzilla vs Lemmy vs PeerTube.
The Fediverse is diverse enough for some Mastodon users to actually be disturbed by this diversity. Just look at my profile, look around the entire server instance, and tell me how close it is to Mastodon. Or look at the mention. Mastodon doesn't turn mentions into long names. Or look at the length of this comment. This is not a case of a hacked character limit. This is a case of there never having been any character limit in twelve years.
It's just that many other Mastodon users don't notice it because they're in a bubble that's almost or entirely only Mastodon.
The Mastodon-to-non-Mastodon rate for Fediverse instances is about 1:2. Two out of three Fediverse server instances are not Mastodon.
For monthly active users, it's about 7:3. Around 70% of active Fediverse users are on Mastodon. Admittedly, this is skewed somewhat because there are no stats that count actual users on Hubzilla and (streams) who make use of nomadic identity and/or multiple channels on the same accounts.
But for many Mastodon accounts and entire Mastodon instances, the rate for active Fediverse users known may pretty well be about 100:1. You can take all users from Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon, Mitra, GoToSocial, micro.blog, Socialhome, Friendica, Hubzilla, (streams), Lemmy, /kbin, Mbin, PieFed, Pixelfed, PeerTube, Owncast, Funkwhale etc., you can put them all together, and you can still have a hundred times more Mastodon users.
In fact, I'm quite convinced that there are lots of Mastodon accounts that follow hundreds of other accounts, but they're all only Mastodon accounts which, in turn, only follow Mastodon accounts themselves. Some people have spent all the time from October 30th, 2022 to today quite active on Mastodon, but without noticing anything from outside of Mastodon.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse What are the chances that the ActivityPub side will get full (or any) support for Pleroma and its forks, Misskey and its forks, Friendica and other things that use the Mastodon client API
Or even server applications that can speak ActivityPub, but that don't have the Mastodon client API implemented
I sincerely hope that Surf isn't built against only Mastodon so hard that it's impossible to add more than just incidental and unsupported compatibility with anything that isn't Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse Mastodon did start out as a full-stack Web application AFAIK. It used the OStatus protocol, the same protocol as what GNU social was based on and what StatusNet was using prior to its merger with its own fork, GNU social.
However, at first, it was not positioned as a fully independent project of its own, much less a federated walled garden that allegedly only connected to itself. It was initially conceived and advertised as an alternative to GNU social proper with a different, "easier-to-use", more Twitter-like GUI being its main selling-point.
I guess it's pretty obvious that what was working underneath was not GNU social proper either. Two examples to prove this:
Neither Identi.ca nor StatusNet nor GNU social had a rigid, hard-coded character limit of 500 characters. Mastodon had it from the get-go.
Also, Identi.ca, StatusNet and GNU social had a summary field. It was part of the OpenMicroBlogging and OStatus protocols. Both Friendica and Hubzilla made use of this summary field as such. Mastodon did not have the summary field implemented because summaries were pointless if all you had was 500 characters.
Fast-forward to 2017. Mastodon had meanwhile repositioned itself on the "market" as a stand-alone microblogging platform, implying to be a "decentralised, federated walled garden" with its own exclusive technology that nothing else used, and that nothing else connected to. Something that just about every last Mastodon newbie takes Mastodon for still today.
At some point in 2017, a Mastodon user from the demo scene with some development experience submitted a pull request to Mastodon's GitHub repository which would repurpose this very same summary field as a content warning field. The pull request was accepted and merged. Ever since shortly afterwards, Mastodon users started believing that Mastodon's content warning field was invented by Eugen Rochko from scratch. And they still do.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #StatusNet #OStatus #Mastodon #Friendica #Hubzilla #FediverseHistory

VET/USDT

Entry price : - 0.05450 - 0.05300

Target 1: 0.055
Target 2: 0.057
Target 3: 0.060

Stop loss : 0.051

Leverage: 10x

Allocate only 1-3% of our deposit for each trade

BTC/USDT:

ENTRY:-104000 -103000

LEVERAGE: ( 10x-20x )

1 105000
2 106000

STOP-LOSS: 102600

This is also why I find the western Misskey forks' desire to pander to mobile users by trying to function with existing Mastodon Clients so counterproductive - the Mastodon Clients often just don't care. They really only are for Mastodon and everything else is "good luck have fun".

Or rather, "Wait, you exist!"
And IIRC, Misskey has its own client API. Aria seems to be the shooting star mobile app for the *keys.
Frontless servers to me are a bad idea, as things stand - despite the appeal in speeding up initial development.

In this regard, Pleroma and Akkoma are the best of both worlds. Headless server, own client API, respective official frontend has its own repository, but you may install third-party frontends instead. And Mangane is actually (also) built against the *omas. "Akkomane" is a thing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #AriaApp #Pleroma #PleromaFE #Akkoma #AkkomaFE #Mangane #Akkomane That, of course, sounds like trouble. No frontend offers you the full functionality with no problems. But still, it's obvious that Hollo is developed for a Mastodon-dominated Fediverse with a side of *key and little regard for anything else. I wouldn't be surprised if the Hollo dev, like at least three quarters of the Fediverse, had never even heard of Hubzilla.
Hubzilla is a special case in many ways. It wasn't built into a Mastodon-dominated Fediverse because it was initially created some four years before Mastodon. Also, it doesn't have replacing Twitter as any of its goals. You can use it for microblogging, yes, but then, you can use it for almost anything. Even runs on Hubzilla.
Granted, Friendica is even older. After all, Friendica's own creator started Hubzilla as a Friendica fork. But Friendica's new developers decided for Friendica to approach Mastodon in some ways. In Hubzilla's case, in stark contrast, it's an explicit design and development decision not to do that. Part of Hubzilla's philosophy is to remain independent from the rest of the Fediverse.
Hubzilla is also one of the few Fediverse projects whose ActivityPub implementation is not designed for maximum Mastodon compatibility. That's partly because Hubzilla is the only Fediverse project that had ActivityPub before Mastodon. And Mastodon's adoption of ActivityPub caused quite some head-butting between Mike Macgirvin and Eugen Rochko.
That's only some of the reasons why the Mastodon API would never work for Hubzilla, and Hubzilla will always require its own tailor-made frontends.
Beyond that, there are those many, many things neither covered by the Mastodon API nor by any Mastodon-compatible app. And I'm not just talking about CMS or groupware features like , cards, , webpages or . (That is, Hubzilla's CalDAV calendars are edited the best with external apps, but via CalDAV and not via the Mastodon API.)
It actually starts at Hubzilla's handling of identities. Your identity is not tied to your account. Your login is not your identity. . And thanks to , you can have the same channel, the same identity, on multiple server instances with different accounts and logins.
An app based on Mastodon and its API would only let you access your default channel at best. At worst, it won't let you access anything because it expects your identity and all your stuff directly on your account, and it's completely unaware of the existence of channels. This is already a feature that's essential for using Hubzilla, but that absolutely requires a UI tailor-made for Hubzilla.
Then there is the distinction between posts and comments. Hubzilla does not mimic Twitter. It's closer to Facebook and blogs.
For one, Hubzilla doesn't display content bit by bit like Mastodon does, at least not by default. It's actually an option that nobody ever uses which may be why it's no longer available on (streams). Instead, it always displays conversations as a whole, just like Facebook, just like blogs, just like forms. Post on top with a title, comments below in chronological order. Always. Even when a new comment comes in, or someone has liked or repeated a comment, when you go and look at what happened, you get the whole thread.
Speaking of which, on Hubzilla, you don't usually do as you'd do on or Mastodon and scroll through your feed/timeline until either you hit stuff that you've already read, or you want no more. Instead, Hubzilla, like everything that Mike Macgirvin has made, has a counter for unnoticed actions. If you open it, you get a list of these actions that you haven't paid attention to yet. Click one, and you're taken to the thread where it happened (and only that thread is shown to you), and everything that was unread in this thread is flagged read.
In addition, has only one editor for everything, posts, comments (which are posts), DMs. So does Mastodon. So do all Twitter/ alternatives in the Fediverse.
But Facebook doesn't. It has a separate entry area for comments. So do blogs. And so forth. And so does Hubzilla. It has , and it has right at the bottom of each thread. It's geared towards having these two separate editors. Even using Friendica, which does have the Mastodon client API implemented, with a one-editor app has to be hackish.
All this continues with text formatting. Unlike the *keys and some Mastodon forks, Hubzilla doesn't use Markdown. It uses . This goes all the way to integration of OpenWebAuth magic single sign-on and .
Generally, image handling, including alt-text. On Mastodon and its forks, you attach your images to your posts as files, and then you get one dedicated entry field for alt-text for each image.
On Hubzilla, you first go to your and use it to upload the images you want to add to your post to the WebDAV-enabled file space built into your channel. You have to pay attention to setting the permissions both for the image files and for the subfolder correctly. Then you go to your post editor (not the comment editor which doesn't officially support inserting images) and select the image you want to embed. And then . (Notice how I've linked to a Hubzilla support forum instead of the WIP help rewrite because there still is no official documentation on how to add alt-text on Hubzilla.)
Any UI elements geared towards the Mastodon way of adding images to posts are useless on Hubzilla, and nothing on a UI for Mastodon can be used to add images to posts the Hubzilla way. Again, you need a Hubzilla-specific UI for this.
By default, and I guess it's actually recommended, posts and comments are composed in raw BBcode rather than WYSIWYG. The lack of a preview button in your average Mastodon app is actually a lesser issue, although it still is an issue.
Next, posting permissions. Mastodon has "Public", "Unlisted", "Followers only" and "Private". All apps are geared towards this.
Hubzilla, in contrast, has the . It offers you to post in public, to post only to yourself, to post to one of your (think Mastodon lists on piles of coke and 'roids), or to post to any individual custom selection of connections of yours. There's no "Followers only", there's no "Unlisted", and there's stuff that's completely unthinkable from a Mastodon POV.
Oh, and if you run your Hubzilla channel on bone-stock standard default settings, you post to a privacy group named "Friends" unless you explicitly choose otherwise. But you have to be able to choose otherwise in order not to only post to that privacy group. An app made for Mastodon won't give you the UI elements to do so.
In fact, an app geared towards the Twitter-style dichotomy of followers on the one side and followed on the other side will clash with Hubzilla because of just this. Again, Hubzilla is not like Twitter. It's like Facebook. It doesn't have one-sided following connections. It only has like Facebook friends.
This means that , but with a UI made for Mastodon, is next to impossible at worst and very, very limited and much less than optimal at best.
For example, let's suppose someone wants to connect to me. On Mastodon, I'd just simply confirm their follow request if I've chosen to do so. Then I may decide whether or not I follow them back.
Here on my Hubzilla channel, a connection request takes me to the . There I choose a for the new connection that defines which permissions that contact shall have. I add the connection to one or multiple privacy groups, of which I have a lot. I adjust the affinity slider. I may also assign to that connection. I may add lines to one of the two filter lists which I have per connection. Finally, I usually hide the new connection. And then I confirm it which not only grants the permissions in the contact role to the contact, but also establishes a bidirectional connection. It's like automatically following everyone back on Mastodon.
Apart maybe from the confirmation button, not even a single one of these features is available on any of the Twitter replacements in the Fediverse, and thus, not in any of the apps geared towards these either. If I were able to use Hubzilla with a Mastodon app, I'd still have to fire up a browser or a Web app or wait until I'm back home to confirm connection requests.
All this only covers your daily operation. I haven't even talked about yet, including the which defines the basics of Hubzilla's extensive permissions system.
There's exactly one app that works with Hubzilla. It's called , it's only available on F-Droid, it hasn't been updated in over five years, and it's actually a Web app that works like a specialised browser and embeds Hubzilla's Web UI.
A fully dedicated mobile app for Hubzilla that entirely relies on a native mobile UI would be so complex even for normal operation (disregarding the CMS bits) that it'd be more complex than K-9 Mail. If you want to go all the way, including (which controls Hubzilla's optional features, and which of these are available to you can differ from hub to hub) and CMS features and such, it'd be even more complex.
The only realistic way to have different frontends for Hubzilla would be the built-in theming feature. It doesn't mean different colours and button styles. A theme on Hubzilla can be an entirely different UI, but one that you can individually choose for each one of your channels. It's like being on Akkoma and being able to switch between Akkoma-FE, Phanpy and Mangane on your account at any given time.
That is, currently, Hubzilla has only got one built-in theme. It has become , and it even as a dark mode which is every bit as configurable as the light mode. More themes are being worked on in the community right now, but I wouldn't count on them coming with all stock Hubzilla installs, much less automatically added to all existing hubs.
So if you want an alternative UI for Hubzilla, you don't install it next to your hub, just like you install Phanpy next to Hollo or GoToSocial. You install it into your hub instead.
And the best way of developing alternative UIs for Hubzilla is not as fully separate external applications that try to latch onto Hubzilla from outside. It rather is as .
Hubzilla is modular and extendable with third-party repositories.
Lastly, both desktop and mobile use can profit from it because the best way to use Hubzilla on a phone is as a Progressive Web App.
, maybe this is interesting for you as well.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla It depends. Not everything works well frontless because not everything works well with a frontend made for Mastodon.
Hubzilla, for example, has a UI that's largely stuck in 2012. Also, it doesn't have the Mastodon client API implemented. But a frontend designed for Mastodon couldn't even cover 5% of Hubzilla's features. It would not grant access to features that are actually critical for operating a Hubzilla channel such as any parts of the permissions system.
And that's actually one of the reasons why Hubzilla doesn't have the Mastodon client API implemented: The only UI that can sufficiently harness Hubzilla's power is Hubzilla's own native Web UI.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonAPI #Hubzilla
so that those who need alt-text have as much information as possible.

Well, depending on where in the Fediverse you are, a whole lot can be possible.
I tend to make a whole lot of use of my possibilities. Hubzilla, where I am, doesn't have any character limits, at least none worth worrying about.
Sure, depending on your contacts, it makes sense to limit your alt-texts to no more than 1,500 characters because Mastodon, Misskey and their forks chop them off at this length if they're longer. Even Hubzilla itself can no longer fully display alt-texts of over a few thousand characters because they can't be scrolled. And alt-texts of such length are very uncomfortable for screen reader users because screen readers can't navigate alt-text.
But at least for my original images, I also give long image descriptions in the posts themselves in addition to the ones in the alt-texts. And with "long", I mean not "essay", but "short story". "Excessive" if you want.
My personal limit there is 100,000 characters for the whole post. As far as I know, Mastodon rejects longer posts than that entirely, and other Fediverse server apps have even lower limits, so describing my images actually becomes increasingly pointless. But 100,000 characters of description would take me three or four days to research for and write anyway.
Still, while my image posts remain within that limit, I regularly describe and explain my original images in tens of thousands of characters each. I see it as justified, given the very obscure but potentially curiosity-inducing topic. But others may say my long descriptions are way overkill, hardly anyone even reads them because it may pretty well take one hour to do so, and literally nobody actually needs them.
That's why I'm constantly wondering if I'm going overboard with details in my descriptions. Hence the question at the end of my first comment.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

XRP/USDT

Entry price : - 2.48 - 2.43

Target 1: 2.55
Target 2: 2.62
Target 3: 2.70

Stop loss : 2.39

Leverage: 10x

Allocate only 1-3% of our deposit for each trade

Truth be told, as cool as Sharkey is with its load of features, its devs have a track record of bad decisions. Cuddling up with Mastodon and bringing Sharkey closer to it isn't even the worst one. Ask ().
Maybe Iceshrimp is worth a look, too, for those used to Twitter. Of course, people who want to leave or have left something entirely different should be taken to something entirely different like Lemmy, Mbin or PieFed for Redditors and Friendica, Hubzilla and (streams) for Faceboook users.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Sharkey #Iceshrimp #Lemmy #Mbin #PieFed #Friendica #Hubzilla #Streams #(streams) Judging by the advice I've read so far, it's always best to describe the colour using basic colours plus attributes such as brightness, saturation and what other basic colour or colours the colour you describe is leaning towards.
For example, "light, yellowish orange", "a darker, slightly less saturated, slightly more brownish tone of orange", "various shades of slightly yellowish, medium-light-to-medium brown", "a solid, slightly pale medium blue with a minimal hint of green", "a medium-dark wood texture, slightly reddish, slightly greyish". All actually used by me in the long descriptions in (content warning: eye contact) .
If the name of the colour plays a role, use it and then describe the colour in the same way as above. Blind or visually-impaired people may not know what Prussian blue or Burgundy red looks like.
What do you say, is that appropriate, complete overkill or still insufficient
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaTo my surprise, indexes instances of more Fediverse server apps than I thought.
What I've found so far, other than hundreds upon hundreds of Mastodon instances:

One could suppose that all these server applications have taken active steps to become more compatible with Mastodon, but I've got my doubts that standard support for any Mastodon API is sufficient, and that they all have gone beyond API support.
Some things that I've yet to see on the list for the first time:

Still, their not only only seem to work on Mastodon, but it seems to be only possible to add Mastodon accounts and nothing else. It says a lot that is completely empty.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Pixelfed #Firefish #Sharkey #Catodon #GoToSocial #micro.blog #Friendica #Mitra #Misskey #Iceshrimp #Iceshrimp.NET #Pleroma #Akkoma #Hubzilla #Streams #(streams) #Forte #Threadiverse #Lemmy #Mbin #PieFed #FediDevs
we would just move on and let the forks pick up where he'd left off.

You don't even need Mastodon forks to stay in the Fediverse.
There's enough stuff in the Fediverse that can do the same things as Mastodon, that's fully connected to and federated with Mastodon, but that isn't Mastodon, that has never been Mastodon, that isn't affliliated with Mastodon, and that outshines Mastodon as well as its forks in many ways.
(Sent from .)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse

BB/USDT

Leverage: 20-75x
Entry Targets:
0.5220
0.5000
Take-Profit Target :
1)0.540
2)0.550
3)0.580
4)0.620

Stop-Loss 0.480


Last updated: 2024-12-26






Best Heritage Trail in North Narrabeen