@hellquist Was there a link to the article? 🙂
@ercanbrack
Yes, on the word Opinion.
@hellquist
It seems the rich text rendering of links is not universally useful. I noticed that when I am looking at my own interlinked toots from different mastodont instances, links and generally rich formatting are stripped.
Lesson: when speaking to others about links we want them to click, always include a naked link. Proper links are more useful when speaking to self.
No fancy anything. Just text of which the last line being the link URL copied straight from browser adressbar.
That original post is simultaneously posted to Twitter. It also gets picked up by Friendica and re-posted (as opposed to re-shared) as an original post by my Friendica user. Finally, that Friendica post gets re-shared on Pleroma.
I only have a few contacts on more than one of those services, but am aiming to clean it up further. The reason I've been using them all is due to (obviously testing, but also) them having slightly different people on the platforms, and (quite importantly), they run at "different speed". My pleroma flow is the fastest. I could easily miss good readable (often longer than a "Great lunch I just had!") posts on it as they simply move off the screen too fast.
That fast movement can be mitigated by adding people (such as yourself @FailForward ) either to "lists" or as a contact in Friendica too. Then I get the more readable/longer content in a separate stream.
Pleroma doesn't support "lists" in its default front-end, so only when I am using either the Mastodon front-end or Soapbox (a Pleroma "theme") can I even see the "lists" functionality.
However, I like the fact that Friendica "sits in the middle" of the Fediverse, and is compatible with pretty much all the other services. Perhaps I should contemplate doing my original posts in Friendica instead. Hmm...
The downside, for me, with Friendica is that posts are using BBCode (which I have to look up every time I use) compared to Diaspora which uses Markdown (which I know already, and which I find neater/faster).
@hellquist @FailForward It’s interesting that you mention BBCode and Markdown. Everything that I see in my Mastodon clients seems to be just basic text. What specifically are you doing to your text in your posts? ie Bold, Italics, etc?
🙂 Try to use Mastodon web interface and click either on my profile, or click on the timestamp of this toot (top right corner - it's the toot age).
# What you will see
## Will probably surprise you
1. but **maybe** not _too much_
2. still can be an ~~interesting~~ experience
Either way, you'll see different stuff than you are used to.
| a | b | c | d | e |
|---|---|---|---|---|
| xxx | | **uuu** | | |
| | rr | | | |
and maybe even something else
<img src="https://upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Raster_graphic_fish_40X46squares_hdtv-example.png/675px-Raster_graphic_fish_40X46squares_hdtv-example.png" width="100%"/>
Like it?
If you look at this via some app, most likely **half** is plain _text_ and the rest is scrambled.
Here's a comparison of what you experience and what I experience on Mastodon. Very different...
I just realised it strips even the `img` tag. That sucks. So the only reliable way to include images is to upload them as attachments. But that is stupid, as often they would be from 3rd party websites... Well, I am misusing Mastodon here at qoto obviously...
