Skip to main content


Exciting! Mastodon may soon see support for incoming rich text.

Which means that more formatting options will be seen in Mastodon.

github.com/mastodon/mastodon/pโ€ฆ

See screenshot for what this might look like.

@fediversenews

in reply to Chris Trottier

Sounds good.๐Ÿ˜€

Hopefully no #fonts and #colors .
Copying and pasting from websites (etc.) into a #toot then becomes tedious, as with website content in html, for instance.

Fediverse News reshared this.

in reply to PensionDan

That is only being rendered on mathstodon!! I really like the effort behind it, even though its results are strange.
in reply to Chris Trottier

markdown is useful, but I've noticed that wherever it is on by default, people will use a single asterisk for a footnote, or for multiplication, or for some non-Markdown reason, and then the next 3 paragraphs of their comment will be in italics, and they'll be confused and upset. Complaints result, until markdown gets removed. To survive, markdown must be off by default, and require a button press to turn it on for a particular toot.

Fediverse News reshared this.

in reply to llewelly

@llewelly
Or integrate some proper WYSIWYG editors in the apps with the way to escape asterisk and other characters. Now, this is probably more daunting and surreal than making people more informed in the ways of Markdown.
Unknown parent

Katzentratschen
I'm well aware what I was replying to and โ€“ gasp! โ€“ I'm able to open the original page. You wouldn't say Pixelfed or PeerTube aren't playing nice for showing just posts with certain media, would you? @atomicpoet @fasnix
This entry was edited (1 year ago)

Fediverse News reshared this.

Unknown parent

Katzentratschen
@goatsarah @fasnix No, they aren't. It's a design choice. Same as limiting posts to 500 characters on most instances. Or don't showing text formatting.

Fediverse News reshared this.

Unknown parent

Jesse
@goatsarah @katzentratschen @fasnix Personally I'm far more bothered by long posts, which appear to be already supported by Mastodon, than rich text. There's no perfect solution but it seems to me the best solution is to let individual users decide.
Unknown parent

Katzentratschen
@goatsarah @fasnix It doesn't limit incoming posts, yes. And I didn't imply that. ๐Ÿ™„

Fediverse News reshared this.

Unknown parent

Katzentratschen
@goatsarah @fasnix Your point? I gave an example which wasn't about incoming posts but other design choices.

Fediverse News reshared this.

Unknown parent

Katzentratschen
@goatsarah @fasnix Or maybe you could just start a different post. I'm muting your account now.

Fediverse News reshared this.

in reply to Chris Trottier

Formatting is nice, now i need ability to make long posts..

Fediverse News reshared this.

in reply to Alex0007

@Alex0007 That is instance specific. I think my instance allows 11,000 character posts.
in reply to Brian Hawthorne

@Alex0007 @Brian Hawthorne @Chris Trottier @Fediverse News Or you look around the Fediverse beyond #Mastodon. All other microblogging and macroblogging projects have much higher limits or virtually none at all. And they all support text formatting.
in reply to Jupiter Rowland

@jupiter_rowland Personally i'm using #WriteFreely for those posts, but project has a lot of bugs and i can't recommend it to anyone.

Bugs: ActivityPub is out of sync on edits, broken fonts on first load, bugged posts import etc..

Here is obvious bug which they marked "Not a bug" lol
github.com/writefreely/writefrโ€ฆ

in reply to Brian Hawthorne

@Alex0007 I've got a blog on #WriteFreely myself. It used to be on #Plume before that, but then the instance disappeared without a notice, and at that time, Plume seemed to be half-dead anyway.

Should everything else fail, I can still move the posts to #Hubzilla itself. They won't be as distraction-free, but they'll be on the same domain and project as embedded pictures.

in reply to Chris Trottier

I hope the "Paste as unformatted text" alternative is in the same package?

Fediverse News reshared this.

in reply to Per Funke

@Per Funke You won't be able to write formatted text either way. This is a read-only feature that'll let you see bold type, italics etc. in posts coming in from outside Mastodon.

And even if you could write formatted text, it wouldn't be by formatting it in Word with point-and-click and then copy-pasting it into Mastodon with all formatting.

It'd be Markdown. Markdown means **bold**, __bold__, *italics*, _italics_ etc. You'd have to "program" the formatting into your toots by hand. This isn't Word-style WYSIWYG.

But again, you won't be able to do that. You'll only be able to see it from others.

in reply to Per Funke

@Michael Gemar Those who'll nag Eugen about it will mostly be those who still "know" that the Fediverse is only Mastodon, and who think that these pretty posts must come from some modified Mastodon instances.

Those who don't will migrate to elsewhere in the Fediverse where you can format your posts. Places where all those cool formatted posts come from.

in reply to Per Funke

@Kat M. Moss I think size and growth don't matter. #MissKey is currently exploding, but from a huge influx of Japanese users.

Right now, the cool kids in town seem to be #Akkoma, #GoToSocial and good old #Friendica.

in reply to Chris Trottier

Cool. Supporting markdown format provides a simple way to increase readability.
in reply to Chris Trottier

I hope it would be implemented by Markdown, BBCode or similar, not via some "rich text" extension/app/tool

Fediverse News reshared this.

in reply to k8quinn

@k8quinn You won't be able to write it; you'll only be able to read it when it comes in from something that isn't Mastodon.
in reply to Chris Trottier

I hope it will be easy to turn off this markdown stuff. Because in other systems with automatic formatting I find it extremely frustrating to have to reformat some message that I have used dashes in and suddenly half my message is struck through. Also, clients need to provide a preview mode, because otherwise it's going to just be horrible.

Fediverse News reshared this.

in reply to Judy Anderson

@Judy Anderson Don't worry, this won't affect the way you write your toots.

It'll be read-only, i.e. it'll only concern posts coming in from projects in the Fediverse that aren't Mastodon.

Markdown support will only enable you to read this in bold type, this in italics, this with an underline, this as code etc. (Check my original post at the source.) But you still won't be able to write this way on Mastodon.

in reply to Jupiter Rowland

@jupiter_rowland the concern isnโ€™t so much toots you write getting or not getting Markdown (personally, Iโ€™d like to see the capability added eventually, but it would have to include some metadata or magic cookie at the front of the toot, becauseโ€ฆ)

โ€ฆ the big concern is the huge body of existing plaintext toots getting โ€œhelpfullyโ€ reinterpreted as Markdown, leading to, for instance, underscores in variable names getting rendered as italics, or random โ€œ*โ€s turning blocks of text italic or bold.

in reply to CarlRJ

@CarlRJ I'm actually wondering if ActivityPub transmits text formatting as Markdown. It's nice for writing, but I would have expected HTML or at least BBcode.
in reply to Chris Trottier

Huh- I thought it had this already, since I'm seeing what seems to be link & basic text formatting markup in a lot of posts. Is that some kind of accidental "support" - i.e., if your markup is minor enough it'll get ignored or just won't break stuff? Or are the instances of origin doing something special?
@fediversenews

Fediverse News reshared this.

in reply to FeralRobots

@FeralRobots The only tag which Mastodon doesn't strip away is the URL reference tag.

Bold type, italics, underline, strikethrough etc. are stripped away when they come in from other projects in the Fediverse.

in reply to FeralRobots

@FeralRobots @Sarah Brown We could try a complete run-through. Which of these can you see?

  • The list itself
  • Horizontal bars
  • URLs
  • Text sizes
  • Bold type
  • Italics
  • Underline
  • Strikethrough
  • Colours
  • [hl]Highlighting[/hl]

  • Quotes
  • Code

We could also try tables or other kinds of lists.

This entry was edited (1 year ago)

Fediverse News reshared this.

in reply to Jupiter Rowland

@jupiter_rowland
Can't see any of them. I think @goatsarah is likely right & I'm conflating my native instance with some forked instance.
in reply to FeralRobots

@Emperor Palpapeen @FeralRobots I think it's all translated to a common language in ActivityPub anyway, probably HTML.

The issue with Mastodon is that it strips everything off except <a href>.

That said, I myself consider the lack of text formatting support a minor issue in comparison with how Mastodon handles pictures in posts from outside.

Unknown parent

FeralRobots
@goatsarah
No, I'm not seeing that as bold, which really makes me wonder how it's happening.
Bold/italic is not common, but I do see it. @jupiter_rowland has explained how I'm seeing links.
@atomicpoet

Fediverse News reshared this.

Unknown parent

FeralRobots
@goatsarah
Ah I misunderstood you. I thought you were saying that was faux-bold via unicode, which was puzzling me since it obvs wasn't unicode.
@atomicpoet

Fediverse News reshared this.

Unknown parent

Helge

I see I was confused by this line in Mastodon code base.

After looking at it again, I realize there is a white space there, resulting in the link being remove. How fun.

Unknown parent

FeralRobots

@goatsarah
Tables are an interesting accessibility problem. I've occasionally tried to pitch to people that at least some tables can be designed such that they make some kind of sense if they end up just getting rendered as a series of paragraphs. But it's a rare table (that should've been one in the first place) that works *well* in that format.

@jupiter_rowland

Unknown parent

@constantine @goatsarah @h Interesting. Iโ€™m viewing this on iOS web version.

But itโ€™s a work in progress. Iโ€™m excited to see itโ€™ll happen.

in reply to Chris Trottier

I've got that in Elk already. Markdown is really fun with German. We've got gender stars (causing cursive), word part omitments with "-" (causing strike through), and (like English) omitted sounds with apostrophes, where some use gravis (`) instead (causing block quote).
in reply to Chris Trottier

wish Iโ€™d seen this before asking my dumb question about markdown in another thread.

Fediverse News reshared this.

in reply to Chris Trottier

Maybe just focus on improving pm/dm? Seeing private messages in the timeline is annoying and feels very unsafe.
Rich text? Because? Priorities, please.

Fediverse News reshared this.

Unknown parent

@Sarah Brown
You can use Friendica for that( like I do). If you want to post like on Instagram, consider Pixelfed.
@Emperor Palpapeen @Jupiter Rowland @FeralRobots

Fediverse News reshared this.

in reply to Robert Logger ๐Ÿ‡ณ๐Ÿ‡ฑ [Friendica]

Fediverse News reshared this.

in reply to Chris Trottier

Currently testing the change on my fork in a dev environment, it seems to work well, including on locally posted content! It's a bit odd that they say "remote" but in reality it's all content? But meh, just glad it seems to work well right now
in reply to AlienKnight

@AlienKnight @Chris Trottier @Fediverse News "Remote" means "from outside of Mastodon" in this context. Mastodon can't produce formatted text, so it has to come in from outside.
in reply to Chris Trottier

do you know if they're working on the mastodon.social server certificate to stop the annoying "not secure site" on the browsers?
in reply to Chris Trottier

what is incoming Rich text? I mean, I know what Rich text is (๐Ÿ’ฐ๐Ÿ’ฐ๐Ÿธ๐Ÿ™€). But where is it coming in from?๐Ÿธ๐Ÿ˜บ

Fediverse News reshared this.

Unknown parent

@constantine @m @goatsarah @h Honestly, I just want italics for book, movie, and composition titles. Using quotation marks is a sloppy stopgap that can contribute to misreading.
Unknown parent

Helge

I will take another shot at making a point that seems to be confusing. People using software other than Mastodon are already able to do various things. So for me this is in italics and this is in bold. I know that you cannot see it on Mastodon and the people on Friendica can.

Now, what does "incoming" mean in this context: Mastodon already get posts with italic, bold, titles, subtitles, lengths over 500 characters and so on. Mastodon will now also render certain HTML tags (as seen in the screenshot from Claire).

What does this also mean: Mastodon will still not render my math equations as they are embed using a math-jax script tag and require math-jax javascript library to be loaded.

in reply to Chris Trottier

hopefully there is a way to disable seeing others excessive formatting in your stream. Thereโ€™s something visually comforting about less noisy text.

Fediverse News reshared this.

in reply to Chris Trottier

Hey @Claire, do you happen to have a link for your rich text post? I'd like to see, how it renders in Akkoma.
It's great to see, that text formatting on the side of mastodon is being improved. I hope it will be compatible with other fedi software. :prettyflower2:
Unknown parent

CarlRJ
@supernovae the โ€œif you do t want it donโ€™t use itโ€ argument is naรฏve as it neatly skips over the reality that Markdown assigns meanings to characters that people were already using - if you turn it on everywhere without any trigger (metadata or some token at the start of the toot indicating Markdown is in effect) then there โ€ขwillโ€ข be unintended consequences and broken text.
Unknown parent

CarlRJ
@goatsarah @HeyLaiverd is it stripping Markdown syntax, or some internal richtext format? Does this mean that, say, the asterisks around *this* word would get stripped, or are the individual incoming posts already tagged as plaintext or Markdown, respectively, so Markdown syntax isnโ€™t โ€œfoundโ€ and โ€œhelpfullyโ€ removed from plaintext posts?

Fediverse News reshared this.

Unknown parent

CarlRJ
@goatsarah @HeyLaiverd fair enough, thank you. I would welcome Mastodon incorporating a fairly limited markup language like Markdown (with, apparently, translations on ingress/egress), as Iโ€™ve found this very useful in other contexts, but Iโ€™m leery of more full-blown rich text, which often causes people to get too carried away with formatting, fonts, colors and such, rather than focusing on the message.

Fediverse News reshared this.

Unknown parent

CarlRJ
@supernovae an argument could be made for limiting the scope (i.e. 500 plaintext characters), for something youโ€™d like to see scale to something like Twitter size - when you sit down to 100 new toots, having them at tweet-equivalents is much less to comb through than if itโ€™s the equivalent of 100 web pages, with all sorts of stuff going on - this would also have implications for sending all that data around. But I can also see that something more would be helpful.
Unknown parent

CarlRJ
markdown test
@sanji FFWIW, the first star on the emphasis line ought to precede the โ€œeโ€, not thenโ€-โ€œ, Iโ€™d youโ€™re going for standard Markdown.
Unknown parent

Aswath Rao

@goatsarah Since the receiving node may not know the format or form of the content (like book review), why not it proxy & embed the content in the timeline. What will be lost?

@atomicpoet @carlrj @HeyLaiverd

Unknown parent

Jupiter Rowland

Fediverse News reshared this.

Unknown parent

CarlRJ
@constantine @m @goatsarah @colorblindcowboy @h โ€œWelcome to Mastodon 2025, where every toot looks like a ransom note glued to the floor of a disco!โ€
in reply to lunchy

@lunchy @Chris Trottier @Fediverse News It was composed with Markdown on a test instance. But ActivityPub transmits it as Rich Text.

And Markdown composition will stay limited to test instances and projects outside Mastodon that use Markdown for text formatting. It won't be generally rolled out to all Mastodon instances.

In other words, you'll be able to see text formatting, but you won't be able to format text yourself.

in reply to Chris Trottier

@quephird I find it curious how our computers all support UTF-8 yet the input methods are so shot that we need complex mark up language to enter in more typography then the 7-bit ASCII allows. I think the tech skipped a step somewhere.

Fediverse News reshared this.

in reply to sukima :verified:

@sukima @quephird replacing a word marked up by underlining, with Unicode underlined characters is not the right path to go down. The โ€ขonlyโ€ข thing that can โ€œeasilyโ€ parse those characters by default are human eyeballs. Those who need to use screen readers plus any software that searches the text will have trouble with those underlined characters.
in reply to CarlRJ

@carlrj @quephird in very much not suggesting that not suggesting any solution. I was merely contrasting how we got here and that technology has failed in something to basic as to need such awkward solutions anyway.
in reply to sukima :verified:

@sukima @quephird we have 95 printable characters in the ASCII set, give or take, which isnโ€™t too hard to work out on a 100ish key keyboard. What would make a better direct input solution for any of the tens of thousands of Unicode characters? Adding keys doesnโ€™t scale.

We have an enormous number of symbols that it is good to be able to uniquely record in computers, but only a few handfuls we really need day-in/day-out. But Iโ€™m interested in alternate input solutions.

in reply to CarlRJ

@carlrj @quephird Still kinda thinking inside the box. Why do we need a solution? It is ok to point out the awkward solutions we have to a problem that if history played out differently we would have. Considering that we are the music makers and we are the dreamers of dreams how did we get to a point where markdown is the solution to a typography problem? Maybe things could be different.
in reply to sukima :verified:

@sukima @quephird but Markdown is not the solution to a typography problem, itโ€™s the solution to a semantic problem - you want to indicate that โ€ขthese wordsโ€ข are being emphasized, not that those individual letters are each being emphasized. There โ€ขisโ€ข a difference, which, as mentioned, gets highlighted by thins like screen readers and programs reading text.

Markdown is not a great solution, but itโ€™s a good solution to use while seeking a better one.

in reply to CarlRJ

@carlrj @quephird 1) You just emphasized just fine without Markdown 2) It has been 50 years, why are we as a technology community still //waiting// on a solution better than Markdown? โ€”This is a bit of a devilโ€™s advocacy but I still think we can express ourselves just fine with plain text without needing fancy things like RichText. It feels weird to me.
in reply to sukima :verified:

@sukima @quephird (1) using โ€ข around words for emphasis is not a standard, and, just like using individuallly underlined letters, cannot be easily understood by software. Markdown can - simply because of widespread adoption, itโ€™s a standard of sorts.

(2) 50 years since what? Computers have been around far longer, Markdown โ€ขfarโ€ข less long.

in reply to CarlRJ

@carlrj @sukima @quephird Iโ€™m still salty because I thought weโ€™d decided long ago that surrounding text with asterisks meant BOLD. But Markdown breaks that by treating it as EMPHASIS, which usually gets shown as ITALICS. As everyone knows, italics should be represented by surrounding the text with //.

#xkcd927 xkcd.com/927/

in reply to Kevin Davidson

@MetalSamurai @sukima @quephird itโ€™s a little trickier - in Markdown, single asterisks, or single underscores, mean italics, while double asterisks mean bold. I canโ€™t recall ever seeing italics done with slashes. Looks too much like Unix pathnames.
in reply to CarlRJ

@carlrj @sukima @quephird Again, leading and trailing underscores mean UNDERLINE*. I was so angry when I first heard about Markdown (from peopleโ€™s glowing reports about how wonderful, simple and obvious it was). Just took existing conventions and scrambled them up for no reason.

* of course if you really wanted to underline ironically youโ€™d follow each individual character with the ^H_ sequence.

in reply to Kevin Davidson

@MetalSamurai @sukima @quephird itโ€™s a shame that your fork of the Markdown code to change it to what you believe is the proper syntax, never caught on.

It wasnโ€™t some big committee that โ€œgot it wrongโ€, it was a guy, who did it for his own use, so he could write blog posts as plain text, and it caught on.

You can write your own and attempt to win Markdown users over to your side, but itโ€™s an uphill battle. Common usage often wins over โ€œbetterโ€ (see QWERTY vs Dvorak).

in reply to CarlRJ

@carlrj @sukima @quephird The conventions Iโ€™m describing were in widespread use long before Markdown. If there are any text corpuses of Usenet posts or mailing lists from the 90s youโ€™d find them in use everywhere, alongside old style ascii smileys. Markdown has now drowned out the old *bold* /italic/ _underline_ and Iโ€™m apparently now an old guy shaking my fist at the sky demanding the youngsters get off the lawn.
in reply to Kevin Davidson

@MetalSamurai @carlrj @quephird I feel your pain. And the mansplaining for Markdown is infuriating. I still prefer ROT13 for spoilers. Sigh, how far we have fallen.
in reply to sukima :verified:

@sukima @carlrj @quephird I lost the Markdown fight long before Iโ€™d ever even heard of Markdown. But I was also on the losing side in the LaTeX vs WYSIWYG word processor wars, no matter how much I shouted โ€œwhat you see is ALL you get!โ€
in reply to sukima :verified:

@sukima @carlrj @quephird A long time ago I wrote code in Occam to use compressed TeX fonts for on screen graphics on a Transputer based massively parallel supercomputer. Gained an appreciation for Donald Knuth and his coding skills doing that.
in reply to CarlRJ

@carlrj @sukima @quephird I must have written hundreds of Man pages, so I used to know the man nroff macros inside out. I thought it wasted vertical space, which was a pain as most terminals only had 24 rows.
in reply to Kevin Davidson

@MetalSamurai @sukima @quephird oh, it wasted lots of vertical space. But I could also count on it being preinstalled on every system I sat down in front of.
in reply to Kevin Davidson

@MetalSamurai @sukima @quephird I was on Usenet quite a bit in the 80โ€™s and 90โ€™s. I donโ€™t recall a lot of slashes being used for italics. Gruber invented something for his own uses that caught on, and nobody jumped in with a clearly better solution, so this is what we have.
in reply to CarlRJ

@carlrj @MetalSamurai @sukima @quephird
I've been sending messages online since mid-70s. Only ever saw/used back then
*big emphasis* (cf Bold)
_lesser emphasis_ (cf Underline)
Slashes? Nope.
in reply to Kevin Davidson

@MetalSamurai @AlisonW @carlrj @quephird I started with Usenet in the 90's and I remember people using slashes and other forms of markup in ASCII for all kinds of emphasis. I even remember lots of <g> used for grin/joke. And it is amazing how this thread devolved into semantics instead of discussing the inability for technology to be expressive by design in the first place.
in reply to sukima :verified:

@sukima @AlisonW @carlrj @quephird Itโ€™s disappointing that nearly 40 years later we are no better at presenting meaningful styled text.

On the other hand itโ€™s entirely on brand for a discussion mentioning Usenet to go wildly off topic. All thatโ€™s left is for us to divide up into Emacs vs Vi and then declare if we are for or against Heinlein.

in reply to Kevin Davidson

@MetalSamurai @sukima @AlisonW @quephird vi, and itโ€™s offspring Vim, is the one true editor, at the feet of which all other editors grovel.

And whatโ€™s left is for the thread to be Godwined by getting into a discussion of mid-last-century German political organizations.

Markup can be easy to write, easy to read, or easy for computers to work with unambiguously. Unfortunately, you only get to pick two out of the three.

in reply to Kevin Davidson

@MetalSamurai @sukima @AlisonW @carlrj @quephird

Emacs! (but vim for some things, particularly over ssh).

Heinlein was an excellent writer, with unexcellent political views.

And yes, markup is good. Obviously TeX/LaTeX would be the best approach.

in reply to CarlRJ

@carlrj @drgeraint @sukima @AlisonW @quephird Emacs was my window manager, my IDE, my Mail reader, Usenet reader, address book, ftp client and more. In server mode it ran all the time so gnuclient in any terminal window would connect with all my state intact.
Vi is what you were forced to use before you could get Emacs installed. Or ex on systems with broken Termcap. Yuck.
in reply to Kevin Davidson

@MetalSamurai @drgeraint @sukima @AlisonW @quephird vi was installed on basically every system (Iโ€™m not sure Iโ€™d call it a Unix system if it didnโ€™t have vi), and for text editing, it requires the fewest number of keystrokes for editing and rearranging text. Sure, in emacs, you didnโ€™t have to go into insert mode, but that meant everything else took more characters, more shift key use, more control key use, etc.
in reply to CarlRJ

Yeah, I was always a bit guy for those reasons: it was everywhere and it wasnโ€™t bloated. I want to edit a file, I donโ€™t need a full operating environment. :โ€™

E ventually
M allows
A ll
C omputer
S torage

in reply to CarlRJ

@carlrj @drgeraint @sukima @AlisonW @quephird Working out the minimal set of key presses to achieve a complicated edit in Vi I suppose is intellectually satisfying. But I find I spend more time thinking which offsets the gain in typing time.
My fingers know the Emacs keybindings without having to think. And they work in tcsh/bash/zsh and eslewhere as well.
in reply to Kevin Davidson

@MetalSamurai @drgeraint @sukima @AlisonW @quephird see I no longer think about how best to get to a certain point in a file, in vi, it just comes naturally. Perhaps not the absolute most efficient way, but pretty close.

tcsh/bash/zsh support vi keybindings as well (โ€œset -o viโ€ in bash). I know Emacs bindings well enough to use at the cmd line as needed (bonus, Emacs bindings work in Mac text fields).

in reply to Geraint

@drgeraint @sukima @AlisonW @carlrj @quephird Of course you can edit files remotely over ssh from inside Emacs.

I think Iโ€™ve read everything Heinlein wrote. Probably gave me some useful thinking tools to articulate why I disagreed with some of his ideas.

in reply to sukima :verified:

@sukima @quephird the notion of adding spaces between words doesnโ€™t go back as far as writing does. Periods, exclamation points, and question marks were added along the way. Underlining the occasional word or phrase has been a thing for hundreds of years. Bold and italics for emphasis is just a natural extension in the same line.

Thereโ€™s a lot not to like about RichText (fonts, colors, etc.), but italics, bolding, bulleted lists, are all things that can improve text.

in reply to CarlRJ

@carlrj @sukima @quephird

we just need another fifteen keys for bitplane shifting, and an optional on-screen popup to show what each key would generate with current bitplane shift combination. : )

in reply to CarlRJ

@carlrj @sukima @quephird

er, ah, those of us with fifteen feet can, I guess, but that only works for us.

in reply to Chris Trottier

excellent! I use #elk as my client for the fediverse and recently I experimented with it's built-in rich text feature in a post which successfully showed up in elk, however, the rich text didn't show up in #mastodon

Fediverse News reshared this.

in reply to Chris Trottier

oooh lists! Love it. Iโ€™m a veteran of the List app and it was my favorite social media app. Love making lists!

Fediverse News reshared this.

in reply to Chris Trottier

Next steps: spreadsheet and presentation!
Fantastic to see great foundational and necessary features finally coming to life!

Fediverse News reshared this.

in reply to Chris Trottier

Funny to think:
Newsgroups and early mailing lists were all plaintext, so people came up with conventions like using asterisks and underscores.

Web forums were able to display rich text, and they used markup to implement it.

Early social media like LiveJournal and such supported rich text via raw HTML

Twitter was designed to fit in an SMS message, so it was plain text.

And everyone went back to using asterisks and underscores. Plus abusing Unicode lookalike chars.

Fediverse News reshared this.

in reply to Kelson's Sorta Old Account

@KelsonV I always think back to how we behave with IRL pens/pencils. If we have different colours weโ€™ll use them. Otherwise weโ€™ll underline and capitalise and draw squares and embolden.

Weโ€™ll use whatever visual components we have available so long as theyโ€™re easy to use and โ€œat handโ€.

Unknown parent

Emperor Palpapeen

@jakob @jupiter_rowland @FeralRobots @goatsarah my experience was bad. Performance issues, uploading issues, browser bogged down by it.

Maybe in a year or so I will look at it again.

Unknown parent

Jupiter Rowland

@Jean-Daniel, aka Sanji @Chris Trottier Same result on Hubzilla as @๐—๐—ฎ๐—ธ๐—ผ๐—ฏ :๐—ณ๐—ฟ๐—ถ๐—ฒ๐—ป๐—ฑ๐—ถ๐—ฐ๐—ฎ: ๐Ÿ‡ฆ๐Ÿ‡น โœ… has on Friendica.

Maybe your instance renders Markdown internally, but it doesn't translate it to Rich Text for other ActivityPub instances/projects.

Now I'd like to hear from someone on (streams)...

in reply to Emperor Palpapeen

@Shrexios
I just haven't had the bandwidth to play with any of these, yet. Most are on stacks I'm not familiar with & my day job (which is 40% Wordpress & 50% keeping up with the devops stacks one needs to maintain a large org's public-facing Wordpress site) sucks up most of the brain cells I'm willing to allocate to web app experimentation right now.

I'm hoping in a yr or so they'll still be around.

@jakob @jupiter_rowland @goatsarah

โ‡ง