I hope thats one of those clocks that bends as it passes your second hole. One of the best feelings ever.
Les pcheries de Pornic.
Fisheries from Pornic - France
-exposure I've basically moved my alt to the Wolf Territories myself. I've actually followed my home and my two shops because they're all on Nautilus sims, and Chad Deischer has relocated the whole Nautilus archipelago to the Wolf Territories several weeks ago, my furnished home, the stuff in my shops and all. So I had to follow suit to reclaim my home and my shops.
I just hope the Wolf Territories will find a way to have that nasty bug with creating folders and outfits fixed, then it'll be much more fun.
As for OSgrid, I'm not sure what to do with the avatar I have there. Maybe keep him as another spare. I'm not even sure if I'll find him a new home. But I won't delete him, seeing as he's the creator of a few items.
My main remains in Dorenas World.
#
Long #
LongPost #
CWLong #
CWLongPost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
OSgrid #
WolfTerritories #
WolfTerritoriesGrid #
WTGrid #
WolfGrid #
DorenasWorld i just figure, hey, sometimes i like to sit there and pick out every detail in a pic for a few minutes, maybe someone using a screen reader would too
Well, as long it's only a few minutes...
For comparison: I've spent two full days, morning to evening, describing the image in in a bit over 1,400 characters of short description in the alt-text and over 60,000 characters of long description (+ explanations + verbatim transcripts of all pieces of text within the borders of the image) in the post itself.
I've figured that . And it's a rule that all text within an image must be transcribed verbatim, but it's a rule that doesn't explicitly cover or exclude unreadable text. I'm just playing by rules.
The reason why I always have two descriptions, one in the post, one in the alt-text, is because every image in the Fediverse must have an alt-text that actually describes the image accurately and at a certain minimum level of detail. Again, I'm just playing by the rules. But at the same time, I can't fit my full descriptions into the 1,500 characters that Mastodon, Misskey and their forks let through.
Anyway, don't worry about peanuts.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta Die Hashtags mssen sein. Zum Teil sind sie zum Filtern bzw. zum automatischen Generieren leserseitiger CWs, was auf Mastodon seit Oktober 2022 und auf () seit 2012 mglich ist.
- #Long
#LongPost: fr diejenigen Mastodon-Nutzer, die sich an Posts mit ber 500 Zeichen stren. Wenn sie dieses Hashtag filtern, sehen sie meine berlangen Posts und Kommentare (ber 500 Zeichen) nicht mehr. - #CWLong
#CWLongPost: dasselbe, aber von vornherein als Content Warning ersichtlich gemacht. Entspricht: "CW: long post (almost 4,000 characters)". - #LangerPost: wie #LongPost, aber fr deutsche Nutzer, die des Englischen nicht mglich sind, damit sie verstehen, was die Hashtags sollen.
- #CWLangerPost: wie #CWLongPost, aber fr deutsche Nutzer, die des Englischen nicht mglich sind, damit sie verstehen, was die Hashtags sollen. Gleichbedeutend mit "CW: langer Post (fast 4.000 Zeichen)".
- #FediMeta
#FediverseMeta: fr Leute, die sich daran stren, wenn jemand ber das Fediverse postet. Wenn sie eines oder beide dieser Hashtags filtern, sehen sie meine Fediverse-Posts und -Kommentare nicht mehr. - #CWFediMeta
#CWFediverseMeta: dasselbe, aber von vornherein als Content Warning ersichtlich gemacht. Entspricht: "CW: Fediverse meta".
Die volle Content Warning im Mastodon-Stil fr diesen Kommentar wrde lauten: "CW: langer Post (fast 4.000 Zeichen), Fediverse-Meta, Fediverse-ber-Mastodon-hinaus-Meta".
Ich wrde so eine Content Warning auch ber diesen Kommentar setzen. Das ist hier aber technisch nicht mglich.
Zum einen: Das CW-Feld ist nicht fr Mastodon ganz neu erfunden worden. Statt dessen hat Mastodon 2017 das Zusammenfassungsfeld, das StatusNet schon 2008 eingefhrt hat, als CW-Feld zweckentfremdet. Denn fr maximal 500 Zeichen braucht man keine Zusammenfassungen.
Hier auf Hubzilla ist es aber immer noch ein Zusammenfassungsfeld. Hubzilla ist 2012 entstanden, und zwar als Fork von Friendica von 2010 von Friendicas eigenem Erfinder. Auch auf Friendica ist es ein Zusammenfassungsfeld. Das war alles noch lange vor Mastodon.
Warum Hubzilla sich Mastodon nicht angepat und das Zusammenfassungsfeld in ein CW-Feld umgewandelt hat Erstens, weil Hubzilla nicht jeden Mist von Mastodon mitmacht.
Zweitens, weil Hubzilla kein Zeichenlimit hat. Oder wenn doch, drfte es in den Millionen liegen. Da ergibt ein Zusammenfassungsfeld Sinn.
Drittens, weil Inhaltswarnungen auf Hubzilla vollautomatisch leserseitig fr jeden Leser individuell generiert werden. Jeder Hubzilla-Veteran wird dir Stein und Bein schwren, da das tausendmal besser ist als Mastodons posterseitige CWs, die jedem gleichermaen aufgezwungen werden.
So, und warum kann ich
hier keine Mastodon-CW einsetzen
Hier kommt der nchste groe Unterschied zwischen Mastodon und Hubzilla: Im Gegensatz zu Mastodon hat Hubzilla in sich geschlossene Konversationen. Genau wie ein Blog, genau wie Facebook, genau wie Tumblr usw. Noch einmal: Hubzilla ist ein Fork von Friendica, das 2010 als Facebook-Alternative an den Start ging, die auch als Blogging-Engine taugen sollte.
Aus Hubzilla-Sicht hat ein Thread genau einen Post, den Startpost. Antworten sind hier auf Hubzilla keine Posts. Es sind Kommentare. Wie Facebook-Kommentare. Wie Blog-Kommentare.
Mastodon hat auch eine Eingabemaske fr alles. Hubzilla hat eine fr Posts und Privatnachrichten. Und eine separate fr Kommentare fr jeden separaten Thread. Und die Eingabemasken fr Kommentare sind speziell auf das ausgelegt, was Kommentare brauchen. Genau wie auf Facebook. Genau wie auf Blogs.
Und welchen Sinn wrde ein Zusammenfassungsfeld fr Kommentare ergeben Wo gibt es das Hat Facebook das Welches Blog hat das
Und genau deshalb gibt's das auch auf Hubzilla nicht.
Last but not least: Wenn es anders ist als Mastodon, ist es weder kaputt noch falsch. Mastodon ist nicht der Standard, an den sich alles zu halten hat.
#
Fediverse #
Mastodon #
Hubzilla Machen Mastodon-Nutzer doch auch oft genug nicht, wenn sie ber Mastodon schreiben.
Und genau darauf spielt an: auf die Mastodon-Normativitt, die gerade unter Mastodon-Nutzern weit verbreitet ist. Mastodon ist der "Standard", und standardmig ist alles Mastodon, auer es wird explizit dazugesagt, da es nicht Mastodon ist. Aber wenn es nicht Mastodon ist, dann
mu das dazugesagt werden.
Es ist ja auch vllig normal fr Mastodon-Nutzer, "Mastodon" zu sagen, wenn man das ganze Fediverse meint, oder "Fediverse" zu sagen, wenn man nur die Serversoftware Mastodon meint. Und auf gar keinen Fall darf man sie dafr kritisieren. Wenn man selbst nicht auf Mastodon ist, schon mal erst recht nicht, weil man dann maximal ein Fediverse-Nutzer zweiter Klasse ist.
Das erklrt (mit), warum Crossgolf sich so verhlt, wie er es tut. Z. B. seine Posts den Leuten im "FoundKey-Netzwerk" zu widmen und nicht etwa im Fediverse.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
NichtNurMastodon #
MastodonZentrizitt #
MastodonNormativitt Add your location to a Google Map Nia Long
Heart of Fire by Elizabeth Gadd
is offline again. Not for a few hours or so like just about everyday for quite a while now. This time, .
The asset server is in such a bad state now that each crash and restart caused more assets to break. Yesterday, OSgrid reached a state in which it was no longer even possible to save inventories as IARs as they all ended up corrupt. So instead of closing the grid on March 21st to , they had to pull the plug immediately.
One could say this means that lots of OSgrid users who wanted to wait until the last moment to save their stuff have lost lots of content. I say they've probably lost it already before the grid closure because chances are it was already broken at that point.
Seriously, the last time I've logged my OSgrid alt in, and that was last week, almost none of his attachments worked. No body. No hair. No glasses. Etc. I had to unpack replacements for some of the items from boxes which happened to still be intact, but for adjusted or modified items, I had to send in another "me" to deliver replacements right into OSgrid.
Now the OSgrid staff say they want to "completely rebuild the assets in a new format". At first glance, this reads like they no longer want to wipe the asset server and fix the assets themselves instead. But seriously, they've tried that for years. To less than no avail as we can see now. More assets are geb0rkt than not.
I myself rather think they've already started wiping it, and they simply want to change the way the assets are stored. And that's although OSgrid has switched to Avination-coined
fsasset after the RAID failure in 2014 and the eight-month data rescue timeout until 2015. But that was almost a decade ago, and you can only change so much on an asset server in a running grid with assets on it.
Basically, instead of just resetting the asset server, they're going to tear it down and rebuild it. After all, they're still hoping for most residents (those who were active recently anyway) to return and bring their stuff back (what parts of it aren't broken anyway).
Most other grids would have called it quits at this point. And seriously, OSgrid was the first public OpenSim grid, it's the oldest grid (launched in 2007), and it's one of only two remaining grids from the 2000s (the other one is AnSky from 2008). It's probably a question of honour for OSgrid to carry on against all odds.
On a more positive note on decentralised stuff, seems to work again.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
OSgridCrossroad
Starting a new "mini-" series if you will here. This one was done in February 12th, as I had a night walk to the nearby traffic light (carrying my tripod and camera), planning to do some long exposures. Generally speaking, the results weren't up to my expectations, but I managed to salvage some shots.
For this shoot, I've used Voigtlnder 20mm, coupled with a variable ND filter (yes, ND, at night, for long exposure), and "Starry Night" filter from Kenko. This filter is supposedly used to reduce the light pollution, and seems awkward to use it in such situations, but I just wanted to try, since I've never used this one before even though I got it months ago. This filter also has a bluish tint, and I had to set the white balance properly (using WB correction tool) and despite all of that, processing the images in terms of colors was a bit of a task, especially in terms of the color halos (or bleeding), which eventually, I had to make peace with! The exposure for this one was about 7 minutes. What's strange though, cars didn't pass by much when I shoot such long exposures, but only after I finish them!
New COVID study, of dozens of countries, from before COVID to now, shows life expectancies dropped and have not recovered.
I you for the to incentivize form content on the network. One I have is... how is that Are we comparing the total count of the post to the total character count of the hashtags Are we counting how many words are normal and how many are
Today is one of those days on which simply too much happens in the Hypergrid at the same time.
There's in ZetaWorlds which starts in a bit over an hour and a half.
There's the in the Wolf Territories.
There's an unlisted St. David's Day Dance on the Welsh sim in Speculoos Grid.
Not to mention a whole lot of more or less regular events.
Maybe we'll do some event hopping today.
#
Long #
LongPost #
CWLong #
CWLongPost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
Hypergrid #
VirtualEvent #
ZetaWorlds #
WolfTerritories #
WolfTerritoriesGrid #
WolfGrid #
WTGrid #
Speculoos #
OpenSimWorldsFair #
StDavidsDay #
DyddGwylDewiHapus #
ZeroDiscriminationDayToday is one of those days on which simply too much happens in the Hypergrid at the same time.
There's in ZetaWorlds which starts in a bit over an hour and a half.
There's the in the Wolf Territories.
There's an unlisted St. David's Day Dance on the Welsh sim in Speculoos Grid.
Not to mention a whole lot of more or less regular events.
Maybe we'll do some event hopping today.
#
Long #
LongPost #
CWLong #
CWLongPost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
Hypergrid #
VirtualEvent #
ZetaWorlds #
WolfTerritories #
WolfTerritoriesGrid #
WolfGrid #
WTGrid #
Speculoos #
OpenSimWorldsFair #
StDavidsDay #
DyddGwylDewiHapus #
ZeroDiscriminationDay Wie schn, dass ihr streiten und trotzdem hinterher Bier trinken knnt und verschiedene Sichtweisen nebeneinander existieren drfen.
Das tun wir ja nicht mit denselben Leuten.
"Bier trinken" tun wir mit Leuten, die offen fr das ganze Fediverse sind, wie und , die ja selbst nicht nur auf Mastodon sind, sondern unter
Doris und
Steffen auch auf Hubzilla. Und Hubzilla ist technologisch wie auch kulturell das diametrale Gegenteil von Mastodon.
"Streiten" tun wir mit denen, die darauf beharren, da das Fediverse nur Mastodon ist. Da Mastodon ein in sich geschlossenes Netzwerk ist und alle, die das bestreiten, in aller ffentlichkeiti als ahnungslose Idioten beschimpfen (was so tatschlich mit einem Tech-Journalisten passiert ist).
Mit Leuten, die Mastodon als Goldstandard im ganzen Fediverse ansehen und alles, was von Mastodon abweicht, als entweder kaputt oder konzeptionell falsch.
Mit Leuten, die mit aller Gewalt Mastodons Kultur (die erst Mitte 2022 von frischen Twitter-Flchtlingen auf Basis von Mastodon 3.x definiert wurde) im ganzen Fediverse durchdrcken wollen und damit andere Serveranwendungen ihrer eigenen, eigens auf sie zugeschnittenen und oftmals sogar lteren Kultur berauben wollen. Damit geht dann einher, da sie Nicht-Mastodon-Nutzern verbieten wollen, Features der von ihnen genutzten Software zu nutzen, nur weil Mastodon sie (standardmig) nicht hat.
Siehe wieder (Calckey, einige tausend Zeichen zur Verfgung), den ein Mastodon-Nutzer angeschnauzt hat, er soll geflligst entweder lange Posts (alles ber 500 Zeichen) in Schnipsel von maximal 500 Zeichen zerschneiden oder sich aus dem Fediverse verpissen. Doch, das ist ganz genau so passiert.
Man stt ja schon auf vehemente Widerstnde, wenn Leute, die nur Mastodon kennen und das ganze Fediverse nur durch die Mastodon-Brille sehen, der felsenfesten Ansicht sind, sie htten einen absolut objektiven und ungetrbten Blick auf das Fediverse. Die allermeisten Mastodon-Nutzer beharren darauf, da Nicht-Mastodon-Nutzer im Fediverse nicht diskriminiert oder ausgegrenzt werden, whrend sie selbst fleiig Nicht-Mastodon-Nutzer diskriminieren. Es ist fr sie ganz einfach komplett unvorstellbar, da das Fediverse fr jemanden, der z. B. Anfang, Mitte der 2010er nach Friendica kam, irgendwie anders aussieht als fr jemanden, der irgendwann von 2022 bis 2024 nach Mastodon kam und nur Mastodon kennt.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon #
MastodonKultur #
MastodonNormativittFrom 24 Feb: COVID shots protect kids from long COVIDand dont cause sudden death - Researchers recommend kids stay up to date on the COVID v... -19 -covid -cardiac-arrest -cardiac-death
There are also the "descendants" of Friendica, created as forks by Friendica's own creator over more than a dozen years now, which have even more advanced permissions systems.
One is , a fork of Friendica from 2012. The other one is called by the community, and it's a fork of a fork of three forks of a fork (of a fork) of Hubzilla from 2021.
I've made that compare Mastodon, Friendica, Hubzilla and (streams) in a number of categories.
Hubzilla and (streams) give you the following possible target audiences for new posts:
- everyone on the Internet (Hubzilla, (streams))
- all your connections ((streams) only on Hubzilla, you can emulate this with a privacy group containing all your connections)
- only the members of one particular privacy group (Hubzilla)/access list ((streams)) (think "Mastodon's lists on coke and 'roids")
- only those to whom you've assigned a specific custom profile of your channel (Hubzilla like Friendica, it actually allows you to have multiple profiles and show them to specific connections so that they see different sides of you)
- only one specific group/forum (Hubzilla, (streams))
- only an impromptu selection of connections of yours (Hubzilla, (streams))
- only you yourself (Hubzilla, (streams))
The permissions systems of Hubzilla and (streams) are compatible to one another, i.e. one understands the permissions defined by the other. I'm not sure how well they and Friendica play with each other, though.
As for Mastodon: Any post that isn't public is understood by Mastodon as a DM and treated as such. Your contacts can't boost it, for example. The downside is that this kills any chances of meaningful discussions for Mastodon users.
So Hubzilla and (streams) have this advanced permissions system, and they understand threaded conversations and treat each one of these as an enclosed object with exactly one post and any number of comments. A thread always has and enforces consistent permissions all over, including all comments.
If you're on Hubzilla, and you send a post to Alice on Hubzilla and Bob on (streams), not only do both see your post, but both also automatically receive each other's comments, and they can comment on each other's comments.
Mastodon understands your post with restricted permissions as a DM. But Mastodon DMs only ever happen between two actors. This means: If Alice and Bob are on Mastodon, then both receive your post as a DM, but neither receives any comment from the other, and they can't comment on each other's comments either.
Also, fair warning ahead:
Neither of them is "Mastodon with some extra features". They're all
very different from Mastodon. They all have steeper learning curves than Mastodon. Friendica's learning curve is significantly steeper than Mastodon's. (streams)' learning curve is quite another bit steeper than Friendica's because the permissions system is not optional, and not everything is public by default. Hubzilla has an even steeper learning curve.
Also, none of the three has a full set of dedicated native mobile apps. For Friendica, there are basically only Android apps. In the Apple App Store, there's nothing. Friendica can also be used with some Mastodon apps, but they only cover maybe 20% of Friendica's features, namely those that Mastodon has, too, so you'll be very, very limited. In fact, they do not cover any permission settings.
For Hubzilla and (streams), there are no phone apps at all. They don't support Mastodon apps either, and they never will. It simply wouldn't make sense because a Mastodon app would not cover important key features.
So if you're on an iPhone or iPad, or if you want to try Hubzilla or (streams), your only option is the Web interface, either in a browser or as a Progressive Web App. At least, all three have Web interfaces that adapt to mobile devices.
Lastly, you won't find (streams) on FediDB or Fediverse Observer. It's intentionally kept away from there, and it intentionally does not submit any stats. There are currently only two public, open-registration instances anyway, , with a German admin who also speaks English.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Friendica #
Hubzilla #
Streams #
(streams) #
Facebook #
FacebookAlternative Typischerweise versuchen Mastodon-Nutzer entweder, jemanden out-of-the-blue zu erwhnen, oder, jemandem out-of-the-blue eine DM zu schicken.
Und genau das geht beides nicht mit Friendica-Nutzern. Wenn du sie einfach so erwhnst, dann merken sie das in aller Regel nicht. Und eine DM kann man nur schicken an volle Verbindungen. Also:
- folgen.
- Warten, bis das Konto einem zurckfolgt.
- Zurckfolgen zulassen. Damit stellt Friendica die standardmige bidirektionale Verbindung her.
- Dann erst eine DM schicken.
Alternative: sich gleich an eine der Gruppen wenden, also entweder oder .
Das geht dann von Mastodon aus so:
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FriendicaLiving a and life
A harmonious balance of physical, mental and emotional health
1. good habits
2. balanced lifestyle
3. positive mindset
4. nutritious diet rich in fruits, vegetables, whole grains, and lean proteins
5. regular exercise
6. staying curious
7. continuous learning
8. maintaining a sense of purpose
Es gibt auch noch , aber von der Community genannt wird.
Das ist ein Fork eines Forks dreier Forks eines Forks (eines Forks) von Hubzilla, aber vom Erfinder von Friendica und Hubzilla. Es ist moderner und praktischer in der Handhabung als Hubzilla und liegt von der Lernkurve her zwischen Friendica und Hubzilla.
Was dabei aber zu bedenken wre:
- Es gibt dafr ebensowenig Smartphone-Apps wie fr Hubzilla. Und es gibt ebensowenig Untersttzung fr Mastodon-Apps, weil das ebensowenig sinnvoll wre bei etwas, was so fundamental anders ist als Mastodon. Also Browser oder Progressive Web App.
- An Verbindungsmglichkeiten gibt's nur das hauseigene Nomad-Protokoll, das auch Hubzilla einschliet, und ActivityPub. Also nix diaspora*, nix RSS/Atom-Feeds abonnieren usw.
- Es gibt in ganz Europa nur eine einzige Instanz mit offener Registrierung: . Serverstandort ist Ungarn, aber der Admin ist ein ausgewanderter Deutscher, Der Pepe (nomd) (alias Der Pepe (Hubzilla) ), ein Hubzilla-Veteran, der auch Pepes Hubzilla-Sprechstunde und PepeCyBs Welt betreibt.
- Mit Dokumentation ist es auch noch nicht weit her. Pepe will noch eine schreiben, so, wie er die Hubzilla-Dokumentation auf Deutsch und Englisch komplett neu geschrieben hat.
- hnlicher wie Facebook als Friendica mit dem Bookface-Theme ist es auch nicht.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FacebookAlternative #
Streams #
(streams)Join Superhot or Ultrahot tier now and get this illustration as a bonus reward at the end of this month! For more information about Sacred Gifts, visit section. Thank you!
-
I don't know what constitutes a "good" example in your opinion, but I've got two examples of how bad AI is at describing images with extremely obscure niche content, much less explaining them.
In both cases, I had the describe one of my images, always a rendering from within a 3-D virtual world. And then I compared it with a description of the same image of my own.
That said, I didn't compare the AI description with my short description in the alt-text. I went all the way and compared it with my long description in the post, tens of thousands of characters long, which includes extensive explanations of things that the average viewer is unlikely to be familiar with. This is what I consider the benchmark.
Also, I fed the image at the resolution at which I posted it, 800x533 pixels, to the AI. But I myself didn't describe the image by looking at the image. I described it by looking around in-world. If an AI can't zoom in indefinitely and look around obstacles, and it can't, it's actually a disadvantage on the side of the AI and not an unfair advantage on my side.
So without further ado,
exhibit A: contains
- an image with an alt-text that I've written myself (1,064 characters, including only 382 characters of description and 681 characters of explanation where the long description can be found),
- the image description that I had LLaVA generate for me (558 characters)
- my own long and detailed description (25,271 characters)
The immediate follow-up comment dissects and reviews LLaVA's description and reveals where LLaVA was too vague, where LLaVA was outright wrong and what LLaVA didn't mention although it should have.
If you've got some more time,
exhibit B:Technically, all this is in one thread. But for your convenience, I'll link to the individual messages.
with
- an image with precisely 1,500 characters of alt-text, including 1,402 characters of visual description and 997 characters mentioning the long description in the post, all written by myself
- my own long and detailed image description (60,553 characters)
(1,120 characters I've asked for a detailed description).
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
AI #
LLaVA #
AIVsHuman #
HumanVsAIDamn I want to find out what that long, thin cock feels like when it hits my second hole.
Aside note:
As far as I know, you can only send
posts to a Friendica forum with an exclamation mark to have them forwarded to all members. But you cannot do that with
comments, not in a conversation whose (start) post did not go to that forum.
On Friendica and all its descendants, a reply is never a stand-alone post. It's always a comment on another post.
Thus, mentioning a Friendica forum in a comment with an exclamation mark is futile.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
FediTips From what I've read, a digital photograph is considered the default. So for brevity reasons, it
must not be mentioned.
Any other media
must be mentioned, whether it's a painting, a screenshot from a social media app, a scanned analogue photograph, a flowchart, a CAD blueprint, a 3-D rendering or whatever.
But an alt-text must
never start with "Image of", "Picture of" or "Photo of". That's considered bad style and a waste of characters and screen-reading time. If the medium is not mentioned, digital photograph falls into its place as a default.
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta How conversations work is not unified all across the Fediverse. Even how
connections work is not unified.
Mastodon has taken over the follower/followed principle from Twitter which is always illustrated with arrows with one point. A following B is illustrated with an arrow from A to B. A being followed by B is illustrated with an arrow from B to A. A and B following each other mutually is illustrated with one arrow from A to B and one arrow from B to A.
It appears to me that Friendica has adopted this to become more compatible with Mastodon. But its several descendants, created by Friendica's own creator, starting with Hubzilla, haven't.
Hubzilla, (streams) and Forte still have the bidirectional "connection" or "contact" as the default. It's illustrated with one arrow, but with one point on each end.
Also, all three understand a threaded conversation as an enclosed contruct entirely owned by the conversation starter. Everyone on these three who has the start post on their stream always actually has the whole thread on their stream.
In fact, all three have Conversation Containers implemented. This feature was in 2022. Forte has had it from the get-go as it started out as a fork of (streams). It was eventually turned into and backported to Hubzilla last year.
All three make sure that everyone who has a post on their stream also always has all comments on that post, at least those that are made after they have received the post.
This works on two basic principles:
- All comments go directly to the original poster because the original poster owns the thread.
- Those who have the post automatically receive all comments from the original poster.
In a pure Hubzilla/(streams)/Forte system, your above example would look like this:
- User 1 and User 2 are connected.
- User 1 and User 3 are connected. (This doesn't even matter.)
- User 2 and User 3 are connected.
- User 2 and User 4 are connected.
Much simpler than explaining everything with "following" and "being followed", isn't it
Now, the conversation works like this.
- User 2 sends a public post, thus creating a Conversation Container of which they are the owner.
User 1, User 3 and User 4 receive the post. - User 3 comments on User 2's post.
The comment goes from User 3 to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 4 who already have User 2's post on their streams. - User 4 comments on User 3's comment.
The comment goes from User 4 past User 3 straight to User 2, who is the owner of the conversation, and it is automatically forwarded to User 1 and User 3 who already have User 2's post on their streams.
The only mentioning that occurs here, if any, is User 4 mentioning User 3. This is not necessary for User 4's post to reach anyone. This is only necessary to make sure on Hubzilla (which doesn't have a tree view) that User 4 is replying to User 3's comment and not to User 2's post.
On Mastodon, for comparison, everything depends on who follows whom, who mentions whom and whose instance knows whose instance.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
Conversations #
FEP171b #
ConversationContainersIn general, you've got two options.
If you don't add a title, Friendica sends the post as a Note-type object. Mastodon will show it with only basic text formatting, i.e. no tables, no horizontal lines, no custom typeface, no text size, no colour, numbered lists converted to bullet-point lists.
As for the images, Mastodon will not show any images within the post. It will show the first four as file attachments below the post, and it will completely ignore the rest because it can't handle more then four file attachments. Even this only works because Friendica, like its descendants, sends images both embedded in the the post and as file attachments. Still, Mastodon throws away all attached images except for four.
If you do add a title, Friendica sends the post as an Article-type object by default. (You can configure Friendica to send posts with titles as Note-type objects as well.) But Mastodon currently still refuses to render Article-type objects. Instead, it just shows the title and a link to the original. The reason for this is a somewhat longer story that involves Mastodon, and some headbutting between their creators and then-developers over full HTML rendering.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
Friendica #
Hubzilla #
ActivityPub neck. book of hours, England ca. 1300. Baltimore, Walters Art Museum, W.102, fol. 93r.
Since you're obviously new in the Fediverse, here's a bit of information that you may not know yet.
You cannot only follow Friendica accounts from Friendica. Neither can you only follow Mastodon accounts from Mastodon.
You can actually follow Mastodon accounts from Friendica. And vice versa, you can follow Friendica accounts from Mastodon.
In fact, you can follow just about
anyone anywhere in the Fediverse from both Mastodon and Friendica. For .
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FediverseFinal Fantasy IX:
. - , -, -- . , , .
My definition of "living under a rock":
is rapidly growing from people who escape from Facebook.
is outright
exploding from people who escape from Instagram.
But you still believe that is only Mastodon because even
the mere existence of Friendica or Pixelfed or still hasn't made it into your little Mastodon bubble yet.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Pixelfed #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverse Because if you want full-blown user rights and all the same features as a local user on
all over 30,000 Fediverse instances, you need a local user account on each one of them.
This means two things:
- If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.
- If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.
For one, this is utter overkill.
Besides, this is technologically impossible. This would require
all Fediverse instances to know
all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse.
And, of course, it would require a newly-launched instance to know
all Fediverse users. Again, with no exception.
How and from which source are they supposed to know
That said, there is a single sign-on system for the Fediverse. It's called . It was created by
Mike Macgirvin (creator of Friendica and all its descendants) in the late 2010s already for now-defunct , a fork (of a fork) of which, in turn, is a fork of the currently hyped Facebook alternative . It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing , got it, too.
However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere.
As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop.
Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so.
OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything.
For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile.
If you're logged out, and you go to my profile page, you see nothing.
But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile.
And all of a sudden, you see my profile.
That, for example, is what OpenWebAuth is for.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Friendica #
Hubzilla #
Zap #
Streams #
(streams) #
Forte #
SingleSignOn #
OpenWebAuth Friendica has only got client-side support, i.e. Hubzilla, (streams) and Forte recognise Friendica logins, but Friendica doesn't recognise
any logins.
Also, the instance that you visit while logged in must accept cookies. And if you're using Firefox and containers, the instance that you're logged in on and the instance that you visit must be in the same container.
But in general, this is technology from the late 2010s. Zap was declared stable with it in 2019. It was backported to Hubzilla in 2020, and it was immediately made available on everything that came after Zap.
At least for me, it generally works like a charm. Both Hubzilla and (streams) instances recognise my Hubzilla login if all precautions are met.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
OpenWebAuthNew entry of AI-generated and added to our :
The 's
And "part of the Fediverse" means that
everything is connected with everything else.You can follow Friendica accounts from Mastodon.
You can follow Instagram accounts from Mastodon.
You can follow PeerTube channels from Mastodon.
You can follow Mastodon accounts from Friendica.
You can follow Instagram accounts from Friendica.
You can follow PeerTube channels from Friendica.
And so forth.
. And it's all connected with each other just the same. I mean, what if I told you that this comment comes to you, to Mastodon, not from Mastodon, but from something called that has got absolutely nothing to do with Mastodon
What's absolutely unthinkable outside the Fediverse (being on Twitter and following Facebook users or YouTube channels from there, and Facebook users replying to your tweets from Facebook) is totally normal in the Fediverse. It's part of what makes the Fediverse the Fediverse.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Pixelfed #
PeerTube #
Friendica #
Hubzillahat tip John Oliver, Last Week Tonight. He's praising the resignation letter where she wrote "I expect you will find someone who is enough of a fool or enough of a coward to file your motion, but it was never going to be me" & he says she may as well have added "bitch" to the end. Clippy was twisted in a good way!
is Clippy
Here's another thing that you may not know about and yet: Not only do they have quote-posts, but they also have pretty effective anti-quote-post defences.
Hubzilla
Hubzilla has a permission setting named "Can source/mirror my public posts in derived channels". It has been there since 2012 when Hubzilla was still a fledgling project named Red, that's 13 years now.
Whether someone may quote-post ("share") your public posts depends on the setting in the channel role. If your channel is set to "Public", I think everyone is allowed to share your public posts. If it's set to "Private", you can (and have to) grant that permission to your connections individually by contact role. Those whom you aren't connected to are not allowed to share any of your posts.
The "Custom" channel role lets you choose between granting that permission, one out of 17 permissions, to:
- everyone in the Fediverse
- everyone on Hubzilla and (streams)
- everyone on your home hub
- unconfirmed and confirmed connections
- confirmed connections
- only those whom you individually grant that permission
- nobody but you
(streams)
(streams) goes even further. As far as I know, it doesn't give you the option to let everyone quote-post any of your posts in the first place. Not only are you always opted out to the point that only you yourself may quote-post your posts, but you can't even fully opt in.
No matter if your channel type is "Social - Public" or "Social - Restricted", the only ones who are allowed to quote-post even only your public posts are those of your connections who get the permission from you. Unlike on Hubzilla, however, you don't have to fumble around with permission roles, although you may do so to speed things up. You've also got a dedicated switch for this permission on each connection labelled "Grant permission to republish/mirror your posts".
The effect
This permission has its strongest effect on Hubzilla, (streams) and Forte: If one of their users is not allowed to share one of your posts, the Share button is missing altogether. And there's no real way around the Share button.
In fact, the Repeat button is missing, too. If you aren't allowed to quote-post it, you aren't allowed to boost it either. This permission is not about
how you may forward someone's content, but
whether you may forward it.
Unfortunately, Fediverse users probably everywhere else are not affected by this permission. Users of Pleroma, Misskey and their respective forks can still quote-post you to their heart's content. And I've got my doubts that Mastodon will understand this permission when it introduces quote-posts.
Then again, it's highly likely that Mastodon's quote-post opt-in or opt-out won't work outside of Mastodon either.
Privacy as an extra line of defence
If you
really want to be safe, you've additionally got the option to not post in public. Any post that isn't public can neither be repeated (boosted) nor shared (quote-posted).
Both Hubzilla and (streams) give you the option to send a post to the members of a privacy group/access list (think Mastodon list on coke and 'roids), to a specific group/forum or to any individual selection of connections of yours. (streams) also has Mastodon's option to send a post to all your connections Hubzilla can emulate that with a privacy group with all your connections in it.
Okay, your post will lose a whole lot of reach. But this is a trick that even Mastodon understands in a certain way: If a post from Hubzilla or (streams) has a restricted audience, Mastodon takes it for a PM. And you can't boost PMs, can you
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Hubzilla #
Streams #
(streams) #
PermissionsEchoes of Language
"A Long Way Home"
"Good! Go home, vamoose! And don't come back!"
These are all thats left of ours, the ones I came in with. , , from the 810th brigade got caught in the grinder, were in piss, sh*t, crap, and blood, Now were getting out of hell.
The surviving soldier shows those who survived.
Depends on the effort per post. It's one thing if it takes you no more than two minutes to describe one image,
any image.
But my own current standards for myself require me to invest several hours into description and explanation for a meme post based on a standard template. For one of my original images, I would need two days now. I would because I can't properly describe at least some of my old images. They're pictures of the past. What they show is no longer there. This means that I can no longer source all the detail informations necessary for an image description on my current level.
In fact, my current level, my current standard isn't even really defined. I'm working on a new series of image posts, I have been since last year. And I may or may not try something new, namely long image descriptions (not to be confused with the short image descriptions in the alt-texts) in little HTML files linked into the post. As long as I don't know if that's actually better than putting the long descriptions directly into the post, inflating it to a titanic size, I can't touch older posts anyway.
That is, if I added a full set of image descriptions to each one of my oldest images, I would also have to go and
upgrade my more recent image descriptions to my current standard. I don't want the quality of my image descriptions to tank at some point two years ago.
While I'm at it, I'd generally have to upgrade all my old posts in several ways. Placement of hashtags. Choice of hashtags, especially filter-triggering hashtags. Mastodon-style content warnings in the summary field, along with summaries, especially for any and all posts and comments that exceed 500 characters.
Trouble is, Mastodon doesn't understand edits from Hubzilla. All posts would go out to my hundreds of Mastodon connections on countless instances once more as brand-new. This would be extra awkward for posts about events that were years ago.
#
Long #
LongPost #
CWLong #
CWLongPost #
Fediverse #
Mastodon #
Hubzilla #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Hashtag #
Hashtags #
HashtagMeta #
CWHashtagMeta #
CW #
CWs #
CWMeta #
ContentWarning #
ContentWarnings #
ContentWarningMeta