Find the latitude of any place.  

Ukraines long-range Flamingo cruise missile enters

Another issue is that I dont see a mechanism for actually *syncing* the content from one server to another.. so that still has to be addressed by some other spec (LOLA, for instance, if I could figure out how THAT works)
But.. once we have a sync in place, Im definitely up for trying to tie an actor or a piece of content to some sort of DID.

It's all being figured out by Mike and silverpill by and by.
On the one hand, silverpill is converting Mitra from your typical non-nomadic, account-equals-identity, built-against-Mastodon-first-and-foremost ActivityPub software into something that's every bit as nomadic as what Mike has made since 2012. Basically, part of what silverpill does is figure out and document what has to be done to achieve this so that other Fediverse server software developers can follow suit. This is the hard part.
At the same time, silverpill casts everything he develops into FEPs so that everything he does is covered by a standard of sorts.
On the other hand, Mike has already had nomadic server software since July, 2012. In fact, he was lucky: Instead of having to build nomadic identity into existing software, he forked his own Friendica, threw the entire backend away and wrote an entirely new one from scratch, this time against Zot rather than DFRN. (On a sidenote, this may explain why Hubzilla is significantly faster than Friendica.) Everything else was evolution ever since.
And he has had nomadic ActivityPub-only server software since July, 2023, which came to exist by taking software based on Nomad and also supporting ActivityPub, ripping the Nomad parts out and basing it entirely on ActivityPub.
So what Mike has is a "nomadic reference". This is where silverpill must head. And (streams) (the one based on Nomad) and Forte (the one based entirely on ActivityPub) are sparrings partners for Mitra's nomadic development branch. As new FEPs emerge, (streams) and Forte are adapted to them by and by. In only very few cases, FEPs are developed on Mitra as well as on (streams) and Forte FEP-ef61 was one such thing.
However, Mike doesn't have to document just how exactly stuff works on (streams) and Forte. You may argue that it'd be important to know for those who want to develop Nomad-based server software. But you don't make your own Nomad-based software by sitting down behind your computer and writing it from scratch. You make it by forking (streams) which was released into the public domain and with no name and no brand identity for this very reason. The streams repository was literally made to be forked.
Now, silverpill still has a long way to go. The nomadic Mitra development branch does understand (streams)' and Forte's portable objects and nomadic identities. But I'm not sure if it's actually nomadic itself yet.
The first step most likely has to be detaching the identity from an account and putting it into a container, the sort that Hubzilla, (streams) and Forte refer to as a "channel". I'm pretty sure that before Mitra goes nomadic, it will support multiple fully independent identities on one login.
The second step most likely has to be identity management between instances of the same container on different servers.
It isn't before then that we can talk about implementing actual data transfer and syncing it.
And it isn't before then that we can talk about standardising and documenting it in a way that helps those who want to go from non-nomadic to nomadic, or who want to build nomadic ActivityPub software from scratch.
Mike can't help much here. Mike sees the Fediverse and nomadic identity through the eyes of someone who has done nomadic things since years before ActivityPub was even made, and who had to switch his already existing concept of nomadic identity to a protocol which is not made for nomadic identity. One could say that Mike is based and Nomad-pilled.
silverpill, on the other hand, comes from non-nomadic ActivityPub, and that's what he knows, what he's used to. Just like every dev in the Fediverse who isn't Mike or one of his contributors or one of the two guys who took over Hubzilla in 2018. He basically has to re-invent the implementation of nomadic identity from scratch. And it's his experience that's required to know how the bits and pieces of nomadic identity can be implemented in both existing and new ActivityPub software and to cast it all into FEPs.
CC:
# # # # # # # # # # # # # # #
for FEP-ef61, i don't have personal experience with implementing it, so i can't speak for how easy/hard it is, i just know it exists. but there's a section in for compatibility with the rest of the current network, so it's not necessarily a split.

It isn't a split. Definitely not. And I know from personal experience as a (streams) user.
Upon first glance, FEP-ef61 looks like there's one ActivityPub Fediverse now that consists of (streams) and Forte, for these two have FEP-ef61 implemented, and one fully separate ActivityPub Fediverse that consists of everything else, and they're completely incompatible with one another. (Not to mention the networks based on other protocols like Nomad or the diaspora* protocol.)
Now let's look at reality. Remember (streams) is Forte before the Nomad protocol was ripped out. It's identical otherwise. The ActivityPub part works just the same, only that you can turn it off on (streams).
I've got two (streams) channels myself, and , both of which are even cloned. Now, look at the connections (you should be permitted to do that). I'm not only connected to Hubzilla, (streams) and Forte channels. I'm just as well connected to Mastodon accounts. Mutually because everything that Mike has created has Facebook "friends" rather than Twitter followers and followed. Black magic Or does FEP-ef61, in fact, not break compatibility to a degree that makes connections impossible
Oh, and by the way, the accounts with these channels on them were created in summer 2024, i.e. after FEP-ef61 was pushed from dev to release and rolled out to the servers. Everything on my channels that has an ID has a portable FEP-ef61 DID. Still, I can connect to Mastodon accounts, and Mastodono users can follow me.
but adding the identity to another server will generally be seen as a new actor by instances who do not support this, so that's definitely not perfect.

Exactly. But this is nothing that came up with FEP-ef61 when it was first rolled out to actual stable production servers in July, 2024. This has been the case since the first Red server connected to the rest of the Fediverse as early as 2012 (Red, spanish la red = the network, was renamed into the Red Matrix the same year and completely retooled, massively expanded and renamed into Hubzilla in 2015.) In other words, Hubzilla has it, (streams) has it, Forte has it, and everything in-between had it, too.
CC:
# # # # # # # # # # # # # # # #

Ukraines long-range Flamingo cruise missile enters serial production

s domestically developed long-range has entered serial production

It's reported that the missile has a range of 3,000 km (1,864 miles).

The official technical specifications have not been publicly released.

-range

'Long years of public service, experience will enrich our nation': PM Modi meets NDAs Vice Presidential nominee

What if moving a server looked like this:
1. sign up for new account
2. authenticate old account (OAuth, whatever)
3. click "migrate"
4. click "yes really"
5. celebrate
If this were possible, then a whole lot of people could become "server admins" without being IT nerds.

Reality on Hubzilla for longer than Mastodon, as well as on (streams) and Forte:
  1. Register a new account.
  2. Optionally: Wait for it to be manually activated by the admin.
  3. Be asked to create a channel (= the actual identity with posts and contacts and files and stuff your account is not your identity).
  4. Choose the option to move an existing channel.
  5. Enter the URL of the existing channel.
  6. Enter the password of the account on which the existing channel is located.
  7. Confirm
  8. A clone of the channel is created on the new server.
  9. The data of the existing channel is mirrored to the clone.
  10. The clone is promoted to main instance of the channel the already existing instance of the channel is demoted to clone.
  11. The ID of your channel is changed accordingly.
  12. All nomadic contacts (= on Hubzilla, (streams) or Forte) are automatically changed to the new ID.
  13. (streams) and Forte only: All non-nomadic contacts receive a new connection request.
  14. The former-main-instance-and-now-clone is deleted because you chose to move rather than clone.
  15. If there are no other channels on the account on the old server, the whole account is deleted because accounts cannot exist with no channels on them.

The only two differences between cloning and moving are that cloning leaves your main instance intact instead of deleting it, and it leaves it as your main instance by default rather than making the new clone your main instance.
It works for Discord, why not the Fediverse

It's a common misconception, probably even by FLOSS devs, that "server" on Discord that a handful of clicks on the Web interface inserts a new 19" rack iron into a rack inside some data centre with a LAMP stack and an installation of the Discord server backend on it and makes you the tech admin. Or something like that.
This is far from the truth. Discord has integrated the word "server" into its newspeak. On Discord, "server" means "chat room". A chat room on the same centralised, corporate-owned, commercially-operated server farm as all the other "servers".
At the same time, Generation Z and newer think that this is what "server" always means because they've never come into contact with TeamSpeak and never experienced LAN parties.
Administrating a Fediverse server, on the other hand, does equal administrating a LAMP stack on the command line, full stop.
I sincerely hope that the day won't come when someone does with e.g. Mastodon what the did with : turn a full server stack into an "easy-peasy", fully-preconfigured, Windows-only point-and-click application that anyone can install on their Windows machines with absolutely zero prior knowledge about servers or networks, that even automatically connects to a dynamic DNS service that was created specifically for this application so you don't even need to know anything about domains, and that can only be handled through the built-in Windows GUI. (Mind you, there are people who are actually asking for exactly this, only not for Windows, but for their iPhones. Food for thought.)
CC:   
# # # # # # # # # # # # # # # # # # # As a matter of fact, the technology behind FEP-ef61 has already been rolled out a bit over a year ago. (streams) uses it for its additional, optional-but-on-by-default ActivityPub support, Forte uses it, too, only that it's based on ActivityPub.
Both can connect to Mastodon and the rest of the Fediverse. So this is not compatibility-breaking. At most, there may be occasional hiccups because something cannot handle the new DIDs (or, like Hubzilla, has a tendency to insert an emoji into the DID because part of the DID URL is also an emoji shortcode). And Mastodon and the rest of the Fediverse still see a cloned (streams) or Forte channel as a number of fully separate, fully identical identities which, for some wicked reason, also happens to have the same backlog of posts and send the same posts simultaneously. Basically, a Mastodon user will perceive a cloned Forte channel like one manually operated Mastodon account and one Mastodon bot account that mirrors the first one. Only that they can't tell which one is the bot.
(Speaking in Mastodon or generally non-nomadic terms and from a Mastodon or generally non-nomadic point of view, if a channel is cloned, all instances but one are bots. From a nomadic point of view, they're all one identity with a bunch of live backups.)
But it isn't like Mastodon users can't follow Forte channels, or Forte users can't connect to Mastodon accounts. (Unless the Forte server admin user-agent-filters Mastodon, that is.) It isn't like FEP-ef61 creates a rift through the Fediverse that's impossible to bridge, and that requires the whole Fediverse to go fully nomadic.
# # # # # # # # # # # # # # # #
I've looked through FEP-ef61 in the past, and will give it another go. I think I struggled to see how this would be compatible with Mastodon, or other servers without them requiring a pretty big rewrite to support portable objects.

It won't. Especially not with Mastodon.
At the very least, they would have to start to understand portable objects and the concept of nomadic identity, e.g. that jupiterrowlandhub.netzgemeinde.eu and jupiterrowlandhub.hubzilla.de may be on two different accounts, but the exact same channel with the exact same identity, the exact same connections, the exact same content etc.
Mastodon has been flipping the bird both at the ActivityPub standard and at FEPs and at the whole rest of the Fediverse since it was made. Eugen Rochko has been trying to EEE the Fediverse since he created Mastodon, the very same thing that people on Mastodon feared that Threads would do. The only time he ever makes compromises is when he is put under pressure by even more powerful players like Automattic or Flipboard, and even then he only throws them tiny bones.
As gradually built his nomadic and ActivityPub-based Forte from his own nomadic and Nomad-based streams repository (itself a Hubzilla descendant), and as started making his non-nomadic and ActivityPub-based Mitra nomadic, their goal was to expand ActivityPub into something that supports nomadic identity via FEPs and, at the same time, make their own software compatible to these FEPs.
Their goal was not to make their software and these FEPs fully compatible with the Fediverse as it was in 2023/2024 and especially not to build them against Mastodon as it was in 2023/2024 or as it is now.
Especially Mike would never build anything explicitly against Mastodon. Rather, he'd make it possible to block Mastodon from an entire (streams) or Forte server, and he did. To Mike, Mastodon is not the heart and the core and the centre of the Fediverse around everything else orbits and justifiedly so. He rather sees it as a nuisance.
Seriously, nothing that Mike has created will ever be fully compatible with Mastodon, not as long as Mastodon's politics don't change greatly. I mean, client-side support for Mike's own OpenWebAuth magic sign-on was proposed for Mastodon. It went as far as an actual merge request in 2023. They core devs never even looked at that merge request, much less merged it. They silently rejected it.

# # # # # # # # # # # # # # # # #

Russias Bombers Keeping up Attack Tempo Despite Op Spiderweb: UK MoD

Russias long-range bombers are still assailing Ukraine at a steady pace despite Junes daring drone attack against the
-rangebomber

Find the latitdue and longitude of any place

I legitimately let out a cry of happiness when I replayed the jackenstein battle and- YOUR TAKING TOO LONG

I like the quite a bit. The of from a at the of the to a green. Very .

I am to know - Did you use a

Visi has the best friends! Grimm grinned as she began to wrap Visi up. Her ability to move and shape a liquid latex type substance made trapping her kinky friend up simple, and Visi loved it! She began to grope and play with Visi's breasts as she whispered kinky threats into her ear.


This makes me wonder if a decentralised, anyone-can-host-it third-party bridge that's only a bridge would be feasible.
Of course, it'd be the easiest to integrate such a bridge directly into Fediverse server software. But we've only got so many multi-protocol Fediverse server applications right now already, and the only one that's still occasionally adding new protocols or even a bridge is Friendica. It is therefore the only Fediverse server software that can connect to Bluesky without Bridgy Fed.
CC:
# # # # # # # # # # #Looooong day

they are trying to retain some relevancy but their licensing is bad compared to other options - they are trying to stay a 'frontier' model when really everybody wants local agi not agi in the cloud - its gonna be 10 years though for things to really really change for better or worse game

Yup. Mastodon clings hard to being purist, minimalist, old-school, original-gangsta microblogging. It's a miracle actually that Mastodon 4.0, released in October, 2022, introduced the displaying of some text formatting.
It says a lot that the character limit of 500 is hard-coded. It is not configurable. Digging into the source and modifying a file that'll be overwritten by git upon the next upgrade is not configuration, it's a fork. Also, Mastodon apparently keeps changing the way of raising the character limit, probably to keep admins from diverging from The Mastodon Way.
There is no technological reason within the Fediverse itself to limit posts to this length.
The software that I'm posting through is older than Mastodon by almost four years. It has been what it is now for ten months longer than Mastodon has existed. It was the first Fediverse software to adopt ActivityPub, two months before Mastodon. And, unlike Mastodon, it plays ActivityPub by the book as far as possible/feasible.
Still, it has a character limit of, wait for it, 16,777,215. That's the maximum size of the database field for the post text. These characters include alt-texts because images are embedded into posts by hotlinking to them rather than being file attachments, but they do not include summaries (= Mastodon CWs) because they've got their own database field.
Not only is it possible to practically not have a character limit at all, but it has actually been done, and it's fully compatible with Mastodon (only that Mastodon rejects posts with over 100,000 characters AFAIK, another arbitrary design decision which makes even less sense).
CC:
# # # # # # # # # # # # # # And yet, my long alt-texts are actually only the much shorter ones out of two descriptions for the same image. The long description always easily exceeds 1,000 words by far.
The only exception is when I post a meme. But even then I provide explanations in the post. If I can link to explanations, I do so. This is always the case with the meme templates themselves I simply link to KnowYourMeme. But as for the topic, if I can't link to explanations there, I have to give explanations in the post itself. I also have to explain how the template relates to the topic.
, I explained everything in the post itself. My impression was and still is that especially Mastodon users vastly prefer being explained stuff in the post to having to open links. So I gave a whole of nine explanations on up to four levels (= explaining an explanation of an explanation of an explanation) which took up some 25,000 characters.
I'm still torn between this notion and the one I got from a poll after this post. In that poll, not only did I ask people how and where they prefer explanations, but I also skewed the poll by estimating how many characters each variant would mean. The vast majority noped out when they read that a full set of explanations that wouldn't have them look up anything themselves would mean well over 10,000 characters.
My current guess is that at least a lot of people do want everything explained right in the post, but only until I directly confront them with how long these explanations would end up.
So for meme posts, my choice is to link where I can and explain what I can't link to, . For original images, my choice is to explain everything myself, partly because there is hardly anything I can link to anyway, partly because the visual description already grows so massive that 10,000+ characters of explanation don't make that much of a difference.
# # # # # # # # # # # # # # #

Warriors playmaker Te Maire Martin decides NRL future, in against-the-odds move

Its quite a turnaround. Earlier this season it looked like Martin would almost certainly depart at the end

Would you lose points for very long alt-texts/image descriptions
I tend to describe my original images in extremely high details. Recently (for any definition of "recently" because I haven't posted a single image in over a year due to the huge effort of describing them), my alt-texts tend to reach 1,500 characters or one or a few below that. At least ca. 900 characters are actual image descriptions, sometimes up to ca. 1,400.
And that's what I consider a "short" description. Because the rest of the alt-text explains where to find the "long" description. It's in the post itself. It includes verbatim transcripts of every last bit of text anywhere within the borders of the image, readable or not. And it includes all explanations which I deem necessary for everyone to understand my images.
This long description exceeds any known arbitrarily defined character limit anywhere in the Fediverse by magnitudes. I can post such long image descriptions because the only character limit I have here on Hubzilla is the maximum size of the database field for the post text.
Yes, you've read that right. I describe each one of my original images twice.
And I must write my image descriptions that long. I don't post real-life photos, nor do I post social media screen shots. I post renderings from extremely obscure 3-D virtual worlds. Maybe one in 200,000 Fediverse users has even only heard of the technology that drives them.
Thus, I cannot assume anything in my images to be familiar to anyone out there. I can't assume that anyone out there knows what anything in my images looks like, also because my images tend to contain things which simply do not exist in real life in any shape or form.
At the same time, my impression is that especially Mastodon users expect all information which they don't have to be served on a silver platter immediately with the image description. If you mention something in your image, and somebody doesn't know what it looks like, you're obliged to describe it right away. Expecting anyone to ask you anything about your image after the fact feels like being considered ableist. I mean, you could just as well expect people to ask you to describe the whole image in the first place, right
Same goes for explanations. Given the choice between looking stuff up themselves, being given links where they can look stuff up and being explained everything right there, right then, Mastodon users appear to greatly prefer the latter and only consider the latter really accessible.
And I have to explain a lot. When I tell you where I've taken an image, this alone takes me more characters than some of you use for a whole day's worth of alt-texts. The whole topic is so obscure that I have to explain explanations of explanations.
My personal record (warning: technically outdated image descriptions): . That's about 10,000 words. It took me two full days, morning to evening, to research for and write the image descriptions. It takes a screen reader about three hours to read the long description out loud. But someone somewhere out there might be interested in all this information and displeased if they had to ask me about it to get it.
As for bilinguality, I should add to my WIP wiki on image descriptions and alt-texts that an alt-text must never include more than one image because screen readers cannot switch between languages mid-alt-text.
What I do, and I'm not even sure if that's such a good idea, is transcribe text in images that is not in English verbatim, literally letter by letter, and then translate it into English as closely as possible. I'm torn between a verbatim transcript which a screen reader cannot read out correctly and only giving a translation which would not be a verbatim transcript.
In fact, I've once had a situation in which I had to transcribe a sign in English, (broken) German and French. So I gave

Nowadays, I'd simply avoid posting images with non-English text anywhere in it like the plague.
CC:
# # # # # # # # # # # Important:
That's because . And those who can't can never read the extra stuff you've put into your alt-text. It's lost to them.
If you need more than 500 characters, you should instead

CC:
# # # # # # # # # # # # # # # # # # # # # # # # # #
Alt text for calling out the relevant details you mistakenly assume are obvious to everyone
Alt text for explaining the joke to people that don't have the same background as you
Alt text for the 10,000 people learning something "everyone knows" for the first time today

Something that next to nobody knows:
You must never make information available only in the alt-text!
Not everyone can access alt-text. To access alt-text, it requires either a screen reader (which sighted people don't have) or at least one working hand.
If you have something to explain or any other information that is not available in/obvious from the image itself, this information goes into the post where everyone can access it.
Here are two articles in my (very early WIP) wiki on image descriptions and alt-text:

# # # # # # # # #

Teen boy housed in Tauranga motel by Oranga Tamariki for more than a year

During that year, Oranga Tamariki sent *Cody on a state-funded trip to a Pacific Island, with his now-estranged

That may be it.
So I stand corrected: If you do use a title, and you haven't changed that part of the configuration of your account, then Mastodon will not show the title, but it will show the abstract and a link to your original Friendica post.
If you don't use a title, Mastodon will show your post itself. But it may "sanitise" as in deface it, e.g. only four images and only as file attachments instead of way more images strewn about your post. It will use your abstract as a CW. And Mastodon fundamentalists may mute or block or criticise or attack or dogpile you for having the audacity to send "long" posts with over 500 characters to Mastodon.
# # # # # # # # # # # # # # # You've got two modes on Friendica.
Default behaviour:

Optionally, Friendica can be configured to always send everything as Note-type objects. If Mastodon shows all your posts, even those with titles, this is probably how you've configured your Friendica account.
Now, until recently, when you sent an Article-type object, Mastodon showed
If you gave an abstract, Mastodon treated it as a typical Mastodon content warning (Mastodon uses the same field for CWs as Friendica for abstracts) and hid the preview to your post behind your abstract-turned-content warning.
With the recent change, Mastodon shows
And it no longer hides this preview if you give an abstract.
The idea has always been that Mastodon leaves it to Friendica (or wherever an Article-type object comes from) to render the post in all its glory, with a title and text formatting and embedded images and so forth. But Mastodon was criticised for only giving a title as a preview for Article-type objects, just as it's still being criticised for largely defacing formatted long-form posts that come in as Note-type objects.
# # # # # # # # # # # # # # #Okay, while this is not optimal, I'd say it comes close enough to an improvement to be of importance.
Some of us know what it's like to send Article-type objects (and long-form content should always be these according to the ActivityPub spec) to Mastodon. Now, Mastodon's handling of long-form content has changed, believe it or not. Something that neither Friendica nor Hubzilla nor (streams) nor Forte could ever achieve happened under pressure from Flipboard (commercial player), Ghost (quickly growing Substack alternative that's trying to attract professional and commercial users), Automattic (the owner of WordPress) and NodeBB (fairly big bulletin-board forum player that added ActivityPub a while ago).
So much I should say in advance: No, Mastodon does not fully render Article-type objects in their full HTML-formatted glory from the title to dozens of embedded images. Mastodon's own Web interface isn't geared towards that, and neither is any Mastodon app, official or third-party.
Instead, Mastodon still handles Article-type objects by linking to the original like it used to. But it used to show only the title if there was one. If there was no title, all that Mastodon showed was a plain URL. If there was a summary, Mastodon did as Mastodon always does and has been done since 2017, regarded it as a content warning and hid the whole "post" with the title (if there was one) and the link behind it.
What Mastodon does now is finally acknowledge that some software out there actually uses the summary field as a summary field. The preview with the link to the original now also contains the summary, along with the title. If there is either, of course.
So if you're on something that can send or always sends Article-type objects (specialised blogging software, Friendica, (streams), Forte), it's well worth adding a summary to those posts that go out as Article-type objects.
(Speaking of Friendica: Dear Friendica users, please substitute any use of "summary" in this post with "abstract" if you don't know what I'm talking about.)

Re: Long-form articles

The long form content "movement" (of which I'm adjacent to but not fully involved) started up because two big implementors, Ghost and WordPress, were running into the same issues AP devs have been seeing this whole time, that Mastodon reduces articles to a title and link.
The difference is devs got together and pushed for changes, and got them done. Mastodon no longer treats articles the way they used to.
Now you can send in a summary that is used, and that gets you heaps closer to a better UX than what came before.
The long form text FEP aims to provide a way to send an alternative representation for the ubiquitous microblog software on the fediverse, in the form of a note, while still maintaining the use of other objects types (e.g. article)
# # # # # # # # # # # # # # # # # Who are the longformers anyway
They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.
They know themselves. They know each other. And they know Mastodon. And that's it.
None of them has ever heard of Pleroma or Akkoma.
None of them has ever heard of Misskey or the Forkeys.
None of them has ever heard of Mitra.
None of them has ever heard of GoToSocial.
None of them has ever heard of Hollo.
None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has . But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.
Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.
Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.
# # # # # # # # # # # # # # # # # # # # # # # # # # # #
Now you can send in a summary that is used, and that gets you heaps closer to a better UX than what came before.

Mastodon has misused summaries for content warnings since someone from the demo scene sent in a PR for Mastodon to do so in 2017.
So this means that Mastodon stopped doing so on Article-type objects and actually regards summaries as summaries and handles them accordingly instead
And when and with which version was this rolled out
Or did Mastodon insist in the creation of yet another text field which has to be rolled out to all macroblogging and long-form blogging server applications Even though ActivityPub does have a perfectly good summary field, only that Mastodon uses it for CWs
Although I must say that the step from displaying Article-type objects as title (if there is any) + link to displaying them as title (if there is any) + summary (if there is any) + link is not that big. Mobile users who see their Web browsers popping up as a nuisance will still ignore your content.
On the other hand, this does not only appease Eugen Rochko, the Lord and Creator of the Fediverse and all of its technology (according to the Gospel of Mastodon, anyway), but also those Mastodonians who demand there must not be any posts with over 500 characters in the Fediverse, and who immediately block everyone who exceeds 500 characters even only once even on the federated timeline.
Besides, there is still "long-form", multiple-paragraph content going out as Note-type objects. In general, I guess that comments always go out as Note-type objects.
# # # # # # # # # # # # # # # # # # # #
The dataset doesn't include some other popular platforms like Friendica, but I am sure they also display long form content just fine.

Friendica and its descendants from the same creator, Hubzilla, (streams) and Forte, can produce long-form content just fine. With just about all bells and whistles from a title plus six levels of headlines to an unlimited number of images embedded within the text.
So yes, they can display it as well. However, outside of their own communities, hardly anyone knows what they're capable of. Thus, Fediverse developers often try to solve problems that aren't even really there because they were solved before they became problems.
Mastodon's lack of support for articles, linking to the originals instead, is not really a lack. It's a deliberate design decision from around 2017 or so.
See, the first ActivityPub implementation was on Hubzilla. That was in July, 2017. And Hubzilla implemented ActivityPub by the book.
Mastodon followed two months later. But Mastodon has always had its own "interpretation" of ActivityPub that was limited by Mastodon's own intentional design limitations in order to remain Twitter-like, purist, minimalist, old-school, original-gangsta microblogging with as few features that Twitter didn't have as possible.
This is also why Mastodon has a HTML "sanitiser" built in. Up until the release of Mastodon 4.0 in October, 2022, that "sanitiser" reduced any and all incoming HTML to plain text. And it did so for all object types, including the Article-type objects which Hubzilla sent. After all, Hubzilla can act as a fully-fledged long-form blogging platform.
However, the ActivityPub spec defines Article-type objects as formatted long-form content. Still, Mastodon defaced Hubzilla's Article-type objects by reducing them to plain text.
So Mike Macgirvin got into contact with Eugen Rochko and told him to adhere to the spec and deactivate Mastodon's "sanitiser" and make it support full HTML rendering for Article-type objects.
And Eugen Rochko said that bold type and italics and bullet-point lists and images in the middle of the content have nothing to do with old-school microblogging, so they have no place on Mastodon, so he won't implement them.
This head-butting went back and forth. Eventually, Eugen presented a "solution". And that was not to render Article-type objects at all anymore. Instead, Mastodon links to them and adds their title above if they have one.
This was only done to shut Mike up so he'd stop complaining about Mastodon defacing Hubzilla posts and breaking the spec by doing so. From Mike's perspective, however, what Eugen did was flip Hubzilla the bird by completely refusing to show actual Hubzilla content and practically lock out a competitor.
Mike's reaction was to break the spec himself and switch Hubzilla from sending Article-type objects to sending Note-type objects, regardless of Mastodon still defacing them.
With the exception of a very short period after the release of Hubzilla 9.0 when Mario Vavti and Harald Eilertsend learned the hard way that Mastodon still links to Article-type objects, Hubzilla has only sent its posts as Note-type objects ever since.
Mike's other creations have different ways of handling object types.
Friendica, by default, sends posts with titles as Article-type objects and posts without titles as well as comments as Note-type objects. This can be deactivated so that Friendica only sends Note-type objects.
CC:
# # # # # # # # # # # # # # # # # # #



<>

Currently getting a few streams on - the version of

Cardinals left tackle Paris Johnson Jr. hopes to take teachings from Bengals great Willie Anderson and reach elite status

The 15-year-old was exhausted, sitting beneath the tree next to the field at a high school in Atlanta,
-NewsHeadlines -Form .

Always on the trade block, never traded: How long will Walker Kessler be with the Utah Jazz

Gli algoritmi di trading AI stanno facendo cartello sui mercati finanziari

Connection is key for Patriots new punter-long snapper pairing

In its essence, football is a game of connection. Whether it is actual physical connection on the field,
-page -england-patriots-media-transcripts-statements-interviews -england-patriots-training-camp

Sidney Crosby kicking off long 2025-26 season later this month with Team Canada

A Long-Term Appraisal of the New Jersey Devils Defenders

I know quite a few avatars that seem not to have changed much since they first showed up, and that was before mesh became a thing.
In at least one case, this goes all the way to classic, non-attachment "hair". That's probably because it has never been possible to recreate that individual look with a hair attachment, much less with a mesh body, a mesh head and mesh hair. The owner was the main tech in Metropolis before he left the sinking ship for OSgrid. That was around 2021, and yet, he styled his OSgrid avatar just like his Metro avatar.
In at least one more case, the hair is only a hairbase, and the avatar has never worn any attachments AFAIK. The owner seems to strongly oppose the idea of styling avatars, at least he doesn't understand why people do that, and I think he has only got that one avatar.
# # # # # # # # #Interesting stuff to see there.
On the one hand, Morning Glory shows a kind of beach house scene, very simple, built entirely from tinted prims with no textures, no transparency or anything. It's kind of reminiscent of screenshots from other virtual worlds. It's cute in a certain way, not to mention easy on your graphics hardware
On the other hand, ' display includes a working mirror, thanks to PBR. Of course, this requires dedicated graphics hardware.
# # # # # # # # # # #

Commission for RKosh
Art by Me

Today's three-hour DJ event in Dereos takes place on a brand-new sim that's inspired by the ZDF-Hitparade. I mean, they already have a sim inspired by the Beat-Club.
However: The music of the first half matches the location. In other words, Schlager. Probably mostly from the 1970s. The first DJ has opened with four Chris Roberts songs.
What really gives me to think is that even has announced "Schlager" for the second half. Whatever that means in her case.
# # # # # # # # # # # # # #
Last updated: 2025-08-19






Classic Vanity Plates