Wow, from the year 2025: use for scripts! Apparently, typing a few extra characters will save the world from and mayhem. How did we ever survive without this wisdom
Use Long Options in Scripts
First of all, "image description" and "alt-text" don't mean the same thing.
Alt-text is what's added directly to the image. It's what screen readers used by blind or visually-impaired people read out loud as they can't "read out loud" an image. It's what people see instead of the image if the image doesn't show for them (text-based client, too slow Internet connection, whatever).
Alt-text should never convey more information than the image which it is a replacement for.
An image description that goes into the post itself is not alt-text.
I don't see any rule or part of the "Fediquette" or "Mastodon culture" that speaks against adding that additional information to a reply.
Whether it works or not depends on whether your customers accept it or not. I guess that 99% of your aspiring customers in the Fediverse will be on Mastodon, only see your start post and not be bothered to check the replies. So my suggestion is to leave room in the original post for tellling your customers that prices can be found in a reply to that post.
But seeing as this will happen to you a lot, it may be worth looking for someplace that offers you more than 500 characters:
- a Mastodon instance with a raised character limit
- Pleroma (5,000 characters by default, configurable by the admin)
- Akkoma (5,000 characters by default, configurable by the admin)
- Misskey (3,000 characters, hard-coded just steer clear of misskey.io)
- the various forks of Misskey and forks of their forks like Iceshrimp or Sharkey (thousands of characters by default, configurable by the admin)
If you need a five-digit character count, the best you can do requires basically re-learning the Fediverse, mastering a significantly steeper learning curve and very likely abandoning dedicated apps. Here we're talking about Mike Macgirvin's creations from Friendica (200,000 characters) to Hubzilla (probably even higher) to (streams) and Forte (over 24,000,000 characters).
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Pleroma #
Akkoma #
Misskey #
Forkey #
Forkeys #
Iceshrimp #
Sharkey #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
CharacterLimit #
CharacterLimits #
AltText #
AltTextMeta #
CWAltTextMeta Long The only talk about a Discord "alternative" in the Fediverse comes from people who want 1:1 clones of all kinds of commercial stuff with an absolutely identical UX, but free and open-source and decentralised with ActivityPub.
Otherwise, for just simply chatting, including multi-user chatrooms, there are Matrix (iOS/Android: Element) and XMPP (iOS: Monal IM, Android: Conversations). They are not part of the Fediverse, but they are free, open-source and decentralised. And they are alternatives to iMessage, Telegram and WhatsApp as well.
For discussion groups/forums, and very much in the Fediverse as in connected Mastodon, there are
- Lemmy (Reddit clone)
- Mbin (like Reddit, but better)
- PieFed (like Reddit, but better)
- Friendica (like Facebook, but better and more powerful)
- Hubzilla (like Facebook, but much better and much, much more powerful)
- (streams) (like Facebook, but much better and more powerful)
- Forte (like Facebook, but much better and more powerful)
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Discord #
DiscordAlternative #
XMPP #
Jabber #
Matrix #
Groups #
Lemmy #
Mbin #
PieFed #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte If the prices can be read in the image, you should add them to the alt-text. A price tag is text, and text must be transcribed.
If the prices are not in the image, they go into the post text. If you only have 500 characters, make room for them. But do
not only make them available in the alt-text.
Not everyone can access alt-text. There are people with physical disabilities who cannot open an alt-text. Information that is only available in the alt-text, but neither in the post text nor in the image itself, is inaccessible and lost to them. This means that information must be in the image
and the alt-text or in the post text, but never only in the alt-text.
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta Why Swinging TOO Long is DESTROYING Your Golf Swing
Hans van Zijst The Comment Control app on (streams) and Forte lets you
- disallow comments on a specific post
- limit comments on a specific post to only your approved connections
- allow comments on a specific post only until a certain date and time in the future
In addition, even without that app, you can generally limit commenting permissions to
- everyone in the Fediverse
- only your approved connections
- only you yourself plus connections whom you specifically give that permission by connection settings/permission role (for those who don't know Hubzilla and its descendants, this means that you can allow some of your mutual followers/followed to reply to you and disallow it for all your other mutual followers/followed while those who follow you without you following them back are not allowed to reply)
You can define a number of days for which people can comment on your posts after sending them.
And you still have Hubzilla's option to "moderate" comments that are, technically speaking, not allowed. (This means that you and only you see them at first. You have two buttons under them. One is for accepting them. In this case, you officially add them to the conversation, and your Friendica, Hubzilla, (streams) and Forte connections will fetch it from your channel. The other one is for rejecting them which also deletes them.)
I don't think that any of this has any influence on whether someone can quote-post ("share") any of your posts or comments. That is, quote-posts are only allowed in public threads anyway. And if there was a permission for quote-posting, it would be defined by the start post for the whole thread because individual comments cannot have individual permissions.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
ReplyControls #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate #
Hubzilla #
Streams #
(streams) #
Forte #
Security #
FediverseSecurity #
PermissionsIntroducing Simon Tathams Puzzles & Tips On Dominosa
I've brought up Simon Tatham's Puzzle Collection here before. It was then, and still is now, one of the great wonders of the World Wide Web, a completely, utterly free, in both beer and libre, collection of randomly-generated puzzles of 40 different
Read The Best 3 S&P 500 Index Funds for 2025: A Complete Analysis by Albert Tan on Medium:
-term investing, &p 500 ETFs, -investing style, creation, planning
That's not what I asked. So if you're not going to answer the question, we'll just go with: "assuming everyone takes one shot."
Lil Bit Sexy Booty
The surprisingly connected origins of "Lent" and "long".
This may come as a surprise, but: is not an abstract concept or a science-fiction idea for the Fediverse.
It is reality. It exists. Right now. In stable, daily-driver software that's federated with Mastodon. And it has been for over a decade.
I'm literally replying to you here from a nomadic channel that simultaneously exists on two servers.
Nomadic identity was invented by
Mike Macgirvin (formerly American software developer of about half a century who has been living in rural Australia for decades now) in 2011 and first implemented in 2012. Almost four years before Mastodon was first launched.
In 2010, he had invented the Facebook alternative , originally named Mistpark and based on his own DFRN protocol.
Over the months, he witnessed lots of privately operated public Friendica nodes shut down with or without an announcement and the users on these nodes lose everything. He added the possibility to export and import Friendica accounts. But that would only help if a permanent shutdown was announced. It did not protect you against shutdowns out of the blue.
There was only one solution to this problem. And that was for someone's identity to not be bound to one server, but to exist on multiple servers simultaneously. The whole thing with everything that's attached to it. Name, settings, connections, posts, files in the file storage etc. etc., everything.
So in 2011, Mike designed a whole new protocol named Zot around this brand-new idea of what he called "nomadic identity" back then already.
In 2012, Mike forked Friendica into something called Red, later the Red Matrix, and rebuilt the whole thing from the ground up against Zot. Red was the first nomadic social networking software in the world, almost four years before Mastodon.
In 2015, ten months before Mastodon was first released, the Red Matrix became , the Fediverse's ultimate Swiss army knife.
I am on Hubzilla myself. is constantly being mirrored between its main instance on and its clone on . Anything that happens on the main instance is backed up on the clone. I can also log into the clone and use that, and whatever happens there is backed up on the main instance.
could go down, temporarily, permanently, doesn't matter I still have my channel, namely the clone. And I can declare the clone my new main instance.
Well, Mike didn't stop at Hubzilla and its original version of the Zot protocol. He wanted to refine it and advance it, but in ways that wouldn't be possible on daily-driver software.
Zot went through several upgrades: Zot6 in 2018 (backported to Hubzilla in 2020, along with OpenWebAuth magic single sign-on). Zot8 in 2020. Zot11 in 2021 which had become incompatible with Zot6 and therefore was renamed to Nomad. Today's Nomad would be Zot12.
Also, in order to advance and test Zot, Mike created a whole bunch of forks and forks of forks. Osada and Zap for Zot6 in 2018, followed by another short-lived Osada in 2019. A third Osada, Mistpark 2020 (a.k.a. Misty) and Redmatrix 2020 in 2020 for Zot8. Roadhouse for
Zot11 Nomad in 2021. All Osadas, Zap, Misty, Redmatrix 2020 and Roadhouse were discontinued on New Year's Eve of 2022.
The most recent software based on Nomad is from October, 2021. It can be found in . It is officially and intentionally nameless and brandless, it has next to nodeinfo code that could submit statistics, and it is intentionally released into the public domain. The community named it after the code repository.
I also have two (streams) channels, one of which is cloned so far.
The newest thing, and that's what the Friendica and Hubzilla veteran
Tim Schlotfeldt referred to, is nomadic identity using nothing but ActivityPub, no longer relying on a special protocol.
This was not Mike Macgirvin's idea. This came from , the creator and developer of the microblogging server application . He wanted to make Mitra nomadic, make it resilient against server shutdown. But he didn't want to port it to Nomad. He wanted to achieve it with nothing but ActivityPub.
So he hit up Mike. The two came to the conclusion: This is actually possible. And they began to work on it. Amongst the results were several FEPs coined by silverpill.
This time, Mike did not create another fork to develop nomadic identity via ActivityPub. He did it all on the
nomadic branch of the streams repository while silverpill did his part on a special development branch of Mitra.
In mid-2024, after enough sparring between (streams) instances, between Mitra instances and between (streams) and Mitra, Mike was confident enough that his implementation of support of nomadic identity via ActivityPub was stable enough. He merged the
nomadic branch into the
dev branch which ended up being merged into the stable
release branch in summer.
Now, at this point, (streams) didn't use ActivityPub for nomadic identity. It still used the Nomad protocol for everything first and foremost, including cloning. But it understood nomadic identity via ActivityPub as implemented on experimental Mitra.
However, while it worked under lab conditions, it blew up under real-life conditions. At this point, (streams) had to handle so many different identities that it confused them, and it couldn't federate with
anything yet.
In mid-August, while trying to fix the problem, Mike eventually forked the streams repository into . It got a name again, it got a brand identity again, it got its nodeinfo back, it was put under the MIT license again.
But most importantly: Any and all support for Nomad was ripped out, also to get rid of a whole number of IDs, namely those for Nomad-actually-Zot12 and for Hubzilla's Nomad-actually-Zot6. Forte only uses ActivityPub for everything. And so, Forte also had to fully rely on ActivityPub for nomadic identity, cloning and syncing.
For almost seven months, Forte was considered experimental and unstable. For most of the time, the only existing servers were Mike's.
But on March 12th, 2025, , the first official stable release of Forte. This is what Tim wrote about. Because this actually made it into Fediverse-wide news.
Not because it's nomadic. Nomadic identity has been daily-driven for over a decade now.
But because it uses ActivityPub for nomadic identity. Which means that you can theoretically make any kinds of Fediverse software nomadic now, all without porting it to the Nomad protocol first.
For the future, Mike and silverpill envision a Fediverse in which one can clone between different server applications. A Fediverse in which one can have one and the same identity cloned across multiple servers of Mastodon, Pixelfed, PeerTube, Mitra, Forte, Mobilizon, Lemmy, BookWyrm etc., all with the same name, all with the same content and settings (as far as the software allows you will certainly not be able to clone your PeerTube videos to Mastodon and Lemmy).
Even if you don't intend to clone, it will make moving instances and even moving from one software to another
dramatically easier.
If you're concerned about your privacy, let me tell you this:
Hubzilla's privacy, security and permissions system is unparalleled in the Fediverse. Except for that on (streams) and Forte which is another notch better.
I can define who can see my profile (my default, public profile on Hubzilla where each channel can have multiple profiles).
I can define who can see my stream and my posts when looking at my channel.
I can define who can see my connections (Hubzilla, (streams) and Forte don't distinguish between follower and followed they aren't Twitter clones).
I can define who can look into my file space (individual permission settings per folder and per file notwithstanding).
I can define who can see my webpages on Hubzilla (if I have any).
I can define who can see my wikis on Hubzilla ().
On Hubzilla, I can define
individually for any of these whether it's
- everyone on the Internet
- everyone with a recognisable Fediverse account
- everyone on Hubzilla (maybe also on (streams) anyone using ActivityPub is definitely excluded here)
- everyone on the same server as myself (AFAIK, only main instances of channels count here, clones don't)
- unapproved (= followers) as well as approved (= mutual) connections
- confirmed connections
- those of my confirmed connections whom I explicitly grant that permission by contact role
- only myself
. And they all have seven or eight permission levels (depending on whether the general non-Fediverse public can be given permission).
On (streams) and Forte, I can define whether things are allowed for
- everyone on the Internet (where applicable)
- everyone with a recognisable Fediverse account
- all my approved connections
- only me myself plus those whom I explicitly grant that permission in the connection settings
Yes, connection settings. Hubzilla, (streams) and Forte give you various ways of configuring individual connections, much unlike Mastodon. This includes what any individual connection is allowed to do.
Hubzilla uses so-called "contact roles" for that, presets with a whopping 17 permissions to grant or deny for any one individual connection. That is, what the channel generally allows, a contact role can't forbid.
(streams) and Forte still have 15 permissions per contact, but they lack some features which Hubzilla has permissions for. These permissions can be set individually for each connection, or you can define permission roles that cover all 15 permissions to make things easier.
Okay, how about posting in public vs in private And when I say "private", I
mean "private". It's "private messages" on Hubzilla, (streams) and Forte, not "direct messages".
Hubzilla, (streams) and Forte let you post
- in public
- only to yourself
- only to your connections ((streams) and Forte only Hubzilla requires a privacy group with all your connections in it for this)
- to all members of one specific privacy group (Hubzilla)/access list ((streams), Forte) that's like being able to only post to those on one specific list on Mastodon
- to everyone to whom one specific non-default profile is assigned (Hubzilla only)
- to a specific group/forum (I'll get back to that later)
- to a custom one-by-one selection of connections of yours
Now, let's assume I have a privacy group with Alice, Bob and Carol in it. I send a new post to only this privacy group. This means:
- Only Alice, Bob and Carol can see the post and the conversation.
- Alice can reply to me, Bob and Carol.
- Bob can reply to me, Alice and Carol.
- Carol can reply to me, Alice and Bob.
- Nobody else can see the post. Not even by searching for it. Not by hashtag either. Not at all.
- Nobody else can see any of the comments.
- Nobody else can comment.
If one of them was on Mastodon, they'd see my post as a DM, by the way, and they could only reply to me. But that's Mastodon's limitation because it understands neither threaded conversations nor permissions.
Or how about reply control This is something that many Mastodon users have been craving for quite a while now. Hubzilla, (streams) and Forte have them. Right now. And they work. They have since 2012.
Hubzilla optionally lets me disallow comments on either of my posts. Users on Hubzilla, (streams) and Forte won't even be able to comment they won't have the UI elements to do so. Everyone else is able to comment locally. But that comment will never end up on my channel. It will never officially be added to the conversation. And at least users on Friendica, Hubzilla, (streams) and Forte will never fetch that comment from my channel as part of the conversation, i.e. never at all.
(streams) and Forte can go even further with all available options. They can disallow comments like Hubzilla. But in addition, they can allow only the members of one particular access list to comment, regardless of who can see the post/the conversation. On top of that, comments can be closed at a pre-defined point in the future. And then you even have a channel-wide setting for how long people can comment on your posts.
Oh, and there's even a setting for who is generally permitted to comment on your posts. And you can additionally allow specific connections of yours to comment on your posts.
Lastly, I've already mentioned groups/forums. Like, you know, Web forums or Facebook groups or subreddits or whatever. Like Guppe Groups on a mountain of coke and with moderation and permission control and optionally private.
Hubzilla has them, and it has inherited them from Friendica. (streams) has them. Forte has them. They're basically channels like social networking channels, but with some extra features. This includes that everything that's send to a group/forum as what amounts to a PM is automatically forwarded to all other members.
On Hubzilla, a forum can be gradually made private by denying permission to see certain elements to everyone but its own members (= connections): the profile, the members, what's going on in it. Depending on what you want or do not want people to see.
On (streams) and Forte, you have four types of forums:
- public, and members can upload images and other files to the forum channel
- public, but members cannot upload images and other files to the forum channel
- like above, but additionally, posts and comments from new members must be manually approved by the admin(s) until their connections are configured to make them full members
- private, non-members can't see the profile, non-members can't see the connections, non-members can't see what's going on in it, but members can upload images and other files to the forum channel
In addition, on all three, a group/forum channel can choose to hide itself from directories. This is always an extra option that's independent from public/private.
What we have here is the most secure and most private Fediverse software of all.
And, once again, at its core, this is technology from 2012. It pre-dates Mastodon by almost four years.
Finally, if you want to know how Hubzilla and (streams) compare to Mastodon:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Mitra #
Friendica #
Hubzilla #
Streams #
(streams) #
Forte #
ActivityPub #
Zot #
Zot6 #
Zot8 #
Nomad #
NomadicIdentity #
Security #
FediverseSecurity #
Privacy #
FediversePrivacy #
Permissions As a user, () and ().
Why, you ask
tldr: Both Hubzilla and (streams) blow Mastodon out of the water big time in every way possibly conceivable.
- Modular architecture. Features (so-called "apps") can be activated and deactivated server-wide by the admin and then activated and deactivated on individual channels by the users. Third-party app and theme repositories can be added to servers. More and more third-party themes are becoming available for Hubzilla which actually change the layout of the UI. (streams) already has two themes to choose from.
- . Basically bidirectional, near-real-time, live, hot backups of your channels on another server, so-called clones. And the clones can be used just the same as the main instances of my channels. One server shuts down, I lose nothing, I've got at least one clone.
- Channels. One account, one login, multiple fully independent identities.
- Full support for discussion groups/forums, both public and private, both visible in and hidden from directories.
- Full support for threaded conversations by means of .
On Mastodon, a conversation is loosely strung together from posts and more posts. And you're mostly shown piecemeal of single posts. All you ever see is posts that mention you and posts from those whom you follow.
On Hubzilla and (streams), a conversation is the same as on Facebook and Tumblr and every blog out there: one post, any number of comments that totally aren't posts. And you're always shown entire threads with the start post and all comments (unless blocking is in the way). Everyone sees everyone else's comments, always within the context of the conversation. - Mastodon: doomscrolling until you want no more, or until you've got no more time. What you don't scroll down to will remain unread forever. No alternative.
Hubzilla and (streams): unread messages counter plus unread messages list. Click one message on the list, and the whole thread around that message will be displayed, and only that thread, and all unread messages in that thread will be marked read. - No character limit to speak of.
Mastodon: 500 characters, chosen arbitrarily.
(streams): over 24,000,000 characters, limited by the database field size. - Text formatting. Just about all of it. With BBcode on Hubzilla and with BBcode, Markdown and HTML on (streams).
- Spoiler tags. In addition to a summary (which Mastodon misuses for CWs).
- Quotes.
- Quote-posts. (Yes, that's something else than quotes. And yes, Hubzilla and (streams) can quote-post Mastodon toots right now with no problems.)
- Being able to embed images within posts. Not as file attachments, but in-line, right between paragraphs, with text above and more text below. You know, like on a blog.
- Unlimited number of images per post.
- Unlimited number of options per poll.
- The most advanced and fine-grained permissions systems in the whole Fediverse. Well over a dozen individual permissions on up to three levels: for the whole channel, for individual connections, per post/thread. Including reply controls which are even more advanced on (streams) than on Hubzilla.
- Private messages, not direct messages.
- Being able to post only to one specific what-amounts-to-a-list-on-Mastodon-but-on-coke-and-roids. Nobody else can see the post. Nobody else can see the comments thread. And nobody else can comment.
- Regular expressions in filters.
- (Optional on Hubzilla) Individual filters per connection, one whitelist, one blacklist.
- ((streams) only Hubzilla needs filter syntax for this) Declutter your stream by choosing to block boosts either for your whole channel or from individual connections.
- (Optional) Separate text filter that automatically hides posts behind content warnings generated reader-side, easy to configure with only one list of keywords (which supports regular expressions at least on (streams))
- (Optional) Friend zoom/affinity slider that lets you filter your stream by how "close" you are to certain connections (all the way to the left: only you all the way to the right: everyone).
- (Hubzilla only) Connect to diaspora* users.
- (Hubzilla only) Subscribe to RSS and Atom feeds.
- Integrated cloud file space with built-in file manager, permissions management and WebDAV connectivity.
- Integrated event calendar.
- Integrated CalDAV calendar server (which uses the event calendar UI on Hubzilla).
- (Optional on Hubzilla) Integrated CardDAV addressbook server.
- (Hubzilla only optional) Post long-form, formatted, non-federating articles.
- (Hubzilla only optional) Make long-form, formatted, non-federating planning cards.
- (Hubzilla only optional) Built-in wiki engine for multiple wikis per channel with multiple pages each.
- (Hubzilla only optional) Add basic webpages to your channel.
By the way, Hubzilla is older than Mastodon. And Hubzilla even supported ActivityPub before Mastodon.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Hubzilla #
Streams #
(streams) #
NomadicIdentity #
Permissions #
Conversations #
ConversationContainers Have you noticed that there are links in my comments
If it has a different colour from the rest of the content, it's a hyperlink. You're probably used to all hyperlinks always being URLs in plain sight. But , where I am, can not only render, but also generate embedded links where the URL is concealed beneath some other text like on websites and in good blog posts. Mastodon can only show them, but not make them.
All links in my post contain actual in-world pictures. You can't see them immediately. I had to put them all behind summaries plus content warnings because the posts are all extremely long, and Mastodon users may be very sensitive about anything that's longer than 500 characters.
For example:
- . If you're on a phone app, your Web browser will open. I can't help that.
- Tap "View article". The post will unfold from the summary and content warning.
- Scroll down. You'll see:
- the actual post
- the image with alt-text, embedded in the post in-between paragraphs
- over 60,000 characters of long image description
If you
absolutely have to see it in your Mastodon app, search for the hashtag
#UniversalCampus
.
Or:
- . If you're on a phone app, your Web browser will open. I can't help that.
- Tap "View article". The post will unfold from the summary and content warning.
- Scroll down. You'll see:
- the actual post
- the image with alt-text, embedded in the post in-between paragraphs
- over 25,000 characters of long image description
This post is not available on your Mastodon instance, so no chance for you to see it in your Mastodon app. Sorry.
If I were to include images right into this comment, I'd have to add a full set of image descriptions to each image.
I do not have any pictures of halfway realistic buildings at hand. I couldn't post them in the Fediverse anyway. I can't properly describe them, so I can't post them, so it isn't even worth creating the images in the first place.
Beyond my own images, I can recommend two blogs to you: by Thirza Ember a.k.a. and by .
If you want something more artsy, check out the and groups as well as the on Flickr.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Hubzilla #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds I don't even have an app.
As I've said, I post my images on now. There are no desktop or mobile apps for (streams). It doesn't work with Mastodon apps, it never will, and that wouldn't even make sense because they're way too different, and Mastodon apps lack UI elements for critical everyday features on (streams).
In fact, I use (streams) and Hubzilla, to which the same applies, via the built-in Web interfaces in a standard Web browser on a desktop computer running Debian GNU/Linux.
When I scroll an image into such a position that I can get as much alt-text onto the screen as possible when hovering the mouse cursor over it, I may be able to get some 2,800 characters. Something between 3,000 and 3,500 if I go full-screen. But the alt-text pop-up is entirely
below the mouse cursor instead of underneath it. The scroll wheel scrolls the Hubzilla or (streams) UI. There are no scroll bars on the alt-text pop-up. And I can't move the mouse cursor over the alt-text pop-up. Moving the mouse will close the pop-up instead and re-open it below where the mouse cursor is then.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
AltText #
AltTextMeta #
CWAltTextMeta Technically speaking, I've got over 24,000,000 characters for posts and the same over 24,000,000 characters for all alt-texts in a post combined. (if I post any at all), alt-text is not a separate data field but woven into the image embedding code.
Too long alt-text still won't work. The UI can only show so much alt-text at once, and it can always only show the beginning. You can't scroll through alt-text trying it will close the alt-text pop-up.
Besides, alt-text is most important on Mastodon anyway. And as I've already said, Mastodon and its forks (Glitch, Hometown, Ecko etc. etc.) as well as Misskey and its forks (Calckey, Firefish, Iceshrimp, Sharkey, CherryPick, Catodon etc. etc.) all cut alt-texts from outside off at the 1,500-character mark and throw the excess characters away.
In my posts, I can go all out. But that leads to extremely long posts. I had before I learned that people do actually prefer externally linked explanations over posts with five-digit character counts due to the many long explanations. And that's without visual descriptions.
On my channel for original virtual world images, I've only got . One image is a fairly simple avatar portrait with hardly any surroundings, the other one is a bit more complex. Altogether, the two long descriptions still exceed 20,000 characters, explanations and text transcripts included.
It could be worse. , but it's complex enough for a 60,000-character description.
In , I've managed to describe one single object in the image with over 3,000 characters and then explain it with another more than 2,500 characters. And that explanation still depends on the explanations earlier in the image description.
This is what happens when the topic is too obscure.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta (berflssige Details auf der einen, fehlende wichtige Info auf der anderen Seite)
Im Endeffekt ist das Beschreiben von Bildern also eine Gratwanderung, um nicht Hochseilakt zu sagen, wo man exakt das Optimum finden mu. Minimal darunter oder darber ist schon sanktionierungswrdig.
Und kopiert es dorthin wo es hingehrt, nmlich in die Medienbeschreibung direkt am Medium.
Damit wre also auch meine Vorgehensweise "illegal": relativ kurze, aber einigermaen detaillierte Beschreibung im Alt-Text plus zustzlich lange, hochdetaillierte Beschreibung inklusive aller notwendigen Erklrungen und inklusive Transkripten aller Texte innerhalb der Grenzen des Bildes im Post selbst (kein erwhnenswertes Zeichenlimit hier). Genau das sehe ich bei meinen eigenen Bildern aber als notwendig an.
Das Problem ist hier nur: Zumindest Erklrungen gehren niemals in den Alt-Text. Manche Menschen haben krperliche Behinderungen, die es ihnen unmglich machen, Alt-Texte aufzurufen. Wenn Informationen nur im Alt-Text zu finden sind und weder im Post noch im Bild, dann sind diese Informationen fr sie verloren.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
AltText #
AltTextMeta #
CWAltTextMeta #
Bildbeschreibung #
Bildbeschreibungen #
BildbeschreibungenMeta #
CWBildbeschreibungenMeta I always explain my image posts extensively because I know they always need extensive explanations, being about very obscure topics and such.
But I don't do so in the alt-text. You should never explain anything in the alt-text. Not everyone can access alt-text. Besides, I'd quickly exceed 1,500 characters which would cause Mastodon, Misskey and their forks to cut my alt-texts off.
Instead, my explanations go into the posts themselves which are almost unlimited. In the case of my original images, the explanations are part of a second, much longer and much more detailed image description in the post.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta It depends.
My original images, rare as they are, are even more niche than 's, namely renderings from extremely obscure 3-D virtual worlds. This is something that maybe one out of 200,000 Fediverse users "has a basic understanding of". The other 199,999 need explanations.
I've long since decided how much detail is relevant, based on who may come across my images, and what they may be interested in. As I don't limit my target audience although I could, I write my image descriptions for random strangers who stumble upon a post of mine on some federated timeline. Considering the topic, they might be interested in
everything in the image, regardless of context. And yes, at the same time, they may not be fully sighted.
And so I go to such detail that I need two image descriptions. A "short" and purely visual description in the alt-text (which still tends to grow to 1,500 characters, complete with the note where a longer description can be found), and a long, detailed description with all necessary explanations and all text transcripts in the post itself (I don't have any character limits to worry about).
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMetaNew entry of AI-generated and added to our :
'
New entry of AI-generated and added to our :
Zum Glck ist das in unseren Sprechstunden nicht so. Aber die beiden Orgas betreiben auch ihren eigenen Hubzilla-Hub, die Regulars sind zum groen Teil woanders als auf Mastodon, und es gibt im allgemeinen jedes Mal einen Vortrag ber eine Fediverse-Serveranwendung oder eine Gruppe davon.
Was es durchaus mal gibt, sind Neulinge, die ganz verdutzt feststellen, da es im Fediverse auch noch was anderes gibt als Mastodon. Aber weder dominieren die, noch betreiben die das Ganze.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon #
Hubzilla #
FediverseSprechstunde Und vor allem dann auch noch diese "Weisheit" mit Zhnen und Klauen zu verteidigen.
Die allermeisten Nutzer im Fediverse kennen in der Praxis nur Mastodon. Sie kennen das ganze Fediverse nur aus Mastodon-Sicht und durch die Mastodon-Brille. Fr sie sind Sachen vllig normal und legitim wie,
- "Mastodon" zu sagen, wenn man das ganze Netzwerk meint
- "Fediverse" zu sagen, wenn man nur die Serveranwendung Mastodon bzw. deren Instanzen meint
- Leuten auerhalb des Fediverse nur von Mastodon zu erzhlen und entweder das Fediverse zu verschweigen oder direktweg wortwrtlich zu behaupten, das Fediverse bestnde nur aus Mastodon
- zustzliche Onlinedienste nur und ausschlielich auf Mastodon auszulegen und zum gesamten restlichen Fediverse inkompatibel zu machen, dann aber womglich trotzdem "Fediverse" oder "Fedi" in den Namen einzubauen
- zustzliche Onlinedienste zwar generell frs ganze Fediverse oder groe Teile davon brauchbar zu machen, aber nur "Mastodon" oder "Masto" in den Namen einzubauen
- zustzliche Onlinedienste frs Fediverse von vornherein nur fr Mastodon zu bauen, auch wenn sie allen nutzen knnten
- Mastodon als alleinigen Goldstandard im Fediverse und Mastab fr alle anderen Fediverse-Serveranwendungen darzustellen
- sogar Unterschiede, die andere Fediverse-Serveranwendungen zu Mastodon haben, als Bugs oder Designfehler zu erachten, die abgestellt gehren (auer die jeweilige Serveranwendung hat in der Verwendung null berschneidung mit Mastodon, und dann sehen sie sie als Zusatz an, der nachtrglich an Mastodon drangeklebt wurde, z. B. PeerTube, Pixelfed, Funkwhale, Castopod)
Was dagegen im Fediverse aus ihrer Sicht absolut nicht okay ist und bekmpft gehrt:
- darauf hinzuweisen, da das Fediverse mehr ist als nur Mastodon
- darauf hinzuweisen, da man selbst nicht auf Mastodon ist
- gegenber Mastodon-Nutzern Fediverse-Serveranwendungen auch nur zu erwhnen, die nicht als Erweiterung zu Mastodon angesehen werden (siehe oben)
- auf Leute zu antworten, die einen nicht erwhnt haben und denen man auch nicht folgt
- mehr als vier Hashtags, egal, wie man die rechtfertigt
- Textformatierung in irgendeiner Form, weil Textformatierung in Mikroblogging nichts zu suchen hat und Mastodon-Nutzer selbst ihre Trts nicht formatieren knnen
- nicht an jeden Post oder Kommentar genau die CWs dranzubauen, die irgendein individueller Mastodon-Nutzer braucht
- das CW-Feld (auch) fr etwas anderes als CWs zu nutzen, weil Mastodon das CW-Feld ja erfunden hat, und zwar als solches
- mehr als 500 Zeichen in einem Post
- berhaupt irgendwelche Features zu nutzen, die Mastodon nicht hat (oder von denen sie nicht wissen, da Mastodon sie auch hat), deren Nutzung Mastodon-Nutzer aber mitbekommen
- generell irgendwas zu machen, was in der Mitte 2022 neu definierten Mastodon-Kultur so nicht vorkommt und so nicht vorgesehen ist
Wer im Fediverse nicht auf Mastodon ist, wird nicht unerheblich diskriminiert. Derweil behaupten sehr viele auf Mastodon, da niemand im Fediverse dafr diskriminiert ist, welche Serveranwendung man nutzt, und zwar, whrend sie selbst weiterhin unbewut oder gar absichtlich Nicht-Mastodon-Nutzer weiter diskriminieren.
Das kommt brigens tatschlich daher, da diese Leute selbst am Anfang "wuten", da das Fediverse nur Mastodon ist. Folglich haben sie sich an ein in sich geschlossenes reines Mastodon-Netzwerk gewhnt und monate- oder gar jahrelang gefhlt in einem in sich geschlossenen reinen Mastodon-Netzwerk gelebt. Und das war schn.
Dann aber haben sie auf die harte Tour erfahren, da das Fediverse eben nicht nur Mastodon ist. Im allgemeinen sind sie irgendwann auf einen Post oder Kommentar gestoen, der sich auf verstrende Art und Weise von dem unterschied, was sie von Mastodon gewohnt waren. Der hatte mehrere tausend Zeichen. Oder
Fett- oder
Kursivschrift, und es war keine Unicode-Trickserei. Oder die Erwhnungen sahen "irgendwie komisch" aus, also verstrend komisch.
Wie auch immer: Dieser Post oder dieser Kommentar war so dermaen kein Mastodon-Trt, da sie vor Schreck Ziegelsteine gekackt haben. Sie waren so gestrt und verstrt, da sie das auf gar keinen Fall tolerieren konnten und nie angefangen haben, es zu tolerieren. Sie wollen, da das Fediverse wieder nur Mastodon ist. Was es brigens nie war. Oder zumindest, da sich alles andere komplett an Mastodon anpat und wie Mastodon wird (oder wahlweise gefediblockt wird) und sich das ganze Fediverse zumindest wie nur Mastodon anfhlt.
Und dann heit es, da "Haltet einfach eure Schnauzen und macht alles ganz genau so, als wrt ihr selbst auf Mastodon" nicht diskriminierend sei. Als Mastodon-Nutzer darf man sowas uern und
mu es sogar.
Als Nicht-Mastodon-Nutzer luft man im Fediverse dagegen, sobald Leute auf Mastodon von einem etwas mitbekommen, auf Eierschalen oder gar durch ein Minenfeld, weil es dann doch wieder irgendwelche ungeschriebenen mastodonzentrischen Regeln gibt, die auf Mastodon "jeder" kennt und beherzigt, von denen aber auerhalb von Mastodon nie jemand gehrt hat.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodon #
MastodonKultur #
MastodonZentrizitt #
MastodonNormativitt Buy /USDT
Entry Zone: 0.01256 - 0.01230
Target: 0.01268 - 0.01280 - 0.01292 - 0.01308 - 0.01322 - 0.01336
StopLoss: 0.01178
Leverage: 20x
This, by the way, is something that next to nobody in the Fediverse knows, and that many will deny and fight with all they can:
Alt-text must never include exclusive information that is neither in the post text nor in the image itself. Such information must always go into the post itself. If you don't have room in the post, add it to a reply or multiple.
That's because not everybody can access alt-text. Certain physical disabilities can make accessing alt-text impossible, for example, if someone can't use their hands. Money quote from way down :
I have a disability that prevents me from seeing alt text, because on almost all platforms, seeing the alt requires having a screenreader or working hands. If you post a picture, is there info that you want somebody who CAN see the picture but DOESNT have working hands to know Write that in visible text. If you put that in the alt, you are explicitly excluding people like me.
But you dont have to overthink it. The description of the image itself is a simple concept.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Inclusion #
A11y #
Accessibility #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost Mostly, just imagine youre telling your friend over the phone about image youre looking at and what they would need to know.
Let's just say I'm a bit critical about that because, in my opinion, it doesn't work in the Fediverse.
You can't describe images in Fediverse posts like over the phone
Allegedly, a "good" advice for image descriptions is always to describe images like you'd describe them to someone on a landline phone.
Sorry, but that's non-sense. At least for anything that goes significantly beyond a real-life cat photo.
If you describe an image through a phone, you describe it to
one person. Usually a person whom you know, so you've at least got a rough idea on what they need described. Even more importantly, you can ask that person what they want to know about the image if you don't know. And you get a reply.
If you describe an image for a public Fediverse post, you describe it to
millions of Fediverse users and
billions of Web users. You can't know what they all want, nor can you generalise what they all want. And you can't even ask one of them what they need described before or while describing, much less all of them. In fact, you can't ask at all. And yet, you have to cater to everyone's needs the same and throw no-one under a bus.
If I see a realistic chance that someone might be interested in some detail in one of my images, I will describe it. It won't be in the shorter description in the alt-text instead, it will be in the long description which I've always put directly into the post so far, but whose placement I'm currently reconsidering. If something is unfamiliar enough to enough people that it requires an explanation, I will explain it in the long description.
Right now, only meme posts are an exception. They don't need as much of a visual description as long as I stick to the template, and a poll has revealed that people do prefer externally linked third-party explanations over my own ones blowing the character count of the post out of proportion. This is the one time that I can safely assume that I actually
know what most people want.
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Inclusion #
A11y #
Accessibility CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
QuotePost #
QuoteTweet #
QuoteToot #
QuoteBoost One thing you could do is
AltText hashtag which many put on their posts with alt-text. Also,
AltTextHallOfFame hashtag and follow .
However, I'm not sure if that will lead to the desired outcome. Checking Mastodon users' alt-texts and the reactions upon these was part of what . In fact, I ended up describing all my original images twice, including with a long image description in the post itself. And I'm constantly upping my game, improving my style and declaring old image descriptions obsolete because I keep learning new things and trying new things.
Granted, you may not be inspired to go as far as I did, seeing as you've got 500 characters in posts whereas I have hundreds of thousands or even millions. But still, chances are that analysing other people's alt-texts may have you overthink image descriptions even more rather than less.
For reference, here are my latest original image posts in reverse chronological order (the older, the more obsolete):
In each case, the post including image(s) is hidden behind a summary and content warning. In the first post, the images themselves are additionally hidden behind a spoiler tag as an extra safety measure due to their potentially sensitive content.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
CharacterLimit #
CharacterLimits #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta If you have a lot to describe, and/or if you need to explain your image, the best you can do is to give two descriptions for the same image.
A "short", purely visual description in the alt-text, also to satisfy the alt-text police and the Mastodon HOA who demand there be an alt-text for all images, no matter what.
And a long, detailed description that includes all explanations, and that goes into the post.
Yes, it will exceed 500 characters. But if you regularly have to describe that much, it's best to move someplace with a much higher character limit. Spreading a long description across multiple Mastodon toots can only be a short-term kluge.
Misskey offers you hard-coded 3,000 characters. All its forks have configurable character limits which tend to be higher. Akkoma offers you at least 5,000 characters. Friendica offers you 200,000 characters, but adding alt-text isn't as straight-forward as on Mastodon.
The limit I have here on Hubzilla is even higher I don't know how high it is, but it doesn't really matter because AFAIK Mastodon rejects all posts from outside with over 100,000 characters.
But I don't post images here anymore because Hubzilla cannot make Mastodon blank out sensitive images. I have two channels for images on (streams) now which
can make Mastodon hide images,
Jupiter Rowland's (streams) outlet and
Jupiter's Fedi-Memes on (streams). (streams) has a fixed character limit of over 24,000,000 that's defined by database field size.
That is, I rarely post images nowadays. Explaining my Fediverse memes is tedious enough already. But properly describing and explaining my original virtual world images so that everyone gets them takes up so much time and energy (one image post always takes up several hours, and I touch-type on a hardware keyboard) that there are practically always months between two image posts.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Misskey #
Forkey #
Forkeys #
Akkoma #
Friendica #
Hubzilla #
Streams #
(streams) #
CharacterLimit #
CharacterLimits #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta*jayrope Von KI fr Bildbeschreibungen fr meine Bilder halte ich gar nichts. Meine Bilder sind ber ein extremes Nischenthema, und um sie zu beschreiben und zu erklren, braucht es extremes Nischenwissen.
Ich hab's demonstrativ zweimal mit LLaVA versucht. habe ich selbst in acht Stunden und ber 25.000 Zeichen beschrieben. LLaVA hat in vielleicht einer halben Minute etwas ber 550 Zeichen rausgetan. .
Fazit:
- Ich konnte haarklein erklren, wo das Bild gemacht wurde, und zwar so, da es auch ein Laie versteht. Der Ort, die Sim, das Grid, die Software darunter, was es mit der Software auf sich hat, was ein Grid ist, was eine Sim ist usw. usf. etc. pp. Das ist es, was die Leute wissen mssen. LLaVA konnte nur grob spekulieren.
- Ich habe den Avatar recht detailliert beschrieben, LLaVA berhaupt nicht und ihn als "Charakter" bezeichnet.
- LLaVA hat darber halluziniert, wohin der Avatar guckt. Ich wute es, obwohl es von hinten gar nicht sichtbar ist. Ich konnte auch sagen, warum der Avatar von hinten zu sehen ist.
- LLaVA hat Text in dem Bild nicht mal gefunden. Ich habe fast alles an Text, was fr mich irgendwie lesbar war. wortwrtlich transkribiert. Ich glaube, ich habe nur ein Nummernschild ber einer Tr auf einem Bild in diesem Bild vergessen.
- Ich habe von dem Ort den popkulturellen Bogen zu Edgar Wallace und zum Frhstyxradio schlagen knnen. LLaVA nicht.
- LLaVA hat nicht mal geschrieben, da das Bild schwarzwei ist. Ich habe korrekt geschrieben, da in Wahrheit alles in-world von der Szenerie bis hin zum Avatar schwarzwei ist.
- Dieses ominse Gebilde rechts im Bild LLaVA hat es nicht mal wahrgenommen. Ich habe es in 3000 Zeichen beschrieben und in weiteren 2500 Zeichen erklrt.
- Bei der Tageszeit hat LLaVA sich total verhauen, weil es weder wute, in welche Richtung die Kamera zeigt, noch, wie hoch die Bume eigentlich sind, die die Schatten werfen.
- LLaVA hat auch keinen der Bume als Bergkiefer identifizieren knnen.
Das wird der Altbot nicht signifikant besser knnen.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
Bildbeschreibung #
Bildbeschreibungen #
BildbeschreibungenMeta #
CWBildbeschreibungenMeta #
AI #
KI #
LLaVA #
Altbot Buy /USDT
Entry Zone : 14.538 - 14.501
TARGETS:
14.655
14.826
14.978
15.132
15.254
15.420
StopLoss: 13.814
Leverage 25x
Click on the link below to join our Telegram channel for more accurate Crypto Signals
/USDT :
Buy: 0.6540 - 0.6300
Target: 0.6606 - 0.6672 - 0.6739 - 0.6810 - 0.6880 - 0.7950
StopLoss: 5%
Leverage: 20x
Hubzilla funktioniert eben fundamental anders als Mastodon und viele andere Sachen im Fediverse. Und ja, es hat eine heftige Lernkurve, bei der einem kaum geholfen wird. Die eingebaute Hilfe ist (noch) unvollstndig, hoffnungslos veraltet und fehlerhaft.
Der Pepe (Hubzilla) hat sie , das ist aber noch nicht offiziell eingebaut. Pepe hat brigens auch die , die ber die Hilfe hinausgeht.
Dazu kommt, da man Hubzilla nicht einfach so mit Standardeinstellungen nutzen kann. Da gibt's eigentlich irre viel, was erst eingestellt werden mu, damit Hubzilla vor allem im heutigen Fediverse vernnftig funktioniert. Hubzilla ist von seinen Standardeinstellungen her darauf ausgelegt, wie man sich 2012 vorstellte, wie das Fediverse 2015 mal aussehen soll.
Um dich z. B. mit Mastodon verbinden zu knnen, mut du erst ActivityPub als "App" "installieren".
Du wirst dich mit dem Berechtigungssystem auseinandersetzen und dir mindestens zwei, drei verschiedene Contact Roles anlegen mssen. Nur auf dem Wege kannst du nmlich die Berechtigungen deiner Kontakte steuern.
Wenn du Privacy Groups "installierst", um sowas wie Mastodons Listen (auf Koks und Steroiden) zu haben, wirst du bei der standardmigen Privacy Group abschalten mssen, da normalerweise alle deine Posts dahin gehen, weil du sonst nicht ffentlich posten wirst, wenn du nicht aufpat.
Es lohnt sich generell, mal in Augenschein zu nehmen. Da gibt's auch .
Auf jeden Fall lohnt es sich, dem
Hubzilla Support Forum beizutreten und zustzlich
Pepes Hubzilla-Sprechstunde.
Falls dich Hubzilla zu sehr erschlgt: Vielleicht brauchst du keine Verbindung zu diaspora*. Oder Artikel, Planungskarten, Wikis oder Webpages. Vielleicht mut du auch nicht unbedingt RSS- oder Atom-Feeds abonnieren. Vielleicht kannst du leben ohne so schicke neue Themes wie Neuhub Tab oder die Utsukta-Themes und ohne die Mglichkeit, so ziemlich alle Farben im "guten alten" Redbasic einstellen zu knnen. Vielleicht brauchst du auch keine mehreren Profile pro Kanal.
Vielleicht kommst du frs erste auch ohne nomadische Identitt aus, weil es ganz einfach noch kaum Instanzen gibt, auf die man klonen knnte.
Dann kannst du dir mal die zwei jngsten "Nachfolger" von Hubzilla angucken, falls du von denen noch nicht gehrt hast.
Zum einen ist da von Oktober 2021 . Inoffiziell wird es nach dem Code-Repository "
(streams)" genannt, also immer in Klammern, weil es eigentlich nicht der Name ist. (streams) ist ein Fork von einem Fork von drei Forks von einem Fork (von einem Fork) von Hubzilla von Hubzillas eigenem Schpfer Mike Macgirvin.
Ein paar Vorteile:
- ActivityPub ist fest in den Kern eingebaut und auch in neuen Kanlen standardmig aktiviert.
- Hubzillas Verzeichnis listet nur Kanle, die auf dem Nomad-Protokoll basieren, also Hubzilla- und (streams)-Kanle. Es kann nicht auf PubCrawl oder diaspora* zurckgreifen. Weil auf (streams) ActivityPub im Kern ist, listet (streams) im Verzeichnis auch alle mglichen ActivityPub-Akteure.
Wenn man "Groups only" whlt, listet (streams) nicht nur Hubzilla-Foren und (streams)-Gruppen, sondern auch Guppe Groups, Friendica-Gruppen, Lemmy-Communities, /kbin- und Mbin-Magazine, PieFed-Communities usw., soweit die Instanz sie kennt. - (streams) ist aktuell die einzige Fediverse-Software, die nomadische Akteure sowohl auf Nomad als auch auf ActivityPub (siehe unten) als nomadisch erkennt.
- Die Einstellungen sind alle an einer Stelle zusammengefat. Den Zirkus mit /settings/features und den Zahnrdern oben links gibt's nicht mehr.
- Kanalweite Berechtigungen knnen sehr viel einfacher eingestellt werden. Man hat nicht mehr alles in undurchsichtige Presets verpackt oder eine Custom-Kanalrolle, wo einem vorm Einstellen gewarnt wird und deren Einstellungen nicht da sind, wo sie ausgewhlt wird. Die Kanaltypen decken nur noch einige sehr wenige Einstellungen ab, alles andere ist immer einzeln einstellbar.
- Berechtigungen pro Kontakt knnen direkt am Kontakt eingestellt werden. Berechtigungsrollen (Contact Roles auf Hubzilla) sind jetzt im Prinzip nur noch Presets zur Bequemlichkeit und daher optional.
- Posts knnen auer mit BBcode auch mit Markdown oder HTML formatiert werden. Gleichzeitig, weil manche Features nur mit BBcode gehen.
- Zusammenfassungen (die Mastodon als CWs versteht) mssen jetzt mit Tags gesetzt werden, dafr gibt es wie auf Friendica kein Eingabefeld mehr. Dafr funktionieren sie zuverlssig auch bei Kommentaren.
- Beim Hochladen von Bildern kann man gleich einen Alt-Text angeben. Bei schon hochgeladenen Bildern kann man einen nachreichen. Wenn man sie dann in einen Post einbettet, wird der Alt-Text gleich in den Einbettungscode eingebaut. Bei Hubzilla ist das noch Handarbeit direkt am Code, die offiziell (noch) nirgendwo dokumentiert ist.
- Wenn du einen Bildpost mit dem Hashtag
#nsfw
oder #sensitive
versiehst, wird das Bild/werden die Bilder so markiert, da Mastodon sie ausblendet. Das ist aber auch eine der ganz wenigen Konzessionen an Mastodon. - Antwortenkontrolle geht (optional) noch weiter als auf Hubzilla: Du kannst bestimmen, da nur Mitglieder einer bestimmten Access List auf einen Post antworten drfen. Du kannst bestimmen, bis zu welchem Zeitpunkt auf einen bestimmten Post geantwortet werden darf. Und du kannst einstellen, wie lange generell auf deine (neuen) Posts geantwortet werden darf.
Da betreibt
Der Pepe (nomd) brigens auch . Support gibt's hier:
Streams.
Falls es dich interessiert: .
Und dann ist da etwas, was Mike Macgirvin selbst Mitte August 2024 von (streams) geforkt hat (er entwickelt immer noch beides weiter), was aber offiziell erst vor vier Tagen, am 12. Mrz, erstmals releaset wurde:
. Im Prinzip funktioniert Forte wie (streams). Aber whrend (streams) auf der neuesten Version des Nomad-Protokolls basiert und ActivityPub immer noch optional ist, basiert Forte komplett auf ActivityPub und erledigt als erstes Fediverse-Projekt auch nomadische Identitt komplett ber ActivityPub.
Einen Tag nach Release hat die wohl auch wieder aktuell gestartet, wobei ich nicht wei, ob da Registrieren mglich ist. Und er hat als Supportforum gestartet.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
ForteThe only thing more exhausting than running a marathon is pretending to be interested in someone else's marathon story
Long Legs Fetish In High Heels And Calvin Kleins
This intimate boutique hotel in Amagansett, NY only has 14 units that feel like your own home. hotels hotels Island York
Posted into The Travel Exchange
The entire "Metaverse = blockchain + crypto + NFTs" cryptobro scene seems blissfully unaware of the existence of (tagging them so they can have a laugh for the weekend if they notice). In fact, apparently, so does almost everyone who started a virtual world since the mid-2010s, especially since Meta's Horizon announcement. A few virtual world makers may be fully convinced that Second Life is dead and gone since 2008 or 2009, just like so many others. Most of them, however, seem to never even have heard that name ever before.
The only exception seems to be Horizon itself, but only
because it was spearheaded by a former Linden. And even then, Horizon failed because Zuckerberg had too much control and, at the same time, no idea whatsoever how virtual worlds work.
It's especially the cryptobros who put raking in money above and before anything else. Sure, a commercial virtual world needs a business model and a steady source of income to stay afloat. But the "business model" of many crypto-based virtual worlds is, "First I'll sell land to celebrities and megacorporations for cryptocurrency worth millions of real-life dollars a patch. Then I'll rake in even more money when the cryptocurrency rises in value as people start speculating with it. And then, well, yeah, I guess I'll take care of the world." Lots of "metaverses" tanked because they sold NFT deeds to virtual land that they never actually managed to create.
Decentraland actually exists, you have to give them that.
Still, the makers of Decentraland had and still have to if they refuse to look at other worlds and .
This includes in-world building. Just because it's possible, doesn't mean it's convenient. And virtual worlds based on game engines like Unity3D or the Unreal Engine don't make it convenient. If you want a city in-world, you have to build the entire city in an external game scene editor
as one block, all small details included, script it there, export it, convert it, and then you can import it. You can't actually build anything in-world. You can't change anything in-world. If you have a few more visitors at home, and you want to add a chair or two, you have to fire up the editor, edit the whole scene, add the chairs there, export it again, convert it again and throw everyone out of your home because you have to delete and re-import the entire scene.
Second Life lets you add a chair right there, right then. Second Life lets you
build furniture on the spot if you're skilled enough. Or entire buildings. At "worst", the external tools you use are Blender for 3-D meshes and Photoshop or GIMP for textures so the
single objects you make look better. And still, you piece your part of the world together from big and small objects
in-world. Say about Second Life's graphics engine what you want, but it facilitates world-building greatly because it doesn't require in-world places to be static, monolithic scenes like in video games.
Speaking of which, Second Life is often criticised for its learning curve and bad on-boarding. Decentraland seems to manage to be even worse.
Oh, and if the makers of Decentraland had actually done their homework and some more research, they wouldn't use that stupid "first decentralised metaverse ever" claim. It's stupid because it's wrong.
The "first decentralised metaverse" came to exist in 2007 already with , a free and open-source server-side re-implementation of Second Life's technology. The term "metaverse" has actually been used around OpenSim since 2007, including by (now offline for extended maintenance) , the first public OpenSim grid, the oldest still existing OpenSim grid and one of the two biggest OpenSim grids.
Decentraland is "decentralised" in the crypto sense: It uses its own cryptocurrency rather than relying on one of the big ones like Bitcoin, Etherium or Dogecoin. But as a virtual world, it's still one big monolithic walled garden.
OpenSimulator is decentralised by being the technology underneath well over 3,000 big and small individual virtual worlds. Now it comes: Almost all of them are connected to one another via the so-called Hypergrid which was created in 2008. You can have an avatar on one grid and visit another grid with that avatar, even taking your inventory with you. You can have friends on other grids. You can join groups on other grids (although group functionality across grid borders can be hit-and-miss).
Lastly, virtual land NFTs being cash cows only works because people don't know about Second Life or think it's dead, and because they've never heard of OpenSim. There are more than enough stories of people or companies shelling out eight-digit US dollar sums for patches of land in new virtual worlds.
AFAIK, Second Life charges you some $250 of monthly rent for a 256x256m standard region with an island on it, surrounded by ocean, and $300 per month for the same size of land on the mainland. Granted, only if you can get that land in the first place.
's has , depending on land size and capacity. The default is a bit over $25 a month for 1,024x1,024m and 20,000 prims. And the Wolf Territories, being a commercial grid, are actually considered expensive because the "standard" has been $10/month for 256x256m and 15,000 prims, and some grids go as low as $5/month for 256x256m. You're likely to get what you pay for, but still.
This is also possible because, unlike Second Life, unlike Decentraland, unlike Horizon, unlike
almost all other virtual worlds, land is not scarce in OpenSim. Anyone can literally make their own land in OpenSim. You can run OpenSim on a Web server or on a machine at home. You can host your own land as a stand-alone and attach it to an existing grid, although only few grids allow this. Or you can even host your own entire grid and open it to the Hypergrid if you so desire. The vast majority of grids is home-hosted.
In fact, all those who are working on building the "open Metaverse" should take quite a few more closer looks at OpenSim. Otherwise they're bound to make some very painful mistakes.
#
Long #
LongPost #
CWLong #
CWLongPost #
Decentraland #
Blockchain #
Crypto #
Cryptocurrency #
Cryptocurrencies #
NFTs #
MetaPlatforms #
MetaHorizon #
Horizon #
HorizonWorlds #
SecondLife #
OpenSim #
OpenSimulator #
Hypergrid #
Metaverse #
VirtualWorlds #
Decentralised #
Decentralized It may not be very active because explaining my memes has proven to be very tedious, even if people let me get away with linking to external explanations. But you may try my "" channel. It's on which is part of the Fediverse and one of its Facebook alternatives. You can follow it from Mastodon.
fedimemesonstreamsstreams.elsmussols.net
Just beware: If I get going again, chances are I'll lampoon Mastodon. A lot. In ways that those who think Mastodon is the bee's knees, the best there is, may not like.
Also, there is where I post my memes as well. It's on , one Fediverse alternative to Reddit. But, again, you can follow it from Mastodon.
fedimemesfeddit.uk
This time, however, you're most likely dealing with people who didn't come from Twitter to Mastodon to Lemmy, but rather with people who came from Reddit directly to Lemmy without ever having been on Twitter or Mastodon. They may not know much about the Fediverse outside of Lemmy, so most memes are only about Lemmy without saying so.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Streams #
(streams) #
Lemmy #
Memes #
FediMemesif you look at what employers are being ask to pay towards employer contributions for staff this year, they may be paying of staff... so what chance does government have in getting term sick and folks with into employment... it is just another **K
IMO...one of the main failings in this concept across all party's who have historically tried to get folks who have a or have been on term sick back into employment is a basic truth... will not them, including, government NHS and Local authorities...
I'm reading a book on anti-gravity, it's impossible to put down
Dildo 25 Cm in the ASS . ANAL Fisting . Long SQUIRT