Find the latitude of any place.  

Patriots draft results: Instant grade for

Patriots draft results: Instant grade for long snapper Julian Ashby

Well, when I describe my images, I have to assume four things.
One, nobody in the Fediverse is even remotely familiar with anything in my images. So what I can't assume is that anyone knows anything about my images anyway, and that it needs no description.
Two, someone somewhere out there might stumble upon my virtual world image posts and end up totally excited because they're proof that the so-called metaverse is, in fact, not dead. And as excited they are, they're also curious about these virtual worlds. Even if they're blind. This means that even if my images focus on something specific, they're just as curious about the whole surroundings.
Three, blind and visually-impaired people want to have the exact same chances at experiencing images as fully sighted people. Now, when someone fully sighted stumbles upon one of my virtual world images for the first time, do you really think they only look at what I say is important in the image Of course not. Instead, they go on a discovery journey through a whole new and completely unknown universe. They take in all the big and small details in the image, whether these details matter in the context of the post or not.
Well, and I have to assume that blind or visually-impaired people want to have a chance to do the exact same thing. But in order for them to be able to do that, I have to help them by describing all the big and small things.
Four, when I mention something in my images, and someone doesn't know what it looks like, and they can't see it, they want to know what it looks like. Not describing them would be lazy, selfish and ableist. And having blind or visually-impaired users ask me about details is just as ableist. They don't want to have to ask. They want to be told right away. I mean, otherwise I wouldn't have to describe my images at all. If someone wants to know what they show, they can ask, right
And so I have to describe my images at an extremely high level of detail.
In addition, I have to explain my images so that people understand the image description. I'm currently working on a series of virtual fashion portraits, so-to-speak, so they need tremendously detailed descriptions of the avatar. But nobody will understand the descriptions if I don't explain everything from the ground up.
So right now, the long image description starts with some 12,000 characters of explanations in the preamble before any visuals are described. It'd be even more if I had to explain the location where I've taken the images. But I hope I can safely assume that nobody wants to know where the images were taken if the entire background is a neutral, featureless white.
I guess things would be much easier if discussion groups had always been an integral part of the whole Fediverse, including Mastodon, and not just a fringe phenomenon that nobody knows about.
There could be a group about accessibility in the Fediverse, populated by online accessibility experts, by actually blind or visually-impaired people, by people who are both like Veronica with Four Eyes and by Fediverse users who want to get their image descriptions as right as possible. They could all discuss things not only with the thread starters, but with one another.
I could go there and ask the questions I have, and I actually have many questions. And people wouldn't just answer me independently from one another. They would see everyone else's answers and comment on these. They would start discussing the topics amongst one another from different points of view to find the best solution, the best answer.
But I can't do that because there are no such discussion groups, and everyone is in places that neither have nor support groups in the first place.
The best I can do is ask a question and then mass-mention not only Guppe groups on accessibility, but also a bunch of Fediverse users of whom I know that they are blind or visually-impaired. Unfortunately, Veronica with Four Eyes, a proponent of describing all images twice like I do, is not even active in the Fediverse, if she's there at all.
I've done that last year when I needed to know if I have to describe what the herringbone fabric pattern looks like or what a full brogue shoe looks like in general and what a specific full brogue shoe looks like in particular, or whether I can assume that to be known. I think I got three independent replies although, fortunately, everyone mentioned each other. They said that I don't have to describe them, and one or two said that I can safely assume that people know what I mean if I just drop the names.
Right now I'm wondering if I can safely assume that everyone knows what the three lions in the Royal Arms of England look like, or whether they need their own detail description. I have to deal with a number of sports jackets with the three lions on the buttons, that's why. And in fact, the buttons are so small in the images that even sighted people can't see the three lions on them.
Also, I'm wondering if everyone is familiar with the term "shank button", or whether that requires an explanation, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta Das stimmt nur teilweise. Die Dopaminjunkies sind weitgehend zu Bluesky abgehauen, weil sie da mehr Follower haben. Und einige Mastodon-Nutzer wollen tatschlich diskutieren. Aber:

Und so hast du in Mastodon dann Threads, wo 20 Leute dasselbe antworten, ohne voneinander zu wissen. Oder mit sten, wo immer nur einer mit dem Threadstarter diskutiert, weil die anderen davon nichts merken, weil keiner wei, wie und wo man sich einen Thread in ganzer Ausdehnung angucken kann, oder weil deren Apps das nicht knnen.
Wenn dann doch mal mehr als zwei Leute diskutieren, erwhnen sie sich alle einen Wolf, um alle Beteiligten in der Diskussion zu halten. Und dann jammern sie, weil neben den ganzen Erwhnungen und der vom Vorgnger automatisch und unwissentlich bernommenen CW von ihren 500 Zeichen kaum mehr was brig ist.
Und trotzdem halten alle das fr das Gelbe vom Ei, weil sie es nicht anders kennen. Also, mit Ausnahme der Nicht-Mastodon-Nutzer, die sich in den Thread verirren und vom Rumgehampel der Mastodon-Nutzer genervt sind.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonMarshall Sutherland This is one of the big differences between Mastodon and Hubzilla.
Mastodon users can only do what they've got buttons for, and they can only toot plain text.
Hubzilla users not only have more buttons at hand, but they can do even more things by manually typing raw code.
Another big difference:
The huge majority of Mastodon users is mostly or exclusively on phones. Many don't know what copy-paste is because they've never used an actual computer, only ever phones instead. For the rest, copy-paste is too fumbly to bother, what with the touch screen being their only input device. Thus, unless Mastodon users get a quote or quote-post button, the only halfway convenient way for them to quote anything is by tooting a screenshot with no alt-text.
On Hubzilla, everyone's on desktop and laptop computers with hardware keyboards and dedicated pointing devices. Copy-paste is a breeze here.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla(This is technically a repost of , but with "unseen" images for the by , a modified post text and an upgraded set of long image descriptions. I didn't have time to complete the descriptions for a set of wholly new images.)
is probably the oldest 3-D virtual world based on free and open-source software (OpenSimulator) and run by community members. It's definitely the oldest 3-D virtual world that's federated with other virtual worlds.
These images are from OSgrid's 17th birthday celebration in July, 2024.
My little in-world sister Juno Rowland, part-time OSgrid resident just like myself, celebrated the grid birthday with outfits based on the officially-issued women's tank tops. The first image shows her wearing one of these outfits on her pier at her now-soon-to-disappear home at Tropicana Tuneage on Friday, July 26th. She had been around the birthday sims on Thursday already, but in a different skirt. On Friday, she posed in one that's much easier for me to describe in front of a background that's a great deal easier to describe than the anniversary sims.
One day later, on Saturday, July 27th, she went and revisited the birthday exhibitions, also to see one of her favourite things, a Leonard Cohen album cover at an exhibition. The second image is from there.

Juno's look





Image descriptions


The medium and the basic setup


Both images in this post are digital renderings from inside a 3-D virtual world, using shaders, simplified real-time reflections and an artificial sun as a directed light source for illuminating the scenery and casting shadows, but without ray-tracing. It shows a digital avatar made to look like a fairly young woman. In the first image, she is standing at the end of a wooden pier. In the second image, she is standing next to a painted portrait of Leonard Cohen which he has used as an album cover.

The locations


The images were created in two different places in OSgrid, known as sims. Both are linked to the 17th anniversary of OSgrid which was celebrated from July 22th to July 28th, 2024.
OSgrid is a virtual world, a so-called "grid", based on a virtual-world engine named OpenSimulator. OpenSimulator, OpenSim in short, is a free, open-source, server-side re-implementation of the technology of Second Life. It is not affiliated with Linden Lab, the creators and owners of Second Life.
Second Life is a centralised, commercial 3-D virtual world launched in 2003. It experienced a big hype starting in 2007 which faded away in 2008. It still exists, it is constantly evolving, and it is celebrating its 21st anniversary this month.
The development of OpenSim started in 2006, originally under the name of OpenSecondLife, then OpenSL, by reverse-engineering Second Life's viewer API and building a virtual world server against it. In early 2007, Linden Lab laid open the source code of the official Second Life viewer, the client application needed to access Second Life. This revealed large parts of Second Life's technology and made not only the development of third-party viewers possible, but also facilitatted OpenSim's development. It was also in early 2007 that the first test version of OpenSim came out.
Second Life, as well as the worlds based on OpenSimulator, are referred to as "grids" because they are split into square regions of 256 by 256 metres or roughly 280 by 280 yards. This roughly corresponds to a bit more than three by two major-league football pitches or soccer fields or a bit less than three by two American football fields.
While Second Life is a walled garden with only one publicly accessible grid that is connected to nothing else, OpenSimulator can be used by just about anyone to create and run their own grid. In 2008, a new feature called the Hypergrid was introduced that allows avatars registered on one grid to visit other grids. Thus, OpenSim is not only decentralised, but actually mostly federated. There are currently over 3,000 active grids, maybe over 4,000, and especially most of the larger public grids are connected to the Hypergrid.
Sims, in turn, are short for simulators which have to run in regions for any kind of content to be able to exist in them and for avatars to be able to enter them. In Second Life, one sim always covers one region. OpenSim has so-called varsims which can cover multiple regions arranged in a square without having borders between the regions. The upper limit imposed by the software is 32 by 32 or 1,024 regions, but anything significantly larger than 16 by 16 or 256 regions has been proven to be highly impractical.
OSgrid was the first public OpenSim grid. It was launched in July, 2007, as a proving ground for OpenSim's own development which it still is. Nonetheless, it was the first OpenSim grid to surpass Second Life in land area, and it currently is one out of two grids to have done so. Also, as early as 2007 already, OSgrid referred to OpenSim in general and then, by 2008, to itself as "the Open Source Metaverse". It has used this term for an actual virtual world 14 years earlier than Mark Zuckerberg. For about just as long, the word "metaverse" has been part of the standard vocabulary in the OpenSim community.

The avatar in both pictures


The avatar shown in the image is Juno Rowland. She is, in fact, a backup avatar for my female alt, short for alternate avatar, that goes by the same name and looks the same while being at home on another grid.
Juno is built to look like a young woman. OpenSim does not explicitly support different ethnicities, but the basic avatar-building components available in OpenSim are almost exclusively geared towards avatars looking white or Latin American and in the 30s at most. She is 1.74 metres or 5 feet 8 1/2 inches tall which is taller than the average real-life Western woman by about the length of an adult person's palm. She is fairly slim which is somewhat concealed by the loose fit of her clothes.
Juno's skin textures are light to medium-light. Highlights and partly also shades are part of the skin textures, but very subdued. Most shading on her is created by the shader built into the viewer.
She has brown eyes and black hair worn as a rather short bob that narrows downward from where her ears are and extends to a height halfway between her chin and her shoulders. Her bangs cover her forehead entirely. Strands of her bangs partly cover her eyebrows, and two of them extend down as far as her upper eyelids. On each side, a single thick lock extends forward and slightly inward. These locks occasionally cover parts of her lower cheeks.
Juno is wearing a loose-fitting black tank top with the official logo of the 17th grid birthday festivities on it. The logo stretches across about 90% of Juno's chest and from slightly higher than right below her breasts to slightly higher than the middle of the front of the shirt.
In the top left corner of the birthday logo, there is the OSgrid logo. It consists of five identical parallelograms. Each one of them resembles a rectangle which, when placed horizontally, has its short edges tilted to the right by 18 degrees. The long edges are longer than the short edges by about three quarters. These five parallelograms are arranged around a common centre at the same distance and at angles of 72 degrees from each other. There is always one pointed angle slipping under the long side of a neighbouring parallelogram. This way, the gap in the middle between the parallelograms is a five-point star. The outer short edge of each parallelogram is farther away from the centre than the parallel long edge of the neighbouring parallelogram by a bit over half the latter's width. The top right parallelogram is placed exactly vertically.
The whole logo has a light, yellowish orange tint. Size-wise, it takes up a bit more than 20% of the width and about 70% of the height of the entire birthday logo.
To the right of the OSgrid logo, there is the name of the grid, "OSgrid", written in all capitals in the same tint of orange as the OSgrid logo. The writing is about two thirds as tall as each parallelogram in the OSgrid logo is long. It starts to the right of the vertical top right parallelogram at roughly 80% of its width, and the top of the letters is slightly higher than the obtuse top right corner of the top right parallelogram. The typeface used is a heavy variant of the Futura typeface, a geometric sans-serif typeface known for fairly small lower-case characters and a lower-case "a" which is like a "d" with a shorter line, much like in hand-writing.
Right below, "The Open Source Metaverse" is written at a vertical distance that is roughly the same as the general thickness of the letters in the "OSgrid" writing. All four words start with capitals. The writing lines up with the "OSgrid" writing to the left. The typeface is the same as the one used for the "OSgrid" writing, only smaller by about 60%. It is small enough to not be easily readable in the image at the resolution at which the image was posted. The writing is tinted a light grey, resembling aluminium.
Most of the lower half is taken up by a horizontal rectangle, tinted a darker, slightly less saturated, slightly more brownish tone of orange. To the left, it lines up with the bottom pointy-angled corner of the bottom left parallelogram in the logo. To the right, it lines up with the end of the writing "The Open Source Metaverse". At the top, it almost touches the vertical line of the "p" in the same writing.
On this rectangle, "17th Birthday" is written in the same black as the rest of the tank top and the same typeface as the other two writings, but twice the height as the writing "The Open Source Metaverse". Vertically, this writing is slightly above the middle of the rectangle. Horizontally, it lines up with the other two writings on the left.
Below the tank top, Juno is wearing a straight, loose-fitting miniskirt which ends roughly the length of one of her hands above her knees. Its texture gives it a look like washed-out denim in various shades of slightly yellowish, medium-light-to-medium brown. Seams, pockets and the fly are all only part of the texture. The pocket on the front to the left from Juno's point of view is completely covered by the tank top, the pocket on the other side is mostly covered. The texture does not emulate any rear pockets.
Apart from the skirt, Juno's legs are bare. On her feet, she is wearing a pair of flat ballet shoes which mostly show a black texture, slightly lighter than the tank top, with a structure that resembles an unidentified fabric. The insides of the shoes are a medium-light, shaded tone of brown, suggesting some fabric or thin leather again. The soles are a medium-light, slightly reddish brown. They have very low heels.
Around her neck, Juno is wearing a necklace consisting what appears to be a single wire of solid gold of a similar thickness as the material used for clothes hangers plus an OSgrid logo made of gold as well. The logo is a bit over half as big as the one on her tank top. The eye through which the wire runs is attached near one of the outer obtuse-angled corners, so the logo is rotated to the left in comparison with the one on the tank top. Both the wire and the logo are glossy, the logo more than the wire, but the material appearance is textured onto both.
In both Second Life and OpenSim-based worlds, unlike most other 3-D virtual worlds, avatars are not only highly configurable in-world, but also highly modular. Everything on Juno is an attachment. Her body is an attachment, the head included. Her feet are a separate attachment different feet for medium and high heels are available. The skin textures can be replaced, and standard skins can be worn on this body. The eye texture can be replaced, too. Eyelashes, fingernails and toenails are attachments, although the latter are fully concealed inside her shoes. Her hair is an attachment. The top, the skirt, each shoe and the necklace are separate attachments which makes it possible for her to wear all kinds of outfits. Her shape is configurable with over 80 parameters, and even that can be replaced with another one which is usually just as configurable.
Everything that Juno is made up from was made by users. Everything else, including the purpose-made texture on the tank top, was made directly for OpenSim.

The scenery in the first image


The first image was created on a sim called Tropicana Tuneage, a multi-purpose sim which is regularly used for events, but which is also Juno's home in OSgrid.
The scenery is limited to a wooden pier which Juno is standing on. It takes up the lower 45% of the image. Its water-side end would line up with the lower side of Juno's butt if she was shown from behind. The top surface of the pier is textured in a way that suggests wooden planks that run transversally across the pier. The wood is very slightly less yellowish tone of brown than Juno's skirt and varies greatly between light-medium, almost light, and medium. The sides of the pier are outside the borders of the image.
The pier leads to the southwest. The camera angle follows it almost exactly in parallel. It is oriented farther to the right by about one degree. It is also roughly at the height of Juno's waist.
Beyond the pier and behind Juno, there is nothing but blue sea with gentle waves on it. The tone of blue has a fairly low saturation, and some of the waves are partly almost medium-dark grey. The horizon is at almost precisely two thirds of the height of the image, roughly below Juno's breasts, which shows that the camera is tilted downward by a few degrees.
The sky is a very pale, greenish blue with a very faint gradient towards the horizon that suggests haze. To Juno's right, there are some thin clouds which increasingly blend in with the sky, the lower they are. A bit of cloud is above her head as well. There are no clouds to her left.

Juno in the first image


Juno is slightly left of centre, standing on her right foot while moving her left foot forward and turning it to the left. She is about to turn herself around. Her arms are on her sides, the left arm is moved a bit forward. Her hands are relaxed with both middle fingers bent inward a little more than the other fingers.
Juno's face is expressionless. Any expressions would require specific animations to be played, mostly manually which would be an extra effort. She is looking past a point slightly above the camera.
Her hair is fully covering her ears. The lock on the left of her face, the right for the on-looker, is in front of the lower parts of her cheek. So is the lock on the other side, but less so.

Lighting in the first image


The simulated time of day is late afternoon. The sun is quite low already in the west. This can be told by the shadows which Juno's legs cast on the wooden planks texture on the pier as well as some narrow highlights on her neck, her arms and her legs. The sun itself is not in the image.
Apart from the sun, there is medium grey ambient light that shines the same from everywhere and therefore doesn't create any shadows.
Save for being cropped, the image is unedited and unprocessed.

The scenery in the second image


The second image was created in a different place on the same grid named OSG17B2. The name refers to OSgrid's 17th birthday, OSG17B in short. It is the second one of four numbered exhibition sims created for the birthday, two of which were opened to the public while the other two remain unused.
In the second image, Juno is inside a building used as a gallery of music album covers.
Most of the right-hand 60% of the image are taken up by an art easel. It is about one and two thirds times as high as Juno is tall while appearing smaller due to the perspective. It is rotated to the right from the camera being directly aimed at its front by about 25 degrees.
The easel is a fairly stable and elaborate construction which looks like it is adjustable for various canvas sizes. Below where the canvas would be put, there is a shelf for painting utensils. The easel is mostly white with no texture on it. The exceptions are eleven slotted screw heads and a handle roughly shaped like a six-point star with which the easel can be adjusted to different canvas sizes. They have metal-like, partly light grey, partly light yellowish or brownish textures with medium-light orange spots hinting at corrosion. These textures include highlights and shading. The parts themselves are not shiny. Of the screw heads, only five are unobscured. One is holding the adjustment handle in place. Three are holding the almost vertical part of the easel together, one close to the top, two near the bottom. The fifth one connects the right-hand rear support to the foot.
The easel is adjusted for something way bigger than what it is carrying. It's the cover of the album Recent Songs by the singer-songwriter Leonard Cohen. It was released in 1979 as his sixth studio album, and it is not known for high-charting single releases. The cover is about half as high as Juno is tall. Again, due to the perspective, it appears to be smaller. Its aspect ratio is very slightly warped, it is a little wider than it is high.
The album cover is based on a frontal facial portrait painting of Cohen by Dianne Lawrence. It shows him as a middle-aged, light-skinned man with green eyes and black, medium-short hair which he wears in a somewhat asymmetrical hairdo that is slightly fuller on his left, the on-looker's right, than on the other side. The top of his hair is cut off by the top edge of the canvas. At the bottom, the portrait ends at Cohen's shoulders. He is wearing a black shirt which lacks too many details to be identifiable any further.
The background behind him is a solid, slightly pale medium blue with a minimal hint of green.
Above his right shoulder, his left shoulder from the on-looker's point of view, there is a drawing of a hummingbird which is only black and background blue and about as long from beak to tail feathers as Cohen's mouth is wide. The bird seems to be hovering above his shoulder with no intention to touch down. Its beak is oriented to the right for the on-looker and tilted slightly downward to between Cohen's shoulder and the collar of his shirt.
Between the top left corner and Cohen's hair, his name is written, "Leonard Cohen". Likewise, between his hair and the top right corner, the title of the album is written, "Recent Songs". Both are in black, fairly small, in an unidentified, very heavy geometric sans-serif typeface and in all-caps.
The narrow right-hand side of the box that has the portrait on its front has a medium-dark wood texture, slightly reddish, slightly greyish, with the grain perpendicular to the long edges.
The wall behind the easel is mostly white with a black circular pattern on it. It consists of 39 concentric circles whose thickness increase from the outermost to the innermost circle. Instead of a 40th circle, there is a dot in the centre which is a little bigger than the thickness of the innermost circle. The texture itself is a bit over one and a half times as high as Juno is tall and twice as wide as it is high. Thus, it has ample of white space on both sides whereas the outermost 16 circles are more or less cut at the top and the bottom. Two of these patterns are within the border of the image above one another. The upper one is cut off by the upper edge of the image in such a way that only the two innermost circles are complete.
The wall makes up a bit less than the upper two thirds of the background of the image. Apart from Juno and the easel, everything below is ground. The edge between the wall and the floor shows that the camera is rotated from being perpendicular to the wall by some five degrees to the left. Thus, the easel is rotated to the right by about 20 degrees from being parallel to the wall. Besides, the camera is as high above the ground as Juno's waist and tilted downward only very minimally.
The ground is a medium orange in the bottom left corner of the image. It gets a little darker and more purplish towards the opposite corner where it meets the wall.

Juno in the second image


Juno is on the left-hand side of the image. standing in front of the easel, a little left of its centre, and facing it. The image shows her to the left of the easel and from the rear right. Her head is tilted downward as if she was looking at the album cover. Her face is entirely on the far side of her head. The bottom of her hair is shifted to the back and to the left because she is actually in motion. Her right ear is still fully concealed under hair.
Her arms are relaxed on both sides. She is resting her weight on her right leg while having lifted up the heel of her left foot.
The right strap of her tank top is hovering above her right shoulder at a distance of a little more than the thickness of one of her fingers. The background appears through the gap.

Lighting in the second image


The only light available in the image are the omnipresent medium grey ambient light and several white point lights on the ceiling beyond the edges of the image, only one of which is on this side of the wall. The sun is fixed straight above the scene, but the roof of the building which is outside the image is in its way. Since shadows are on in this picture, the roof keeps the sunlight out. Point light sources like those on the ceiling don't cast shadows, so they add to the ambient light, but they only illuminate avatars, objects and the like from one side. The highlights on her legs hint at the position of the sole point light on this side of the wall, namely behind and slightly to the left of Juno.
Save for being cropped, the image is unedited and unprocessed.
#Long #LongPost #CWLong #CWLongPost #AltText #ImageDescription #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OSgrid #OSG17B #UnseenImageChallengeI wanted to participate in today's motto of the Unseen Image Challenge. But I wanted to do so with descriptions of actual images. And it made more sense to complete a set of descriptions that I had been working on since last year (yes, I know that other people take only a few seconds to fully describe an image) than to make an entirely new image.
However, even at the most limited extent, that would have meant one post, four images, twelve portraits, at least with no background whatsoever, with the same avatar in all twelve outfits, with a whole lot of similarities in the outfits and with always the exact same posture.
Nonetheless, I had to complete the preamble and improve it in parts. I had to write a detailed description of the custom shoe design in almost 2,000 characters. And I had to describe four variants of the same sports jacket and five variants of the same button-down shirt (I've done one jacket and three shirts now). It takes me longer to describe one button than it takes most people to describe an entire image. And I'm talking about portraits of a 3-D virtual world avatar.
In fact, I wanted to use this as a test balloon for which way of offering long image descriptions (not long as in 800 characters in the alt-text, but long as in well over 20,000 characters elsewhere) is better. I wanted to post the same images twice.
For one, I wanted to do as I always do and add a block with the long descriptions of three images and twelve portraits in the post itself, below all three images. The description block would start with a very long preamble that explains everything and describes what the images have in common, followed by individual descriptions of each image.
I know that this works technically, but it would inflate the post itself to way more than 40 times the size of a Mastodon toot, and it would put a whole lot of distance between each image and its individual description.
Besides, I wanted to make complete descriptions for each image as HTML documents, include each image plus alt-text in the respective HTML document, upload the HTML documents to the file space in my channel and put a link to each document underneath the corresponding image in the post.
This would have put the descriptions fairly close to the images, and it would have dramatically reduced the length of the post. But it would have been entirely untested. It may pretty well have blown up in my face. Besides, the descriptions wouldn't actually be where the images in the post are. And users of dedicated mobile apps wouldn't be able to read the image descriptions in their apps. Instead, tapping the description link would open the browser (provided what I plan to do works in the first place).
Well, I had to nix this for today because there's no way I can get it all done within the next bit over one hour.
Instead, I may use the two images of Juno Rowland that were the last original images I posted, combine their alt-texts and long descriptions with fully black images and correct the image explanation where it's actually factually wrong. The post with these images in them is from last year. That's so long ago that I guess nobody remembers it anyway, so I hope this doesn't count as cheating.
I may actually post the "images" here on my Hubzilla channel instead of on . Since there's nothing to actually see in the images, I don't have to be afraid of triggering anyone with eye contact.
As for my new portraits, they will go on (streams) because they will contain eye contact. But I can't say when this will be. There's still so much to do in the image descriptions.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #UnseenImageChallenge


<>

Ich schtze, mehr als 90% der heutigen Fediverse-Nutzer auerhalb von Lemmy kennen eigentlich nur Twitter (hat keine Gruppen) und Mastodon (hat auch keine Gruppen). Die allermeisten wiederum davon sind seit Ende Oktober 2022 vor Elon Musk von Twitter geflohen.
Wenn Mastodon ein Feature nicht hat, dann glauben sie, das ganze Fediverse hat dieses Feature nicht. Und etwa jeder zweite von ihnen ist heute noch der felsenfesten berzeugung, da das Fediverse berhaupt nur aus Mastodon besteht. Das heit: Wenn Twitter damals ein Feature nicht hatte, ist fr viele schon unvorstellbar, da Mastodon es hat.
Dabei knnte es so einfach sein: Lemmy-Communities und Friendica-Gruppen nach dem durchsuchen, worber man reden will. Oder zumindest nach einer passenden Guppe Group suchen, wo auch was los ist. ber (streams) und Forte knnte man theoretisch auch alle mglichen Arten von Gruppen querbeet suchen. Ich bin auf einer (streams)-Instanz mit etwa einem Dutzend Kanlen, und da ist schon irre, was die alles kennt und im Verzeichnis listet. Aber das ist wenig bekannt, und da gibt's kein zentrales Register, das mu ber eine Serverinstanz gehen.
Dann den Gruppen beitreten, die einen interessieren. Sich damit vertraut machen, wie man von Mastodon aus in einer Lemmy-Community oder einer Friendica-Gruppe einen neuen Thread startet. Und schon hat man Gruppen auf Mastodon.
Statt dessen rufen ber 99% aller Mastodon-Nutzer einfach nur "in den ther", wenn sie z. B. etwas wissen wollen oder irgendwelche Hilfe brauchen oder so. Bestenfalls bauen sie noch zwei, drei Hashtags ein. Die, die immer noch "Twitter im Kopf" haben, tun nicht mal das und glauben statt dessen an Zauberei. Und dann wundern sie sich, da keiner antwortet, weil die allermeisten Mastodon-Nutzer auch nicht wissen, da man Hashtags folgen kann.
Und wenn man viel ber ein bestimmtes Thema lesen will, tritt man auch keiner Gruppe bei. Einem oder mehreren Hashtags folgen tut man auch nicht. Zum einen, wie gesagt, wei man nicht, da das geht. Zum anderen: "Was ist denn das Hashtag fr XYZ" Will sagen, Abstraktions- und Vorstellungsvermgen haben viele auch nicht, geschweige denn, da sie wissen, wie man testen kann, welche Hashtags es gibt.
Statt dessen folgt man tausend Nutzern, die ab und an mal ber das Thema schreiben. Die mllen einem dann mit allem mglichen anderen Zeug und vor allem uninteressanten Boosts im Zweiminutentakt dermaen die Timeline zu, da man von dem interessanten Zeug nur einen Bruchteil liest, weil man keine Zeit/Lust hat, durch alle ungelesenen Posts zu scrollen. Da Mastodon in den Timelines keine Threads darstellt, sondern nur Einzelbeitrge, macht alles noch schlimmer.
Selbst von denen, die schon mal von einem Fediverse ber Mastodon hinaus gehrt haben, wei kaum einer, was die Nicht-Mastodon-Serveranwendungen knnen, also z. B., da Friendica, Hubzilla, (streams) und Forte fderierte Gruppen haben. Auerdem, das haben wir ja Anfang des Jahres zur Genge gesehen, wissen sehr viele nicht, da die verschiedenen Fediverse-Serveranwendungen nicht nur in sich dezentral sind, sondern auch miteinander verbunden.
Mein Gott, wie oft habe ich das mitbekommen, wie Mastodon-Nutzer vor Staunen wie die Autos geguckt haben, als sie gesehen haben, wie sich auf ihr Zutun hin ihr Mastodon-Konto mit einem Pixelfed- oder Friendica-Konto verband. Eine Sekunde vorher hatte das noch deren Vorstellungsvermgen berstiegen.
Aber wie ich vor ein paar Tagen schon schrieb: Wenn Mastodon irgendwann mal Gruppen einbaut, dann mu dieses Gruppenfeature einen sofort sichtbaren, auffallenden Button kriegen. Und zwar berall. Webinterface, iOS-App, Android-App, auch in allen unabhngigen Apps mu dieser Button da sein. Nicht in einem Men versteckt, sondern ganz vorne, sofort direkt im Sichtfeld. Was in einem Men oder auf einer anderen Seite versteckt ist, das findet keiner. Siehe Beitrge im Original ansehen oder Hashtags folgen oder auch nur Filter.
Idealerweise htten das Webinterface und alle wichtigen Apps ein Pop-up, das aufspringt, wenn man nach dem Einbau der Gruppenfunktion das Interface das erste Mal ffnet, und einen ber mehrere Seiten ber Gruppen informiert und erklrt, was das ist und wie das geht. Am besten noch, da das Gruppenfenster beim Schlieen des Pop-up aufspringt und einem schn einen Haufen Gruppen auflistet, am besten noch fr die ganz Doofen/Faulen/Bequemen nach den fnf Hashtags gefiltert, die man selbst am meisten nutzt.
Wenn es nicht berall fr Gruppen einen dicken fetten Button gibt, der einem sofort nach dem ffnen der App ins Gesicht springt, dann wird keine Sau auf Mastodon wissen, da es Gruppen gibt. Und alle werden weiterhin "in den ther rufen" und sauer sein, weil keiner antwortet.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Lemmy #Mbin #Guppe #GuppeGroups #Fediverse #Gruppen #FediverseGruppen #FediGruppen On the one hand, that's the very reason why I give so many and so detailed explanations in the long image descriptions that I put directly into my posts in addition to alt-texts. (I can do that because my character limit is not 500 but 16,777,215.) My original images show extremely obscure niche content, and they aren't even real-life photos. That's why .
On the other hand, additional information must never be available exclusively in the alt-text. Not everyone can access alt-text. Reading alt-text requires working hands. Not everyone has working hands. Those who don't cannot read alt-text. Any and all information that's available only in the alt-text and neither in the post nor in the image is inaccessible and therefore permanently lost to these people.
If accessibility is for everyone, it must also be for those with physical disabilities that prevent them from reading alt-text.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

in 2 days!!!

Its going to be great!

Featuring Karin Hammar Claude Lapalme, Lilac Gilad and many of the regions top trombonists.

Special thanks and big shoutouts to:



&McQuade

Bring a donation for

Links in bio!

Tribalism and brand worship are key factors in all this, yes. While some Fediverse users choose the software they use by what suits them best, especially feature-wise, others behave more like fanbois and fangurls. They cling hard to what they use like someone who has been driving the same car brand for decades out of principle and out of being convinced that everything this brand makes is superior to all the competition.
This seems particularly wide-spread amongst Mastodon users. First, when they joined, they were eager to defend Mastodon against as much better. When they learned about Bluesky and Threads, they started defending Mastodon against these two as much better. But the more they learn what else exists in the Fediverse, like Misskey and its forks or Friendica and its family, they even feel compelled to defend Mastodon against these as well as much better.
In addition, there's instance tribalism. "My home instance is better than yours" or even "my instance is better than all the others!" Not the only reason why Mastodon users refuse to move to a better-suited instance, much less better-suited software, but one of them. That is, this seems more of an issue on Lemmy where users are being judged according to which instance they're on.
But there's also convenience. Moving instances is inconvenient. Always staying on the same instance is convenient. Also, having to configure your account is inconvenient. The default settings being perfect is convenient.
Why do Mastodon users demand all kinds of features be added to Mastodon although they're readily available elsewhere in the Fediverse Not only because most of them don't know that these features are available in the Fediverse outside of Mastodon, but also because they want these features without going where the features are. They want the features to come where they are. They want the features on the instance that they're on right now.
And if these features are optional, they have to be activated by default on their home instance. Oh, and if they don't like a feature, Mastodon must not add it, or at the very least, it must be off by default on their home instance. Yes, even if it's mastodon.social that they refuse to move away from, home of over 20% of the Fediverse's population. See full-text search. See federation with Threads. See the Bluesky bridge. And so on.
From the point of view of a veteran of Mike's nomadic software, this has to look hilarious. Granted, there is some sticking to brands there, too, even on (streams) where the intentional lack of a brand has become a brand of its own, although (streams) users seem to constantly be ready to jump ships to Forte or back to Hubzilla, should (streams) go under. But there is no instance tribalism. For one, there are only so many instances. Besides, if you go nomadic, you're on multiple instances at the same time anyway.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #Tribalism Also, () ist das grte Featuremonster im ganzen Fediverse mit wahrscheinlich der steilsten Lernkurven im ganzen Fediverse. Auerdem ist es eines der lteren Projekte im Fediverse: Es kam erstmals im Mrz 2015 raus, also noch zehn Monate vor Mastodon.
Um's kurz zu machen: habe ich mal eine Anzahl an Tabellen angelegt mit Vergleichen zwischen

Es ist auf eine Art eine Facebook-Alternative. Aber nur deshalb, weil es ein Fork von vom selben Schpfer ist, das tatschlich vor fast 15 Jahren explizit als Facebook-Alternative an den Start ging. Aber es ist kein Facebook-Klon, auch deshalb nicht, weil es sehr, sehr viel mehr kann als Facebook.
Posts knnen da ganz anders sein als auf Mastodon. Du hast ein Zeichenlimit von ber 16,7 Millionen. Du bist auch nicht beschrnkt auf nur vier Bilder als Dateianhnge, sondern du kannst beliebig viele Bilder an beliebiger Stelle in die Posts einbauen, also mit Text darber und Text darunter (wobei Mastodon dann doch nur vier davon als Dateianhnge anzeigen wird). Dabei ldt man die Bilder auch nicht in irgendein Datennirwana hoch wie auf Mastodon, sondern in den Cloudspeicher, der zum eigenen Kanal gehrt. Den kann man sogar per WebDAV als externes Laufwerk einbinden.
Dazu hast du alles, was HTML an Textformatierung untersttzt, von Fett- und Kursivschrift ber sechs berschriften, sechs Arten von Listen und eingebetteten Links bis hin zu Tabellen. Auf Hubzilla kann man mehr Textformatierung erzeugen, als Mastodon anzeigen kann. Allerdings werden Posts mit BBcode formatiert, das man vielleicht noch aus Internetforen aus den 2000ern und 2010ern kennt. Auf Hubzilla ist BBcode mit haufenweise Zusatzfeatures erweitert. Auch deshalb ist Hubzilla eine der ganz wenigen Fediverse-Serveranwendungen, die einen Vorschau-Button haben.
Hubzilla untersttzt Post-Titel, und was auf Mastodon das CW-Feld ist, ist auf Hubzilla immer noch das, was es schon immer war: ein Feld fr Zusammenfassungen.
Hubzilla hat im Prinzip alles, was ein voll ausgewachsenes Blog braucht, bis auf Pingback.
Wenn man nicht will, da die eigenen Blogposts von Mastodon-Nutzern immer nur verstmmelt gesehen werden (oder da man alle Naselang angeschnauzt wird, was einem denn einfllt, ber 500 Zeichen in einen "Trt" zu packen), kann man optional die Artikel-App installieren und Posts als sogenannte Artikel schreiben. Die fderieren zwar nicht, aber das sollen sie dann auch nicht, sie sind leichter auffindbar, und man kann sie in fderierten Posts einfach verlinken.
Hubzilla hat schon seit Anbeginn Gruppen, die da "Foren" heien. Und zwar mit Moderation, mit der Option, zustzliche Admins als Moderatoren zu bestimmen, mit der Mglichkeit, sie privat zu machen, und mit der Mglichkeit, sie aus Verzeichnissen fernzuhalten.
Fr die, die Sicherheit, Privatsphre und Berechtigungskontrolle wollen, hat Hubzilla das zweitbeste Berechtigungssystem im Fediverse (das beste gibt's auf den Hubzilla-"Nachfolgern" von 2021 und von 2024, beide wieder vom selben Schpfer, der auch weiterhin beide pflegt und weiterentwickelt). Es arbeitet auf drei Ebenen: fr den ganzen Kanal, fr einzelne Kontakte und fr bestimmte Inhalte. Das Berechtigungssystem ist allerdings auch einer der Grnde, warum Hubzilla in der Handhabung nicht eben einfach ist.
Fast berall sonst ist das Konto gleich die Identitt. Auf Hubzilla kann man auf einem Konto mehrere separate sogenannte "Kanle" haben. Ein Kanal entspricht dabei einem kompletten Konto woanders, nur eben nicht jeweils mit eigenem Login, sondern alle Kanle auf einem Konto haben einen gemeinsamen Login, und man kann zwischen den Kanlen hin- und herwechseln, ohne sich auszuloggen. Das ist z. B. praktisch, wenn man Kanle fr verschiedene Zwecke hat, etwa einen oder mehrere als Forum. Mastodon und fast alles andere im Fediverse nehmen die Kanle tatschlich als eigenstndige Konten wahr.
Zustzlich kann jeder Kanal auch noch mehrere separate Profile haben. Eins hat man immer, und das ist auch das offizielle, ffentliche Profil, sofern man das nicht auf privat schaltet. Die anderen Profile kann man jeweils Kontakten zuordnen, so da die (wenn sie die Technologie haben Mastodon hat sie nicht) dann ein anderes Profil zu sehen bekommen. Die Idee dahinter ist, da man ein ffentliches Profil hat mit den Informationen, die man ber sich selbst ffentlich bekannt machen will. Dann hat man ein Profil fr die Saufkumpanen, eins fr die Familie, eins fr Arbeitskollegen, und in jedem erzhlt man was anderes ber sich, was die jeweils anderen und die allgemeine ffentlichkeit nicht unbedingt wissen sollen.
Hubzilla geht aber noch weiter: Ein Kanal mu nicht unbedingt nur auf einem Konto auf einem Server lagern. Hubzilla hat etwas, das man "nomadische Identitt" nennt: Man kann einen Kanal auf Konten auf anderen Servern klonen. Die Klone sind dabei aber nicht einfach nur dumme Kopien, wie wenn man mit dem Mastodon-Konto umzieht. Nein, sie sind Echtzeit-Backups, die in zwei Richtungen funktionieren und die man genau wie das Original nutzen kann. Damit kann man einen Hubzilla-Kanal hervorragend gegen pltzliche Serverschlieung absichern. Selbst wenn der Server mit dem Original offline geht, kann man die Klone weiter nutzen und einen der Klone zum neuen Original erklren. (Auch hier wieder: Mastodon und fast alles andere im Fediverse sieht die Klone als eigenstndige Konten.)
Da man auch mit einem kompletten Kanal mit allem Drum und Dran sauber umziehen kann, und zwar, ohne die alte Kopie des Kanals zurckzulassen, ist davon eigentlich nur ein Nebeneffekt.
Es gibt noch einen ganzen Haufen mehr Features. Hubzilla kann als Content Management System fungieren man kann optional darauf ganze statische Websites fahren, die formatiert werden knnen in BBcode, Markdown oder HTML. Kein Witz: Die offizielle Hubzilla-Website luft auf einem Hubzilla-Kanal. Es kann auch als Groupware-Server verwendet werden mit einem CalDAV-Kalenderserver, der das Webinterface des Event-Kalenders mitbenutzt (wobei das fr CalDAV nicht sehr gut ist, weil zu eingeschrnkt) und einem optionalen CardDAV-Adrebuchserver.
Man kann auf einem Hubzilla-Kanal auch beliebig viele Wikis haben mit jeweils beliebig vielen Seiten. Ja, Wikis. Zugegeben, die verwenden als Sprache auch entweder BBcode oder Markdown, also kein MediaWiki-Markup. Aber es gibt sie.
Hubzilla kann sich an sich schon mit dem Rest des Fediverse verbinden. Ich habe das hier gerade selbst von Hubzilla geschickt. , , , , und trotzdem knnt ihr das auf Mastodon lesen.
Allerdings ist Hubzilla die einzige Fediverse-Serveranwendung, bei der ActivityPub nicht nur optional ist, sondern fr neue Kanle standardmig abgeschaltet. , falls du den Schalter nicht gefunden hast: Drei-Punkte-Men ganz rechts auf der Navbar, "Apps", "Verfgbare Apps", "ActivityPub-Protokoll" auswhlen und "Installlieren" klicken. Erst dann kann sich dein Hubzilla-Kanal mit Mastodon & Co. verbinden.
, wenn das getan hat, kopierst du das hier: kulturkramkistehub.netzgemeinde.eu, fgst es in Mastodon bzw. in deiner Mastodon-App in die Suche ein und suchst. Idealerweise sollte s Kanal gefunden werden.
Zustzlich kann Hubzilla sich brigens optional auch mit (dem dahinsiechenden) diaspora* verbinden, man kann RSS- und Atom-Feeds abonnieren, und je nachdem, was der Admin aktiviert hat, gibt's auch noch ein paar andere Verbindungsmglichkeiten.
Ach ja, , hier sind zwei Foren-Kontaktempfehlungen fr Hubzilla: Hubzilla Support Forum und (weniger aktiv, aber deutschsprachig) Pepes Hubzilla-Sprechstunde. Tausendmal besser, als fr Hubzilla-Supportanfragen wie bei Mastodon einfach in den ther zu rufen und zu hoffen, da irgendjemand das liest.
Die eingebaute Hilfe ist brigens von Der Pepe (Hubzilla) komplett neu geschrieben worden und zu finden.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediverseMeta #Hubzilla

Dolphins In Depth: Dolphins must address trenches early in 2025 NFL draft

When Mastodon introduces groups, it had better also introduce a strikingly big "Groups" button to its Web interface and the official iOS and Android apps. And the major third-party phone apps had better follow suit as soon as possible.
Otherwise the majority of Mastodon users won't even know that the Fediverse has groups (it does right now, and they don't right now), much less that Mastodon has introduced them. And they'll go on shouting into the void like they've always done, hoping that the right people may happen upon their posts.
I mean, Mastodon has also copied Friendica's, Hubzilla's and (streams)' automatic, reader-side content warning generation into its existing filters and rolled that feature out with Mastodon 3.0 in October, 2022.
But next to nobody on Mastodon even knows that this feature exists anywhere in the Fediverse, much less on Mastodon itself. For the huge majority, putting content warnings into the summary field (of which next to nobody on Mastodon knows that it's actually a summary field) and forcing the very same content warnings on everyone in the Fediverse is without an alternative. As is demanding that the very same content warnings that one requires oneself be forced upon everyone else while oneself be spared from all other content warnings.
And, in fact, it also seems like hardly anyone on Mastodon knows that you can follow hashtags on Mastodon, just like you can follow people. There's no big honking button in front of everyone's noses for that either.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Groups #FediGroups #FediverseGroups #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta Find the latitdue and longitude of any place

/USDT :

Entry: 0.1575 - 0.1520

Leverage: 20x

Target 1: 0.1590
Target 2: 0.1606
Target 3: 0.1622
Target 4: 0.1639
Target 5: 0.1655

StopLoss: 0.1484

5 best bets for the US Masters 2025 at Augusta

I didn't add tags to your post. If I were on Friendica, I could do that. But I'm not. I added them to my own comment.
And I've added those specific tags mostly for other people to be able to filter away my posts or comments or at least have them hidden behind automatically generated reader-side content warnings. That's a feature that has been available in the Fediverse since 2010 and on Mastodon since 2022. Hubzilla, where I am, has had it since its inception which was before Mastodon was created. I'm living Hubzilla's culture here.
I always tag anything I post that exceeds 500 characters even only by a smidge #Long, #LongPost, #CWLong and #CWLongPost so that those who don't want to see my "long" posts or comments have a choice not to see them. And trust me, there are lots of people on Mastodon who want the whole Fediverse to be a purist micro-blogging platform, and who want to rid themselves of any and all content that exceeds 500 characters. I give them a chance to do so.
When I talk about image descriptions in general, I always use the tags #ImageDescription, #ImageDescriptions, #ImageDescriptionMeta and #CWImageDescriptionMeta, and when I talk about alt-text in particular, I always use the tags #AltText, #AltTextMeta and #CWAltTextMeta.
For one, #AltText, #ImageDescription and #ImageDescriptions help people find my posts and comments on the topic. If you really think that the majority of Mastodon users will take a look at the whole thread and therefore your post, then I have a bridge to sell you.
Besides, #AltTextMeta, #CWAltTextMeta, #ImageDescriptionMeta and #CWImageDescriptionMeta make it possible for them to remove my "weird" and "crude" ideas on alt-text and image descriptions which are "weird" and "crude" because they deviate from Mastodon's "standards" so much that they may be potentially disturbing.
By using these hashtags, I hurt you.
By not using these hashtags, I probably hurt hundreds or thousands of Fediverse users who have filters for one or several of these hashtags to get rid of my posts and comments. Not using these hashtags does more damage overall than using them.
If you aren't okay with that, go block me on the spot.

Todays prompt is (word or inspiration)

Make a new post including the two hashtags. Write a one-post story for the prompt.

Keep it clean!

There are no limits on previous prompts use or re-use as you like.

Have fun!

(21 Apr) Why Cameras Are Popping Up in Eldercare Facilities

Archive: ais: ia:

-industry -term-care -mexico -dakota -homes -island -dakota -new-old-age

Be aware that quotes and quote-posts are two different things, and both exist in the Fediverse. At least Friendica, Hubzilla, (streams) and Forte can generate both.
This is a quote, like in every bulletin-board forum out there:
Coming soon in #BotKit 0.2.0: Native #quote post support!

Or this, but it has to be coded manually into the comment's source code:
Coming soon in #BotKit 0.2.0: Native #quote post support!

This is a quote-post a.k.a. shared post a.k.a. quoted share:
Coming soon in 0.2.0: Native post support!
We're excited to share a preview of the upcoming quoting features in BotKit 0.2.0. This update will make it easier for your bots to engage with quoted content across the fediverse.
The quoting feature set includes:Here's a quick example of how you can use the quote detection:
bot.onQuote = async (session, quote) =>
  // The quote parameter is a Message object representing the post that quoted your bot
  await quote.reply(textThanks for quoting my post, $quote.actor!)
  
  // You can access the original quoted message
  const originalPost = quote.quoteTarget
  console.log(Original message: $originalPost.text)

And creating quote posts is just as simple:
// Quote in a new post
await session.publish(
  textI'm quoting this interesting message!,
   quoteTarget: someMessage
)
// Or quote in a reply
await message.reply(
  textInteresting point! I'm quoting another relevant post here.,
   quoteTarget: anotherMessage
)
Remember that quoting behavior may vary across different implementationssome platforms like Misskey display quotes prominently, while others like Mastodon might implement them differently.
Want to try these features right now You can install the development version from :
deno add jsr:fedify/botkit0.2.0-dev.90+d6ab4bdc
We're looking forward to seeing how you use these quoting capabilities in your bots!

Also, Friendica, Hubzilla, (streams) and Forte handle quote-posts a lot differently from Misskey and the Forkeys.
Misskey and the Forkeys do quote-posts like so:
RE: https://hollo.social/botkit/01965678-eb56-7003-9c91-07e4418bf63a
At least on Hubzilla, (streams) and Forte, a quote-post starts out like this:
share=74153074/share
Upon sending the post, this piece of BBcode is changed into a full, dumb copy of the original post, led in by a line that says who posted this first, complete with a link to the profile, and that also links to the original. The original poster is being notified about this (unless they chose not to), but if the original post is edited, the edit is not forwarded to quote-posted copies.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #Forte #Quotes #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts
Image descriptions are cool and good! Please write them, if you can! Not just for blind people they're also super helpful for if the image doesn't load (we personally have this when we're out of mobile data and limited to nigh-unusably-slow internet) and for people staring at the image going "...what am I supposed to be looking at here, what's important in this" (also me).

How about people who don't even know what it is that they're looking at Especially if they're curious about what it is
I'm asking because my original images aren't even real-life photos. Rather, they are from very obscure 3-D virtual worlds, very obscure as in only one out of at least 200,000 Fediverse users even knows the underlying technology, much less specific places there. If I posted my images without sufficient explanation and description, next to nobody would have an idea what the images show.
Don't stress about having a Bad Description, and don't stress about Describing Literally Everything less is actually /better./ Something simple like "my kitty in a basket, looking cute" is a perfect description, and way better than describing every last irrelevant detail. The irrelevant details actually make it harder to read.

Is there any hard, steadfast rule on what's relevant, and what isn't One that applies to all images out there, no matter how obscure and niche and unusual the content
Again, I post super-obscure content. Ask random people out of the blue what it looks like, and they won't know, regardless of whether they're sighted or not. They simply don't even know that it exists.
You can assume that everyone knows what a real-life cat looks like.
But, for example, I can't assume that everyone knows what my avatar looks like, also, but not only because my avatar can wear a whole assortment of different outfits.
At the same time, I can't assume that nobody wants to know what my avatar looks like. Or anything else in-world. Thus, I owe them a visual description. A sufficiently detailed one.
In fact, I can't just simply mention there being things in my images. I always have to expect there being blind or visually-impaired people asking, "Yeah, that's all fine, but what does it look like" They legitimately don't know. I mean, how should they In addition, they may ask, "And why do I even have to ask Why don't you tell me right away what it looks like, you ableist swine"
Trees are simple to describe. Buildings are a nightmare. And it gets even worse with objects that don't exist in real life. I couldn't possibly get away with mentioning that there's an OSW beacon standing somewhere. Would you know what it looks like Especially since there appear to be at least five standard types of beacon, not mentioning modified beacons or even custom builds
In fact, would you know what it is in the first place What it does What it's there for What do you think, how many people would know How many people would be completely satisfied if I only name-dropped it
In fact, the same goes for the very location. Most people won't have the slightest idea what that place is of which they see a part in my pictures. But they may want to know. But if I just name-dropped or or or , people would be about as smart as before because next to nobody has ever heard of any of these places before. (Be honest, have you) And so I have to explain what they are and where they are.
For almost two years now, I've had to describe my original images twice. First of all, there's a long, detailed description in the post text body itself (as opposed to the alt-text) I've got a character limit of over 16.7 million (!), so I've got enough space. That description also includes all explanations necessary to understand the image and its content as well as verbatim transcripts of all pieces of text within the borders of the image. It regularly reaches five-digit character counts, and it may take me multiple entire days to research for and write it.

In addition, I always distill a shorter description with no explanations for the alt-text from the long description. It usually doesn't contain any text transcripts either because there simply is no room for them. Nonetheless, it normally grows about 900 characters long. I need the other 600 characters to announce the long descriptions in the post itself so that people on Mastodon prior to 4.3 find them.

In case you say that this is way overkill: Before I've (content warning: long post, eye contact, alcohol) , my virtual world image posts looked like (content warning: eye contact, alcohol) or (content warning: long post, eye contact, alcohol) or (content warning: eye contact) . Apart from the missing full stops (and the missing content warnings), would you honestly and sincerely say the descriptions in the alt-texts are fully sufficient for everyone out there Or would you say that even they are still too long
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta


<>

(18 Apr) A Stunning Image of the Australian Desert Illuminates the Growing Problem of Satellite Pollution

Stitching together 343 distinct photos, Joshua Rozells illuminates a growing problem of satellites polluting the night sky.


Archive: ais: ia:

-rozells -exposure

If anything, the AI to describe the image should be chooseable, and the available AIs should be configurable at least for the admin. And especially, AI image description must not be mandatory and hard-coded. There must always be a way to describe an image manually, no matter how many people swear that AI is better at describing any image out there than any human.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AI #AIVsHuman #HumanVsAI Still, first of all, if I posted an image without an alt-text (which I'd never do), AltBot would have to assume full admin rights over because that's the only way for another Fediverse actor to alter the source code of my posts.
Altering the source code of the post is necessary because Hubzilla, (streams) and Forte neither have a dedicated alt-text field, nor are images file attachments there. Rather, images are embedded directly into the post, in-line, just the same way blogs handle images. And alt-text has to be woven into the image-embedding code in the post. Thus, the post itself has to be altered.
So, assuming AltBot actually manages to circumvent the two most advanced permissions systems in the Fediverse, it would have to trace back an image that it perceives as a file attachment to where exactly the embedding code for that particular image is in the post.
It would have to be able to both understand and write the specific flavour of BBcode used by Hubzilla, (streams) and Forte.
It would have to, for example, take this piece of code...
zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=800x533https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpg/zmg/zrl
...and edit it into this.
zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/b1e7bf9c-07d8-45b6-90bb-f43e27199295zmg=https://hub.netzgemeinde.eu/photo/b1e7bf9c-07d8-45b6-90bb-f43e27199295-2.jpgDigital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery./zmg/zrl

Not to mention that AltBot would require extensive detail niche knowledge about the topic covered by the image to be able to whip up the above alt-text in the first place. (By the way: The alt-text example is genuine. I've actually used it. And it's an extremely whittled-down version of the long image description of the same image in the post itself, a description which has to be the longest in the entire Fediverse.)
Ideally, AltBot would do so without flagging the post as edited.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta The main obstacle is that Mastodon has little support for titles (except for using them to show Article-type objects instead of their full content long story) whereas they're absolutely mandatory in the Threadiverse.
If you want to start new thread, this is how you must always structure your posts.
Title
< --- blank line here --- >
mention (only one Lemmy/PieFed community or /kbin/Mbin magazine, otherwise only the first one will be recognised)
< --- blank line here --- >
Post text body

Comments, on the other hand, don't need titles.
Also, prepare for people on Lemmy being very irritated about hashtags. And people on Mastodon being very irritated about what your toot looks like.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Threadiverse #Lemmy #/kbin #Mbin #PieFed #FediTips Kind of similar here, only that the extra information always goes into the post text itself. That extra information is necessary because I only ever post about extremely obscure topics, and I want people to understand my image posts without having to look anything up themselves.
Whenever I post a wholly original image, I even add two image descriptions, a "short" and purely visual one in the alt-text and an extensive one that includes explanations in the post itself.
And yes, I write my image descriptions myself by hand. I'm on a desktop computer with a hardware keyboard most of the time. Besides, AI can't nearly do what I do.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

Golf pennants victories for Waikohus Solly men at end of long and winding road

Define "similar".
As for Tumblr: For one, there's Wafrn which aims to be a direct drop-in replacement for Tumblr. Downside:
As for Facebook: Mike Macgirvin has spent the last 15 years developing about a dozen Fediverse server applications which are (also) designed to be alternatives to Facebook. Today, there are still (2010), (2012/2015), (2021) and (2024).
However, if what you're looking for is "literally Facebook without Musk and with ActivityPub", as in a 1:1 Facebook clone that looks like Facebook and feels like Facebook just like Bluesky looks and feels like early Twitter, then you're out of luck. All four are "better than Facebook" Facebook alternatives that add useful stuff on top, but that don't look and feel close enough to Facebook for nobody to have to learn something new. The closest you'll get is Friendica if the node in question has the theme installed.
Even then you'll have to "install" Friendica on your iPhone as a progressive Web app through Safari and use its own Web interface (which is mobile-compatible). There is no native app for Friendica for the iPhone in the Apple App Store. There's one in development, but it's far from complete. And while Friendica supports Mastodon apps, a Mastodon app only covers a small fraction of Friendica's features, it leaves out some features that you'll need daily (simply because Mastodon doesn't have them), and I'm not sure if there's any Mastodon app for the iPhone that works with Friendica it has officially only ever been tested with Android.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookAlternative #Tumblr #TumblrAlternative #Wafrn #Friendica #Hubzilla #Streams #(streams) #ForteI'm daily-driving Hubzilla, and I have been doing so under various independent identities since it was still fairly new (second half of the 2010s).
By default, Hubzilla doesn't look much different from what Friendica looked like in 2012 when Hubzilla started out as a Friendica fork named Red. However, very very recently, third-party themes have started emerging.
The default UI, the Redbasic theme, is quite convoluted and can be confusing. That's because work done on it over the last 13 years was almost limited to slapping more UI elements to it somewhere. Configuration is split between the Settings page in the channel menu, cogwheel icons towards the left of the navbar on some pages and even a few (partially actually essential) settings exclusive to /settings/features, a page for which there is no link on the UI anywhere (unless you have the newbie links on). And configuration is important using Hubzilla at default settings makes even less sense than using Friendica at default settings.
On top of this, Hubzilla is highly modular, similarly to Friendica. There are dozens of "apps" which the hub admin can activate or deactivate for everyone, and in addition, some "apps" are on by default on new channels (if they're on for the whole hub), and some are off. This means that some optional features are activated by turning settings on whereas others are activated by "installing" an "app" as a user.
On top of even this, one of the "apps" that are off by default is Pubcrawl, Hubzilla's ActivityPub connector. Hubzilla has to be the only Fediverse server application on which ActivityPub has to be activated manually. That's because Zot6 (Hubzilla's version of the Nomad protocol, formerly known as Zot) doesn't interact as smoothly with non-nomadic protocols as (streams)' more current version of Nomad. Back in 2015, Hubzilla was geared towards purely nomadic operation. Since then, the Fediverse has changed a lot (and not into the direction which was desired in conjunction with Hubzilla's development), but Hubzilla hasn't in this regard.
And "installing" the ActivityPub "app" is only one of the things highly recommended to do before you even only post something or connect to someone.
Even if you're used to Friendica, Hubzilla's learning curve can and probably will be staggering. That's because Hubzilla is even more complex than Friendica. It's Friendica with a content management system, a groupware server, a whole new concept of identity and the second-most powerful permissions system in the whole Fediverse.
The first huge difference between Friendica and Hubzilla: On Friendica, like almost everywhere else in the Fediverse, your account/login is your identity. On Hubzilla, your identity is independent from your account/login.
For starters, you can have multiple independent channels on one account where one channel corresponds to one Friendica account, only without its own login. You can switch back and forth between all channels on one account without logging out. Friendica, Mastodon and everything else that doesn't understand the Nomad protocol (i.e. everything that isn't Hubzilla or (streams)) understands Hubzilla's channels as separate accounts.
This is not to be confused with Friendica's multiple profiles per account. Hubzilla has multiple profiles per channel, too, which can be assigned both to privacy groups (think "lists") and individual contacts. You can have multiple identities, with multiple profiles each if so desired, on one account.
But you cannot only have multiple channels on one account on one hub. You can have the exact same channel on multiple hubs with one account each. This is called "nomadic identity", something that Bluesky claims to be working on pioneering, but that has actually been first implemented by Friendica's and Hubzilla's creator as early as 2012 as the ultimate safety net against unannounced server closure.
Nomadic identity is basically a live, hot, near-real-time backup of an entire channel with almost everything on it ("almost" because the one thing that isn't mirrored is which apps you have installed on your channel) on another server instance. And it's bidirectional. You can actually log onto your clones and use them like the main instance, e.g. if the hub with the main instance is offline. Whatever you do there will be mirrored to your main instance and your other clones if you have more than one clone. And you can declare one of your clones the new main instance and thereby demote your previous main instance to clone status.
Another difference is that permissions are everything on Hubzilla. Hubzilla has the second-most powerful permissions system in the Fediverse, only barely behind (streams) and Forte. Permissions are granted on three levels: for the whole hub, for individual contacts, per conversation.
On a hub level, there are four so-called channel roles which define what the channel generally permits: Public (social networking with a lot of permissions granted right away), Personal (social networking with fewer permissions granted), Community forum (public group) and Custom (adjust all channel-level permissions yourself, one by one).
You can grant permission for others to

You can grant these permissions to

The next level is permissions per contact. These are granted by so-called "contact roles" which contain the same permissions as the channel, but only with "yes" or "no" as the options because the contact role defines whether a contact is granted a specific permission or not. Permissions granted by the channel are automatically also granted by all contact roles and cannot be revoked, except on a channel level. Each contact is always assigned one contact role.
Lastly, you can grant permissions on a content level. For example, a new post can be public or restricted to

At least on servers that understand these permissions, all those who are permitted to see the post are also permitted to see all comments and comment themselves.
That is, optionally (that's an off-by-default app again), you can disallow comments on specific posts altogether.
For viewing files and folders in your file space, there are the permissions mentioned above which control who in general and which contacts specifically are permitted. In addition, you can define access permissions like those for posts to individual folders or files.
All this ties in with OpenWebAuth, a single sign-on system developed for Zap, a now defunct fork (of a fork) of Hubzilla, in 2018/2019 and backported to Hubzilla in 2019 or 2020. Friendica has client-side OpenWebAuth support, i.e. Friendica's logins are recognised by OpenWebAuth. Hubzilla has full support, i.e. not only are its logins recognised, but it recognises logins itself.
Speaking of the file space: It can be connected via WebDAV. As if that isn't enough, Hubzilla has two calendar systems. One is Friendica's federated event calendar. One is a CalDAV calendar server that shares the same frontend. And, as another optional app, Hubzilla even offers a CardDAV addressbook server.
As indicated above, Hubzilla has even more to offer:

As for external federation, Hubzilla is second only to Friendica itself. It does not have Bluesky integration or a WordPress cross-poster, and OStatus support was removed years ago with the release of Hubzilla 6.
How fast it is depends not so much on the software (Hubzilla requires fewer server resources per channel than Mastodon does per account, though) as it does on the underlying server (hardware, configuration, MySQL/MariaDB vs PostgreSQL etc.). Still, the Zot code from 2012 (and what evolved from it) seems to be more optimised than the DFRN code from 2010, so that Hubzilla may actually be quicker than even Friendica.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla Verstndnisfrage: Strst du dich daran, wenn jemand Mastodon selbst verwendet, um mehr als 500 Zeichen zu posten
Oder strst du dich daran, wenn du lngere Posts auf Mastodon siehst, egal, woher sie kommen
Bedenke: Das Fediverse ist nicht nur Mastodon. Das Fediverse wurde auch nicht mit Mastodon erfunden. Das Fediverse war zu keinem Zeitpunkt nur Mastodon.
Schon als Mastodon mit seinem 500-Zeichen-Limit im Januar 2016 startete, verband es sich sofort mit Friendica, einer "Besser als Facebook"-Facebook-Alternative mit vollen Blogging-Features, die seit Juli 2010 existierte, damals schon seine eigene florierende Kultur basierend auf seiner eigenen Technologie hatte und ein Limit von 200.000 Zeichen hat. Ebenso verband sich Mastodon sofort mit dem Friendica-"Nachfolger" Hubzilla von Mrz 2015, dessen Limit bei ber 16 Millionen Zeichen liegt.
Du siehst auf Mastodon also nicht nur Mastodon-Trts, sondern durchaus auch Content von anderen Plattformen und Serveranwendungen mit anderem Fokus, anderer Technologie, anderer Philosophie, anderer Kultur. Das knnen Blogposts von WordPress, WriteFreely oder Plume genauso sein wie mittellange Posts von Pleroma, Akkoma, Misskey, Iceshrimp oder Sharkey oder auch noch lngere Posts von Friendica, Hubzilla, (streams) oder Forte. Und nirgendwo wird sich jemand auf das beschrnken, was Mastodon "kann", nur weil der eigene Content vielleicht auf Mastodon landen und da die Microblogging-Puristen stren knnte.
Wenn du aber Mastodon unbedingt als puristischen reinen Microblogging-Dienst haben willst mit nie mehr als 500 Zeichen und auch sonst nichts, was Vanilla-Mastodon selbst nicht kann, dann wirst du sehr viel zu blockieren haben. Nicht nur Nutzer, sondern tausende ganze Domains.
Aber: Das Medium ist nicht Mastodon. Das Medium ist das Fediverse. Und das Fediverse ist nicht nur Mastodon, war es nie und wird es auch nie werden.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #Pleroma #Akkoma #Misskey #Iceshrimp #Sharkey #Friendica #Hubzilla #Streams #(streams) #Forte #WriteFreely #Plume #Zeichenlimit #Zeichenlimits #500Zeichen Not to mention that Tumblr, just like Facebook and every last blog out there, uses a one-post-many-comments conversation model whereas Mastodon hangs on to Twitter's loose strings of posts.
If you want that conversation model and full HTML text formatting and images embedded within the post and development being done outside the USA, your only choices is the family of "better-than-Facebook Facebook alternatives": Friendica, Hubzilla, (streams), Forte. Friendica is developed by two Germans with the code on GitHub in the USA. Hubzilla is developed by a German and a Norwegian with the code on Framagit in France. (streams) and Forte are both developed by their and Friendica's and Hubzilla's creator in Australia with the code on Codeberg in Germany.
None of them is a Facebook clone, though, and nobody should expect either to be a full-on Tumblr clone. UI and UX are a lot different. Also, all four have quite a bit of a learning curve, regardless of where you come from.
Lastly, readily available native third-party mobile apps only exist for Friendica and for Android. There's an iPhone app for Friendica in development, but it's a long way to daily-driver material. Friendica is also the only one of the bunch with the Mastodon client API, but Mastodon apps can only cover a tiny fraction of what Friendica can do, namely what Mastodon can do, too.
As for apps for the other three, no dice. There's no native mobile app even in sight, also because such an app would end up an absolute monster. And none of them supports Mastodon apps and most likely never will because the Mastodon client API covers even fewer of their features. In fact, it does not cover a lot of critical everyday features, so trying to use one of the three through a Mastodon app makes no sense whatsoever. You're better off with the Web interface either way.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Tumblr #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte I take it you're using the official Mastodon mobile app
If so, no chance. The official Mastodon mobile app seems to be hard-coded against the assumption that the whole Fediverse only consists of vanilla Mastodon with a maximum of 500 characters.
If you don't like that, try another app like Mona or IceCubes for iOS or Tusky for Android. Of course, that requires getting used to the app not having the same name as the "service".
To my best knowledge, the official Mastodon mobile app is the only Fediverse frontend that can't collapse posts. In fact, it's most likely the worst and most lack-lustre Mastodon app out there.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonApp Doch. Wenn man nmlich eben gerade keine "inhaltlich vielfltige Timeline" haben will, sondern einen Stream, in dem nur passiert, was zu den Themen des eigenen Kanals gehrt.
Der Kanal, von dem aus ich hier jetzt gerade schreibe, ist thematisch stark spezialisiert. Primrthema: speziell und virtuelle Welten im allgemeinen. Sekundrthema: gewisse Aspekte des Fediverse. Ich poste hier ber nichts anderes, und ich will hier eigentlich auch nichts anderes lesen.
Ich kann mich noch daran erinnern, als ich gerade mal mit etwa 300 Leuten verbunden war. Der weit berwiegende Teil von denen waren Mastodon-Nutzer, die mir folgten, weil sie einmal einen klugen Post oder Kommentar von mir ber das Fediverse jenseits von Mastodon gelesen hatten. Ich ging damals davon aus, da ich die Verbindung besttigen mute, damit sie mir folgen konnten.
Die Folge: Alle paar Stunden war mein Ungelesene-Mitteilungen-Zhler bei "99+". Und das allerallermeiste davon war Mll, der mich nicht im geringsten interessierte. Den interessanten Content, wegen dessen ich mich mit anderen verband, mute ich dazwischen raussuchen. Vor allem waren darunter Leute, die auch schon mal alle paar Minuten irgendwas geboostet haben. Das war also eine grandiose Zeitverschwendung.
Klar htte ich das Affinity Tool zum Einsatz bringen knnen, um Posts von denen loszuwerden, die eh nichts interessantes zu posten hatten. Ich wollte das aber eleganter und sauberer lsen. Zeitgleich kamen immer wieder neue Leute an und wollten mir folgen.
Mein erster Versuch, meinen Stream aufzurumen, war also Filtern. Whitelisten sogar. So sollte nur Content in meinen Stream kommen, der mich interessierte. Ich habe also bei haufenweise Kontakten in die jeweilige Filter-Whitelist eine ganze Reihe von Filterzeilen gecopypastet.
Das fiel mir aber auf die Fe, denn damit filterte ich Posts und Kommentare und PMs. Hubzilla kann zwar per Filtersyntax beim Filtern kontrollieren, ob es auch Kommentare und/oder PMs betreffen soll, aber nicht in Verbindung mit einer Whitelist mit mehreren Schlsselwrtern. Mich schrieb spter mal jemand in-world an wegen einer DM, die sie mir mal geschickt hatte. Die hatte ich nie bekommen. Die war im Filter hngengeblieben, weil sie keins der ntigen Schlsselwrter enthielt.
Nachdem ich eine Weile erfolglos mit den Filtern herumexperimentiert hatte, nderte ich meine Strategie.

Und auf einmal war das Postaufkommen sehr viel geringer, sehr viel angenehmer.
Zustzlich nutze ich Superblock, um Leute, deren Posts a) gern und viel geboostet und b) gern und viel kommentiert werden, komplett stummzuschalten. Damit konnte ich vermeiden, da ich morgens z. B. von einem Eugen Rochko oder einem George Takei einen Post plus mindestens 120 Kommentare im Stream hatte. Und ein paar Minuten spter gleich wieder ein paar Dutzend Kommentare. Und so weiter und so weiter. Denn was die beiden posten, interessiert mich auch nicht die Bohne. Warum soll ich mir dann tagelang durch jeweils einen ihrer Posts meine Stream mit ungelesenen Kommentaren zuspammen lassen
Inzwischen wei ich, da mir z. B. Mastodon-Nutzer keine Folgeanfragen stellen, sondern mir direktweg folgen, und zwar ohne meine Besttigung. Ich kann die Verbindung lschen, und sie knnen mir trotzdem weiter folgen. Also habe ich inzwischen angefangen, meine Verbindungsanzahl von zwischendurch ber 650 sukzessive um diejenigen zu reduzieren, die eh nicht berechtigt sind, mir Posts zu schicken. Ich schtze, am Ende werden keine 200 brig bleiben.
Gleichermaen: Wenn mir jemand von einer Mikrobloggingplattform folgen will, aber nichts Interessantes zu posten hat, dann lsche ich den Kontakt gleich wieder, statt denjenigen erstmal per Kontaktrolle stummzuschalten.
Die "Alles als gelesen markieren"-Funktion nutze ich nur, wenn der Zhler bzw. die Liste ungelesener Beitrge wieder etwas enthlt, was ich nicht aufrufen kann, um dann den Zhler wieder zu nullen.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla Das Problem der Reichweite auf Mastodon, das ja auch vernnftigen themenbezogenen Diskussionen im Wege steht, hat eigentlich zwei Ebenen.
Zum einen haben viele immer noch "Twitter im Kopf" und nutzen Mastodon wie Twitter. Das heit, sie trten einfach drauflos ohne Hashtags und ohne gar nix, weil sie zu sehr daran gewhnt sind, da irgendein obskurer Algorithmus ihre Trts schon an die richtigen Adressaten liefert. Oder sie hoffen, da irgendjemand zufllig in der lokalen oder gar in irgendeiner fderierten Timeline ber ihre Trts stolpert.
Einige versuchen noch an Reichweite zu kommen, indem sie hunderten oder tausenden Leuten folgen in der Hoffnung, da die ihnen zurckfolgen. Nebeneffekt ist, da sie nur einen winzigen Bruchteil dessen, was ihnen in die Timelines gesplt wird, lesen, weil es einfach viel zuviel wird, wenn man ber 3000 Akteuren folgt ohne jegliche Filterung.
Ein bichen kann man das mit Hashtags beheben. Aber zum anderen ist auch Trten mit Hashtags ein "Rufen in den ther", dieses Mal in der Hoffnung, da zeitnah die richtigen Leute zufllig nach den richtigen Hashtags suchen. Oder, wenn man schon ein bichen mehr Ahnung von Mastodon hat, in der Hoffnung, da genug Leute den Hashtags folgen, die man gesetzt hat. Die allerallermeisten Mastodon-Nutzer wissen aber noch nicht mal, da man auf Mastodon auch Hashtags folgen kann, also macht das kaum einer.
Noch dazu ist das Prinzip sowieso halb kaputt, weil es Leute gibt, die gewisse populre Hashtags in alle Trts einbauen, um ihre Reichweite zu erhhen, auch wenn es in den Trts gar nicht um das geht, wofr die Hashtags stehen.
Leider ist aus der Sicht von Leuten, die nur Mastodon kennen, damit das Optimum schon erreicht. Fr die einen ist es das Gelbe vom Ei, weil sie nichts besseres kennen und sich nichts besseres vorstellen knnen. Fr die anderen taugt auch das nichts, und weil sie nichts anderes kennen, taugt das ganze Fediverse nichts.
Zwei wichtige Dinge fehlen Mastodon. Das eine ist native Untersttzung fr Gruppenakteure. Mastodon hat keine Gruppenfunktion. Im Grunde versteht Mastodon nicht mal, was ein Gruppenakteur ist, und kann daher auch nichts damit anfangen. Ganz zu schweigen davon, da Mastodon keine eigenen Bedienelemente fr Gruppen hat. Man kann an sich schon Gruppen im Fediverse beitreten, aber deren Handhabung ist alles andere als intuitiv, zumal Mastodon ja auch kein Titelfeld hat. Und weil es keine dedizierten Bedienelemente fr Gruppen gibt, drften mehr als 90% der Mastodon-Nutzer nicht mal wissen, da es im Fediverse berhaupt Gruppen gibt, geschweige denn, da Mastodon an sich mit denen mehr oder weniger interagieren kann.
Das andere, und das ist eigentlich Voraussetzung fr das vernnftige Funktionieren von Gruppen und Diskussionen in Gruppen, sind Konversationen. Auch wenn Mastodon-Fans das vehementestens bestreiten: Mastodon kann keine Konversationen. Mit "Konversationen knnen" meine ich zwei Dinge. Zum einen, immer und sofort den ganzen Thread anzuzeigen wie hier bei mir auf Hubzilla. Statt dessen bekommt man standardmig nur Einzelbeitrge und darf sich den ganzen Thread mhsam zusammensuchen. Zum anderen, allen Teilnehmern einer Konversation auf einen Schlag antworten zu knnen, ohne sie erwhnen zu mssen. Auch das ist anderswo im Fediverse schon lange der Standard.
Unterm Strich werden in Mastodon vielfach Erwartungen gesteckt, die Mastodon gar nicht erfllen kann, weil es als Twitter-Klon dafr gar nicht konzipiert ist.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #Konversationen #Gruppen Gut, da ich den Hubzilla-Hashtag-Feed abonniert und das hier gefunden habe. Da kann ich gleich mal ein bichen "druckbetanken". Denn auf Hubzilla ist alles anders als auf Mastodon, sogar und ganz besonders der Einstieg.
Der Hubzilla-Guru vor allem im deutschsprachigen Fediverse ist Der Pepe (Hubzilla) . Der betreibt die und Pepes Hubzilla-Sprechstunde. Seine komplett neu geschriebene Hubzilla-Hilfe scheint im Moment offline zu sein.
Lesenswert in der KnowledgeDB sind am Anfang auf jeden Fall die Eintrge und .
Sehr viel aktiver, wenn Support ntig ist, ist das englischsprachige Hubzilla Support Forum, wo nicht nur Admins mitlesen, sondern auch beide Entwickler. Bei den Supportforen zeigt sich wirklich, wie viel effizienter eine Gruppenfunktion ist als einfach "in den ther" zu rufen und zu hoffen, da irgendjemand das zufllig liest, der helfen kann. Fr die Handhabung von Foren gibt's , bevor du versuchst, das wie auf Mastodon anzugehen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #HubzillaAnfnger #FediTips

Buy /USDT

Entry Zone: 0.1552 - 0.1521

Target: 0.1568 - 0.1583 - 0.1599 - 0.1614 - 0.1630 - 0.1645

StopLoss: 0.1485

Leverage 20x


<>

Rory McIlroys daughter steals the show with long putt ahead of Masters s

Tiger Woods Reveals Long Iron Secrets: Pro Golfers Windy Day Strategy!


Last updated: 2025-04-27






Affiliates Program privacy policy