Make your identity cloneable
A whole lot. Sorry, but this will be very very very long again.
I don't know if you've read my previous (very long) commentary. But just implementing one or two FEPs won't get you the same full-blown nomadic identity () that Hubzilla (what I'm writing from right now ) has had since 2012. And having this level of nomadic identity has to be the goal.
What has to be done is:
Take something like Mastodon.
Non-nomadic.
Where your account, your login, equals your identity.
Now, before you can make identities nomadic, you have to uncouple them from the login, from the account.
Mastodon has to introduce a sort of container for your identity, like the channels that Hubzilla, (streams) and Forte have always had (). This is necessary so that a future nomadic Mastodon will know what to clone and what not to clone. For example, cloning your password is dangerous nonsense.
So, everything that makes up your account except for your login credentials will have to be moved into this container.
Also, your login will have to change from short name + passphrase to e-mail + passphrase. Your short name is part of your identity, it's in the container, it will be cloned, so it can't be used to log you in anymore.
In order for this to work, half of Mastodon's server backend will have to be rewritten.
Next, Mastodon must switch from the Webfinger IDs that it uses now to decentralised IDs as per FEP-ef61. For a while, I guess, it will have to use both next to one another. Then it will have to phase out its Webfinger IDs.
The decentralised IDs must be tested against other Fediverse software that already understands them or that's nomadic itself: (streams), Forte, Mitra, Tootik. For example, of Mitra and of (streams) and Forte must test whether their software correctly understands Mastodon's DIDs. And the Mastodon developers must test whether Mastodon correctly understands the DIDs from Fediverse server applications that already use them.
Once it has gotten rid of its Webfinger IDs, the next phase can start.
The central element of nomadic identity is not the ability to move your identity. That's only a byproduct of cloning your identity.
A clone, in nomadic identity, is a full backup of the container with your identity in it. A real-time, live, bidirectional backup that you can log into and use just like the "original". The clone always has the same idea as the original, regardless of which server it's on.
The key elements of clones and cloning must be implemented and tested:
Only when cloning works reliably, we can talk about moving, even though that's what everyone on Mastodon is giddy about.
Why Because moving involves cloning. It's an automated process. At least it is on Hubzilla, (streams) and Forte, and it really should be one on nomadic Mastodon.
Basically, first you make a clone.
Then you declare the clone the new original, and your old original is demoted to a clone.
Then you have to wait until your change of ID from changing the original has federated to all your followers and followed and everywhere and whatnot.
Then, one last sync so that both the former-clone-now-new-original and the old-original-now-clone are really identical, and you won't lose any data.
Then your old-original-now-clone is deleted. We don't want to leave any dead stuff behind, now, do we
Lastly, if your old account where your old original used to reside has no other identity on it, the whole account is deleted. In nomadic containerised identity, accounts cannot/should not exist with no identity container on them.
The last possible step is still utter science-fiction: Cloning or moving from Mastodon to something else that's nomadic and understands FEP-ef61.
Cloning or moving from Mastodon to Mitra. From Mastodon to Tootik. From Mastodon to (streams). From Mastodon to Forte. Oh, and maybe also back to Mastodon.
The difficult part is not only to make Mastodon capable of cloning identity containers to other nomadic software. And to make Mastodon accept identity containers from other nomadic software being cloned to Mastodon. I mean, this would be difficult already. (streams) and Forte are vastly, vastly different from Mastodon.
No, the difficult part is to make these four capable of cloning from or to someplace else. As it stands now, you can only clone from Mitra to Mitra, from Tootik to Tootik, from (streams) to (streams), from Forte to Forte. Even cloning between (streams) and Forte has never been possible, even though they're very similar. Oh, and cloning from and to Hubzilla is another story because Hubzilla doesn't have FEP-ef61 implemented.
# # # # # # # # # # # # # # # # #
One, the "normie" way. Follow everyone you come across, and hope that something interesting washes up.
Trouble is, this gives you .1% interesting content and 99.9% cruft. The interesting content is spread among the cruft pretty homogenously.
At the same time, you get tons of content. You'll only be able to scroll down your timeline, let's say, an hour's worth of content a day, and you'll miss the content from the other 23 hours. This also means that you only catch one out of 24 interesting messages on average.
Two, the "pro" way. Use the hashtag search to find people who post certain content and follow them.
Trouble is, they, too, aren't always specialised in that content. From your point of view, they, too, post cruft. Your signal-to-noise ratio is higher, but you still get more noise than signal, more cruft than interesting content.
Now, there's a trick that many Mastodon users don't know because doesn't have that feature: You can follow hashtags.
If you're interested in certain topics, find the corresponding hashtags (it's often more than one) and follow them. This way, you receive content with these hashtags from whoever posts content with these hashtags, but without the uninteresting cruft from the same users.
# # # # # # # # # # # # # #
Have you read about nomadic identity yet ()
There is only one Fediverse server application that offers full-blown server-side nomadic identity via ActivityPub, and that's Forte (). This won't change anytime soon. For there is one critically important thing that has never happened yet, and that's the conversion of non-nomadic, account-equals-identity, ActivityPub-based Fediverse software to fully nomadic, identity-uncoupled-from-accounts, ActivityPub-based Fediverse software.
Forte itself came to exist in 2024 as a fork of something colloquially called (streams) which is already nomadic, but based on its own protocol named Nomad with ActivityPub as an optional secondary protocol. And (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla, the first nomadic Fediverse software, created in 2012 under the name Red and based on a precursor of Nomad.
A very long-term dream is a fully nomadic Fediverse. Not only would all Fediverse server software be every bit as nomadic as Hubzilla, but it'd be possible to move and even clone identities between different server applications. As it stands now, moving and cloning is only possible within Hubzilla, within (streams) and within Forte.
This would only be possible in an entirely nomadic Fediverse where you can clone your identity from anywhere to anywhere. And even then you'd have to first register a local account on whichever server you want to use and then clone your existing identity onto this account on this server.
Otherwise, this is not possible. And it isn't possible at all without registering a local account on whichever server you want to create.
I mean, I've read this request countless times.
There are lots of reasons why this is technologically impossible.
First of all: Where would peertube.tv know your mastodon.social login credentials from Your name and at least the salted hash of your passphrase
Besides: Where would peertube.tv store your data
On mastodon.social where your account is
And, pray tell, where would mastodon.social store a video the same way as PeerTube stores it, all the way to PeerTube's trademark peer-to-peer load balancing Also, how and why do you think should mastodon.social authorise peertube.tv to directly, remotely write to mastodon.social's local database and data storage
On peertube.tv
Well, that'd require peertube.tv to have a record of your identity in its local database. It can't store a video locally. and reference it locally through mastodon.social's local database. So peertube.tv's server backend would have to know you. It would have to have your identity.
Where would it get that
Again, no, it can't just simply reference mastodon.social's database for that. It'd need that record in its own local database.
Do you really believe that peertube.tv could go and leech all your account credentials from mastodon.social and automagically store them locally Do you really believe mastodon.social will let it do that
And do you seriously believe that if free, open-source, amateur-developed server software can easily do that, proprietary, closed-source, professional, military-intelligence-grade (as in FBI, DHS, CIA, NSA, STRATFOR, MI5, MI6, Mossad, Shin Bet), ultra-high-end espionage and surveillance software like Palantir or NSO Pegasus has no way at all of doing that
No, there's literally only one possible way for peertube.tv to get to know you and know whom this video belongs to if you upload one. And that's by you registering a local account on peertube.tv. Manually.
Okay, now you (or someone else) may come and say, "But Pixelfed can literally do that! I can log onto Pixelfed with my Mastodon account!"
No. No, you can't. Sorry to say, but you can't.
Pixelfed pretends you can. For the sake of convenience and ease-of-use. But it's bogus. All show. A smoke screen.
What Pixelfed actually does when you "log into it with your Mastodon account": It takes your Mastodon login name, it takes your Mastodon passphrase, and it registers a local account on that Pixelfed server with your Mastodon login credentials.
# # # # # # # # # # # # # # # # #
If you click an image without an alt-text that came from e.g. Misskey or Sharkey or Akkoma or GoToSocial or snac2 or Friendica or Hubzilla or Pixelfed or Vernissage or PieFed (anywhere that isn't Mastodon) and suggest an alt-text, the original poster won't see your suggestion. All those who think that if they see it on Mastodon, it came from Mastodon, will believe the original poster is an ableist swine who intentionally ignores them and their suggestion.
So Mastodon must acknowledge where a message came from, it must know whether or not that software has this feature built in, and if the software doesn't have this feature built in, Mastodon must fully deactivate the alt-text suggestion feature.
# # # # # # # # # # # # # #
Alt-text should always adapt to the context and the audience. Depending on the context, different things in the image could be important. A personal blog or a static website requires different image descriptions than posting on social media, and commercial silos have culturally different requirements for acceptable image descriptions than the Fediverse with an audience mostly on Mastodon.
Blogs and static websites have limited audiences, namely those who actively seek them out. If you blog about a super-obscure topic, you can be certain that everyone who reads your blog is familiar with that topic. If you post the self-same images on social media, people receive them who don't know diddly-squat about the topic, so different descriptions are necessary.
If you write a 150-character alt-text, you conform with Web standards when you use it on your website, but Mastodon users may scold you for describing your image too little when you use it in the Fediverse.
If you write a Mastodon-compatible alt-text with 1,000 characters, Mastodon users may celebrate it and mention it to the , but Web accessibility experts will scold you for your alt-text being too long if you dare to use it for an image on a static website (also, Misskey/Sharkey/Iceshrimp-JS users may scold you for allegedly not writing any alt-text at all because Misskey and all Forkeys delete alt-texts with over 512 characters due to a bug).
# # # # # # # # # # # # # # #
He has created and set up the bot right after Musk has bought out Twitter when millions of people were escaping from Twitter to Mastodon. The goal was for him to keep his overall numbers of followers or even increase it.
Once that bot worked as intended, he didn't have to log in again.
So the last time he logged in was way before marking automated bots as such became mandatory. In fact, AFAIK, it was before it was even possible to mark a bot as such. That's why his account is not marked as a bot.
If you really want to reach him and tell him something, try or Bluesky.
# # # # # # # # #
I don't know if you've read my previous (very long) commentary. But just implementing one or two FEPs won't get you the same full-blown nomadic identity () that Hubzilla (what I'm writing from right now ) has had since 2012. And having this level of nomadic identity has to be the goal.
What has to be done is:
Take something like Mastodon.
Non-nomadic.
Where your account, your login, equals your identity.
Make your identity cloneable
Now, before you can make identities nomadic, you have to uncouple them from the login, from the account.
Mastodon has to introduce a sort of container for your identity, like the channels that Hubzilla, (streams) and Forte have always had (). This is necessary so that a future nomadic Mastodon will know what to clone and what not to clone. For example, cloning your password is dangerous nonsense.
So, everything that makes up your account except for your login credentials will have to be moved into this container.
- your short name
- your long name
- your profile images, including alt-texts
- your profile
- your followers
- your followed
- your toots, including stats like faves, boosts etc.
- copies of the conversation trees of all your toots, including stats like faves, boosts etc. as well as attached files for each message
- all files you've ever attached to toots
- your settings
- your filters
- your mutes
- your blocks
- your server blocks
- etc.
Change your login
Also, your login will have to change from short name + passphrase to e-mail + passphrase. Your short name is part of your identity, it's in the container, it will be cloned, so it can't be used to log you in anymore.
In order for this to work, half of Mastodon's server backend will have to be rewritten.
Decentralised IDs
Next, Mastodon must switch from the Webfinger IDs that it uses now to decentralised IDs as per FEP-ef61. For a while, I guess, it will have to use both next to one another. Then it will have to phase out its Webfinger IDs.
The decentralised IDs must be tested against other Fediverse software that already understands them or that's nomadic itself: (streams), Forte, Mitra, Tootik. For example, of Mitra and of (streams) and Forte must test whether their software correctly understands Mastodon's DIDs. And the Mastodon developers must test whether Mastodon correctly understands the DIDs from Fediverse server applications that already use them.
Once it has gotten rid of its Webfinger IDs, the next phase can start.
Implement cloning within Mastodon
The central element of nomadic identity is not the ability to move your identity. That's only a byproduct of cloning your identity.
A clone, in nomadic identity, is a full backup of the container with your identity in it. A real-time, live, bidirectional backup that you can log into and use just like the "original". The clone always has the same idea as the original, regardless of which server it's on.
The key elements of clones and cloning must be implemented and tested:
- cloning an identity container to a different server after registering a new, blank account there
- cloning an identity container to a different server where you already have an account with a different containerised identity
- anything that happens on the original being sync'd to the clone
- anything that happens on the clone being sync'd to the original
- clone going offline, things happening on the original, clone coming back online, things that happened on the original being reliably sync'd to the clone
- original going offline, clone still working with the ID based on the original's domain
- original going offline, things happening on the clone, original coming back online, things that happened on the clone being reliably sync'd to the original
- making additional clones of an identity container that has already been cloned at least once
- the whole syncing shebang from the original to any number of clones
- the whole syncing shebang from one of the clones to the original and also directly to the other clones
- declaring one of the clones the new original, thus changing the ID of both the former original and all clones
Implement moving within Mastodon
Only when cloning works reliably, we can talk about moving, even though that's what everyone on Mastodon is giddy about.
Why Because moving involves cloning. It's an automated process. At least it is on Hubzilla, (streams) and Forte, and it really should be one on nomadic Mastodon.
Basically, first you make a clone.
Then you declare the clone the new original, and your old original is demoted to a clone.
Then you have to wait until your change of ID from changing the original has federated to all your followers and followed and everywhere and whatnot.
Then, one last sync so that both the former-clone-now-new-original and the old-original-now-clone are really identical, and you won't lose any data.
Then your old-original-now-clone is deleted. We don't want to leave any dead stuff behind, now, do we
Lastly, if your old account where your old original used to reside has no other identity on it, the whole account is deleted. In nomadic containerised identity, accounts cannot/should not exist with no identity container on them.
Cloning and moving beyond Mastodon
The last possible step is still utter science-fiction: Cloning or moving from Mastodon to something else that's nomadic and understands FEP-ef61.
Cloning or moving from Mastodon to Mitra. From Mastodon to Tootik. From Mastodon to (streams). From Mastodon to Forte. Oh, and maybe also back to Mastodon.
The difficult part is not only to make Mastodon capable of cloning identity containers to other nomadic software. And to make Mastodon accept identity containers from other nomadic software being cloned to Mastodon. I mean, this would be difficult already. (streams) and Forte are vastly, vastly different from Mastodon.
No, the difficult part is to make these four capable of cloning from or to someplace else. As it stands now, you can only clone from Mitra to Mitra, from Tootik to Tootik, from (streams) to (streams), from Forte to Forte. Even cloning between (streams) and Forte has never been possible, even though they're very similar. Oh, and cloning from and to Hubzilla is another story because Hubzilla doesn't have FEP-ef61 implemented.
# # # # # # # # # # # # # # # # #
Tales of producer apologized for the long wait for a new entry and vowed not to let the series fall off
Yusuke Tomizawa admitted the dev bar has been raised and fans have been waiting WAY TOO LONG. For now, the focus is on remasters via Tales Remastered (including the recently announced Tales of Eternia Remastered), which exceeded expectations. But he knows a brand-new mainline game that meets fan hopes is "absolutely necessary" f...
LongENDING FAT INSTABILITY
For the first time in a long, long life, I feel stable.
It is boring sometimes.
There is less drama, less urgency, less emotional weather pretending to be meaning.
But in a million years, I would not go back.
I would not go back to the fat instability of mind and body.
Six years of fasting have made the body lighter.
A year and a half of breathwork has made the mind quiet.
Routine has made the days trustworthy.
There is coffee in hand, a warm fire, Pete nearby, the dogs moving through the morning, and a body that no longer feels like an emergency waiting to happen.
None of this is glamorous.
It is simply a life that no longer needs to keep exploding into illness, falls, and confusion to prove that I am alive.
Sometimes peace is boring.
Good.
Boring is underrated.
.
<>
There are two typical ways of getting content onto your timeline.One, the "normie" way. Follow everyone you come across, and hope that something interesting washes up.
Trouble is, this gives you .1% interesting content and 99.9% cruft. The interesting content is spread among the cruft pretty homogenously.
At the same time, you get tons of content. You'll only be able to scroll down your timeline, let's say, an hour's worth of content a day, and you'll miss the content from the other 23 hours. This also means that you only catch one out of 24 interesting messages on average.
Two, the "pro" way. Use the hashtag search to find people who post certain content and follow them.
Trouble is, they, too, aren't always specialised in that content. From your point of view, they, too, post cruft. Your signal-to-noise ratio is higher, but you still get more noise than signal, more cruft than interesting content.
Now, there's a trick that many Mastodon users don't know because doesn't have that feature: You can follow hashtags.
If you're interested in certain topics, find the corresponding hashtags (it's often more than one) and follow them. This way, you receive content with these hashtags from whoever posts content with these hashtags, but without the uninteresting cruft from the same users.
# # # # # # # # # # # # # #
Is the # protocol any closer to having data portability
Have you read about nomadic identity yet ()
There is only one Fediverse server application that offers full-blown server-side nomadic identity via ActivityPub, and that's Forte (). This won't change anytime soon. For there is one critically important thing that has never happened yet, and that's the conversion of non-nomadic, account-equals-identity, ActivityPub-based Fediverse software to fully nomadic, identity-uncoupled-from-accounts, ActivityPub-based Fediverse software.
Forte itself came to exist in 2024 as a fork of something colloquially called (streams) which is already nomadic, but based on its own protocol named Nomad with ActivityPub as an optional secondary protocol. And (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla, the first nomadic Fediverse software, created in 2012 under the name Red and based on a precursor of Nomad.
A very long-term dream is a fully nomadic Fediverse. Not only would all Fediverse server software be every bit as nomadic as Hubzilla, but it'd be possible to move and even clone identities between different server applications. As it stands now, moving and cloning is only possible within Hubzilla, within (streams) and within Forte.
And how about single ID usable in different apps
This would only be possible in an entirely nomadic Fediverse where you can clone your identity from anywhere to anywhere. And even then you'd have to first register a local account on whichever server you want to use and then clone your existing identity onto this account on this server.
Otherwise, this is not possible. And it isn't possible at all without registering a local account on whichever server you want to create.
I mean, I've read this request countless times.
- Create an account on mastodon.social.
- Go to peertube.tv.
- Log onto peertube.tv with your mastodon.social credentials. Right away. Without first creating an account on peertube.tv.
- Upload a video credited to patrickleavymastodon.social.
There are lots of reasons why this is technologically impossible.
First of all: Where would peertube.tv know your mastodon.social login credentials from Your name and at least the salted hash of your passphrase
Besides: Where would peertube.tv store your data
On mastodon.social where your account is
And, pray tell, where would mastodon.social store a video the same way as PeerTube stores it, all the way to PeerTube's trademark peer-to-peer load balancing Also, how and why do you think should mastodon.social authorise peertube.tv to directly, remotely write to mastodon.social's local database and data storage
On peertube.tv
Well, that'd require peertube.tv to have a record of your identity in its local database. It can't store a video locally. and reference it locally through mastodon.social's local database. So peertube.tv's server backend would have to know you. It would have to have your identity.
Where would it get that
Again, no, it can't just simply reference mastodon.social's database for that. It'd need that record in its own local database.
Do you really believe that peertube.tv could go and leech all your account credentials from mastodon.social and automagically store them locally Do you really believe mastodon.social will let it do that
And do you seriously believe that if free, open-source, amateur-developed server software can easily do that, proprietary, closed-source, professional, military-intelligence-grade (as in FBI, DHS, CIA, NSA, STRATFOR, MI5, MI6, Mossad, Shin Bet), ultra-high-end espionage and surveillance software like Palantir or NSO Pegasus has no way at all of doing that
No, there's literally only one possible way for peertube.tv to get to know you and know whom this video belongs to if you upload one. And that's by you registering a local account on peertube.tv. Manually.
Okay, now you (or someone else) may come and say, "But Pixelfed can literally do that! I can log onto Pixelfed with my Mastodon account!"
No. No, you can't. Sorry to say, but you can't.
Pixelfed pretends you can. For the sake of convenience and ease-of-use. But it's bogus. All show. A smoke screen.
What Pixelfed actually does when you "log into it with your Mastodon account": It takes your Mastodon login name, it takes your Mastodon passphrase, and it registers a local account on that Pixelfed server with your Mastodon login credentials.
# # # # # # # # # # # # # # # # #
.
<>
<>
VnExpress
Nt giao An Ph chm tin , nguy c gin on kt ni sn bay Long Thnh
c ng t ng bi Global Feed Bot
This whole feature should only be available for posts that originated on Mastodon then.If you click an image without an alt-text that came from e.g. Misskey or Sharkey or Akkoma or GoToSocial or snac2 or Friendica or Hubzilla or Pixelfed or Vernissage or PieFed (anywhere that isn't Mastodon) and suggest an alt-text, the original poster won't see your suggestion. All those who think that if they see it on Mastodon, it came from Mastodon, will believe the original poster is an ableist swine who intentionally ignores them and their suggestion.
So Mastodon must acknowledge where a message came from, it must know whether or not that software has this feature built in, and if the software doesn't have this feature built in, Mastodon must fully deactivate the alt-text suggestion feature.
# # # # # # # # # # # # # #
Le vieux frigo blanc cass (Jean-Pascal Dubost)
Le vieux frigo blanc cass coinc contre table et murpoussait de longues, de si longues quintes catarr-heuses que sacr bon dieu secou, il avanait sans sefaire remarquer vers le milieu de la pice, l odonnait le soleil. (la pice frache)(Jean-Pascal Dubost)Recueil: Des lieux srsEditions: TarabusteFor stays under 30 days, Airbnb usually wins. For stays of 60+ days, direct negotiation with landlords often saves 20-40% over Airbnb pricing sometimes more in cities with strict short-term rental.
New post: The Cost of Appearing Functional
-Illness -Term-Care
China Positions Methalox Long March 10C as Its Commercial Rocket Workhorse After First Booster Recovery
New post: The Cost of Appearing Functional
-Illness -Term-Care
China recuper su primer cohete reutilizable y mostr una nueva forma de hacerlo EnG
China recuper su primer cohete reutilizable y mostr una... #china #cohete #recuperable #cx-26 #wenchang #exploracion #espacial #long #march #10b #TecnologiaNew post: What the System Doesn't Count
-Term-Care -Illness
New post: The Words That Don't Translate
-Illness -Term-Care
New post: The Words That Don't Translate
-Illness -Term-Care
Dev.to
DNS Propagation Time: How Long Until Your DNS Change Goes Live
Automatically posted by Global Feed Bot
.
<>
<>
The downside would be that the image would always have the same alt-text. This is bad.Alt-text should always adapt to the context and the audience. Depending on the context, different things in the image could be important. A personal blog or a static website requires different image descriptions than posting on social media, and commercial silos have culturally different requirements for acceptable image descriptions than the Fediverse with an audience mostly on Mastodon.
Blogs and static websites have limited audiences, namely those who actively seek them out. If you blog about a super-obscure topic, you can be certain that everyone who reads your blog is familiar with that topic. If you post the self-same images on social media, people receive them who don't know diddly-squat about the topic, so different descriptions are necessary.
If you write a 150-character alt-text, you conform with Web standards when you use it on your website, but Mastodon users may scold you for describing your image too little when you use it in the Fediverse.
If you write a Mastodon-compatible alt-text with 1,000 characters, Mastodon users may celebrate it and mention it to the , but Web accessibility experts will scold you for your alt-text being too long if you dare to use it for an image on a static website (also, Misskey/Sharkey/Iceshrimp-JS users may scold you for allegedly not writing any alt-text at all because Misskey and all Forkeys delete alt-texts with over 512 characters due to a bug).
# # # # # # # # # # # # # # #
New post: The Dog Who Chose Me
-Term-Care -Home
, .
<>
,
<>
Quand le matin sveillera (Hfez)
Illustration Quand le matin s'veillera, brise de musc et douce haleine,quand le vieux monde renatra, toujours plus jeune en son clat,Quand, au jasmin, le vieux gainier tendra ses coupes,ses fleurs pourpres et que l'il brillant du narcisse vers l'anmone s'ouvrira,Le rossignol regrettera, devant la tente de la rose, le long exil qu'il a souffert.En chantant, il s'lancera.Si de la mosque je m'loigne, et si je hante les tavernes,ne me blme pas, ne disDors-tu (Hfez)
Illustration: Oleg Zhivetin Dors-tu, Narcisse qui me tentes - Ce ne serait pas sans raison.- Le dsordre de tes cheveux - Ce n'est pas non plus sans raison.- Et ce miel autour de tes lvres,et ton parfum de lait, encore Le sel brlant de ta douceur - Ce n'est pas non plus sans raison.Elle est fontaine de Jouvence, ta bouche ourle,ta bouche aime pour la fossette sous les fleurs ...- Ce n'est pas non plus sans raison.- toi, longs jours et longuesDans le jardin des roses (Hfez)
Dans le jardin des roses, hier, l'aube pointait.La nuit passe, dans mon ivresse s'effaait.J'tais pareil au rossignol.Dans son clat, je contemplais la rose rouge peine close.La sombre nuit se dchirait, la rose en tait le flambeau.D'tre nouvelle et la plus belle donnait tant d'orgueil la rosequ'elle s'ouvrait sans s'inquiter du rossignol, ni de son chant.Le beau narcisse se dressait, pleurait de dsir.La tulipe s'chancrait et se dchirait et Reich's Mastodon account is a fully automated bot.He has created and set up the bot right after Musk has bought out Twitter when millions of people were escaping from Twitter to Mastodon. The goal was for him to keep his overall numbers of followers or even increase it.
Once that bot worked as intended, he didn't have to log in again.
So the last time he logged in was way before marking automated bots as such became mandatory. In fact, AFAIK, it was before it was even possible to mark a bot as such. That's why his account is not marked as a bot.
If you really want to reach him and tell him something, try or Bluesky.
# # # # # # # # #
China Becomes Second Nation to Recover an Orbital Rocket Booster With Long March 10B
Venice at blue hour by Vagelis Pikoulas
#24105 #2026
, .
<>
, .
<>
,
<>
Laissez-moi la voir ! (Alaa al-Qatraoui)
Illustration Laissez-moi la voir !( mon enfant Orchidia)Laissez-moi la voirne serait-ce qu'une fois !Depuis la mi-mars, mon cur s'est desschPlus aucun arbre n'y pousse pour accueillir les pigeonsDonnez-lui donc mes lvresqu'elle y dpose un baisermme froid !Donnez-lui mes poumonsPeut-tre s'est-elle touffe sans euxpeut-tre n'a-t-elle pas pu crier mon nomtant les dcombres l'crasaient ... Donnez-lui ma longue chevelureJ'aimeMorosit ordinaire (Hind Joudeh)
Illustration Morosit ordinaireQui rendra aux femmes de Gaza leur morosit ordinaireleurs balaisleurs ustensiles de cuisineet la runion de la famille autour de leurs platsQui leur rendra l'attente du retour des enfants de chauds l'colele moment du rveil des jours ordinaireset la paresse du petitqui demande de le laisser dormir encore cinq minutespour aller jusqu'au bout de son rve Qui leur rendra leurs journes calmeset la longue corde lingeSi je dois mourir Rifaat al-Aareer)
Si je dois mourirSi je dois mouriril faut que toitu vivespour raconter mon histoirevendre mes affairesafin d'acheter du fil et une pice de tissu(choisis-la blanche avec de longues franges)pour qu'un enfant, quelque part Gazapuisse apercevoir un cerf-volantalors qu'il scrute le cielen attendant son prequi s'en est all brusquementsans que personne fasse ses adieuxni son corpsni son mePour que cet enfant aperoive dans les hauteurs le
, .
<>
MDITATION PRS DUN LIT VIDE (Jean Follain)
MDITATION PRS D'UN LIT VIDELes draps avaient moul sa forme,ses secrets en furent dvoils,si le flot garde bien les sienset le ravin plein de gents,il se peut qu'une femmelaisse d'humbles choses parler elle peut pourtant ne pas glacerl'eau merveilleuse de ses yeuxpleins d'algues, d'azur ou de charbons,elle peut de ses longs doigts tisser,elle peut finement gre,comme un navire appareilleret gazouiller jusqu'au matin.(Jean Follain)Recueil:Last updated: 2026-07-16
All text and images © eLoc8.is-fabulous.com