home.social
Sign in Create account

#richtext — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #richtext, aggregated by home.social.

  1. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  2. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  3. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  4. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #long #lists #groups #cwlong #richtext #hubzilla
  5. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  6. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  7. रञ्जित (Ranjit Mathew) @[email protected] ·

    “Why The Heck Are We Still Using Markdown?”, Burak Güngör (bgslabs.org/blog/why-are-we-us).

    Via HN: news.ycombinator.com/item?id=4

    On Lobsters: lobste.rs/s/nn403y/why_heck_ar

    #Markdown #HTML #Text #Rants #CommonMark #RichText #Markup

    #markdown #html #text #rants #commonmark #richtext
  8. The Eclectic Light Company [Unofficial] @[email protected] ·

    Even richer text editing with DelightEd version 2.5

    fed.brid.gy/r/https://eclectic

    #macs #technology #updates #delighted #richtext #rtf
  9. Mike @[email protected] ·

    Can someone point me to a #RichText post on #Mastodon so that I can test a new feature?

    #richtext #mastodon
  10. Princesa Jujuba FedIverso 👸 @[email protected] ·

    GENTE A MONARCA CONSEGUIU. Depois de sofrer 30 minutos no HTML e Markdown, DESCOBRI que o bagulho era o RICH TEXT. Agora tô com estilo de postagem COMPLETO, posso postar até link, formatar text, colocar enlace, ser feliz. Muito burrx? Não, MONARCA DETERMINADA. 👑💅
    #PrincesaJujuba #RichText #Tumblr #Conquista #MonarcaDeterminada

    #princesajujuba #richtext #tumblr #conquista #monarcadeterminada
  11. Andrea 📚 @[email protected] ·

    Test Post auf deutsch.

    Weil ich gesehen habe, dass ich hier (also mit Mona 7) wohl Text Fett, kursiv, unterstrichen oder auch darstellen kann. Wird das per Screenreader eigentlich erkannt? 🤔. Wäre ja ne feine Sache, oder?

    • Listen gehn auch
    • muss jetzt nochmal ne Zeile hinzufügen

    ⁃ auch Listen mit Spiegelstrichen
    ⁃ Ne Liste braucht natürlich mehr als nur 1 Zeile

    1. nummeriert geht auch
    2. Zahlen sind immer gut

    #RichText getmona.app/rich_text/27716611

    #richtext
  12. The Eclectic Light Company [Unofficial] @[email protected] ·

    Explainer: Text formats

    fed.brid.gy/r/https://eclectic

    #macs #technology #doc #html #pages #richtext
  13. The Eclectic Light Company [Unofficial] @[email protected] ·

    Explainer: Text formats

    web.brid.gy/r/https://eclectic

    #macs #technology #doc #html #pages #richtext
  14. The Eclectic Light Company [Unofficial] @[email protected] ·

    Explainer: Text formats

    fed.brid.gy/r/https://eclectic

    #macs #technology #doc #html #pages #richtext
  15. The Eclectic Light Company [Unofficial] @[email protected] ·

    Explainer: Text formats

    fed.brid.gy/r/https://eclectic

    #xml #word #webarchive #utf8 #text #rtfd
  16. The Eclectic Light Company [Unofficial] @[email protected] ·

    Podofyllin 1.5 beta can export PDF to RTF

    fed.brid.gy/r/https://eclectic

    #macs #technology #beta #pdf #podofyllin #richtext
  17. Hacker News @[email protected] ·

    Rich Text, Poor Text (2013)

    laemeur.sdf.org/words/D29.html

    #HackerNews #RichText #PoorText #2013 #TechTalk #WritingCommunity #DigitalLiterature #HackerNews

    #hackernews #richtext #poortext #techtalk #writingcommunity #digitalliterature
  18. Sami Lehtinen @[email protected] ·

    @envs Beep beep, bad news! I think the envs cryptpad richtext editor is broken. I’ll share the full log if necessary, but this is where the problems start:

    Content-Security-Policy: The page’s settings blocked the loading of a resource (media-src) at data: because it violates the following directive: “media-src blob:” pad
Content-Security-Policy: The page’s settings blocked an inline script (script-src-elem) from being executed because it violates the following directive: “script-src 'self' resource: https://pad.envs.net” utils.js:42:10

    #cryptpad #richtext #editor #error #broken #CSP

    #broken #csp #cryptpad #editor #error #richtext
  19. Dendrobatus Azureus @[email protected] ·

    I went to search for a site where I can post content for free. I found one, all they do is put some ads and if you are as me you will have an ad block running already.

    What I did not expect is a full-blown site builder with everything, including kitchen sinks, 32 channel mixing consoles, 18" subwoofers and full range speakers :)

    All I need is a place where I put my markdown formatted text directly and get it published immediately.

    Now I need to wade through the system to find where I can put in straight markdown text, no formatting from them , no YSWYG editor

    #markdown #mastodon #richtext #formatting

    #Music #Audio #Bass #Guitar #SoundEngineering #Joyo #Pedal #Console #Yamaha #Behringer #FX2000

    #markdown #mastodon #richtext #formatting #music #audio
  20. Dendrobatus Azureus @[email protected] ·

    I just ran

    `wc -m ~/gate/pgm/hugo/quickstart/content/posts/fifth-post-fx2k-reportI.md`

    `10034' was the output!

    I just saw in this post that markdown is not officially suported on mastodon.

    @stefano what is the case on this server? I have md text that I want to display with only unsorted and sorted lists and formatting of bold italic

    fedi.tips/is-mastodon-compatib

    #markdown #mastodon #richtext #formatting

    #Music #Audio #Bass #Guitar #SoundEngineering #Joyo #Pedal #Console #Yamaha #Behringer #FX2000

    #music #audio #bass #guitar #soundengineering #joyo
  21. Simon Jones @[email protected] ·

    What open source rich text editors do people recommend?

    We've used CKEditor in the past, but we've had some issues with customising it to get more accessible HTML (and I see they are moving towards a commercial model).

    I'm aware of quilljs.com (but never used it). Any recommendations appreciated! #WebDev #RichText

    #webdev #richtext
  22. Fedi.Tips @[email protected] ·

    Mastodon will display rich text such as underlines, bold, italics etc if they are in posts from other kinds of Fediverse servers.

    However, Mastodon itself doesn't support creating rich text posts unless you're on a server that uses unofficial customised software such as Glitch Mastodon.

    You can find out more about Mastodon and rich text here:

    ➡️ fedi.tips/is-mastodon-compatib

    There are nice servers running Glitch Mastodon listed at fedi.garden/tag/glitch-mastodo

    #FediTips #Mastodon #RichText #Markdown

    #feditips #mastodon #richtext #markdown
  23. Jupiter Rowland @[email protected] ·
    @ᴚ uɐᗡ It's called a quote. Standard feature on Friendica, Hubzilla (where I am), (streams), the now-deceased rest of the family, Misskey and all its forks etc., basically everywhere that isn't Mastodon.

    Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
    [quote]if the process is really that involved and if they can fix it[/quote]

    (streams) also has ways of doing that with Markdown or HTML.

    There are various different ways of getting that code, also depending on whether one replies to a post or a comment.

    ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.

    Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText
    #cwfediversemeta #textformatting #fediversemeta #cwlongpost #cwfedimeta #friendica
  24. sudokill @sudokill ·

    Anyone who want to define a new language, based on , but for rich-text document ?

    For example :
    // Center that line
    __underline__
    "Text in red"{}
    And of course, a zip file '. mdz' to encapsulate text and images.

    I use this kind of syntax in my own linux editor, and it works really well.

    If you want to contribute, have some ideas.... : codeberg.org/sudokill/markdock

    #markup #markdown #red #xwriter #markdock #editor
  25. David Blue ⁂ ∆ @[email protected] ·

    FB13172586 (Append to Note Siri Shortcuts Action Disfigures Rich Text Input)

    This issue has been present since iOS/iPadOS 17 Developer Beta 1 and continues to be present as of the Release Candidate.

    #apple #applefeedback #ios #shortcuts #richtext #ios17 #ipados17 #automation #applenotes

    #apple #applefeedback #ios #shortcuts #richtext #ios17
  26. Antonio Bueno @[email protected] ·

    @am1no The conversion from #RichText to #Markdown is pretty terrible in iOS 16.x but if you run this #shortcut you’ll generate three notes with diverse format:

    icloud.com/shortcuts/0159e21ec

    If you run my previous shortcut with those three notes, only the lists and the links survive:

    icloud.com/shortcuts/7bd980075

    #richtext #markdown #shortcut
  27. Jupiter Rowland @[email protected] ·
    CW: CW: long (almost 1,700 characters, mostly structured as a list), Mastodon vs non-Mastodon meta
    I'm wondering...

    What if someone on #Mastodon started a campaign for defederating everything in the #Fediverse that isn't Mastodon?

    Reasons:
    • users of these projects keep shoving them into the faces of Mastodon users
    • they think their projects are better than Mastodon
    • they keep bragging about what their projects can do that Mastodon can't
    • they spam Mastodon timelines with #LongPosts with over #500Characters
    • they pester Mastodon users with their #RichText #TextFormatting
    • they even use text formatting that Mastodon doesn't support, that must be intentional
    • their mentions look weird because they're different from Mastodon mentions
    • or they don't mention anyone at all when replying
    • they can #FullTextSearch Mastodon already now
    • they can make #QuoteToots of Mastodon toots, and nothing can stop them
    • they rarely add alt-text
    • they don't add content warnings because they don't have instance rules that demand so
    • or they don't add content warnings because they claim that they'd allegedly got a better way of handling them, and the content warning field was actually for something else
    • they never mark their images sensitive
    • not a single one of their instances has signed the Mastodon Covenant
    • you can't reach the admins of their instances
    • or if you can, and you report a user for some of the stuff above, the admin claims the user hadn't done anything wrong
    • it confuses and disturbs newbies when they find out that the Fediverse is not only Mastodon
    • it makes the Fediverse too complicated if not everything is Mastodon


    If you actually find this a good idea, keep in mind that defederating an entire decentralised project is a game of Whack-a-Mole.
    #textformatting #fulltextsearch #500characters #quotetoots #fediverse #longposts
  28. Jörn Franke @[email protected] ·

    @digitalcourage provides a @cryptpad instance - collaborate with others without disclosing data to a cloud provider #privacy #e2e #encryption #word #spreadsheet #diagrams #form #survey #slides #richtext #code

    cryptpad.digitalcourage.de

    #privacy #e2e #encryption #word #spreadsheet #form
  29. Jupiter Rowland @[email protected] ·
    @maegul @Jeff Sikes @Kainoa @Chris Trottier This would have to happen on the server side. And this, in turn, would work the best if it happened directly on the instance servers, and if it was part of the #Fediverse projects themselves.

    We've seen what happens when you rely on a third party. It tends to lean towards something centralised, either because someone deliberately only designs a centralised service for it, e.g. #Mastodon full-text search, or because nobody but the devs can be bothered to run an instance, e.g. #Guppe.

    Also, decentralised third-party services will have to be connected to Fediverse instances by the admins manually because the admins will have to decide which instance to connect. Many admins won't take that step at all because they've stopped reading the manual the very moment their instance started working reasonably well, and so they don't even know that they have to connect to such a service.

    That said, the Fediverse already speaks one common formatting language, and that's #RichText. #CalcKey translates the #Markdown in out-going messages to Rich Text. #Hubzilla translates the #BBcode in out-going messages to Rich Text. #Streams translates Markdown, BBcode and #HTML to Rich Text. And so forth.

    Also, translation between message formats will remain half-useless as long as certain projects show a severe lack of capabilities of displaying messages, and this won't change anytime soon, if ever.

    Like it or not, #Mastodon fans, but Mastodon is the worst offender. It can't have more than four images in one post, and it can't embed images within the text. All stuff that has been possible on projects older than Mastodon even before there was Mastodon.

    On #Hubzilla (and not only there, but just to take one example), I can design any regular message like a blog post:
    Text block 1
    Image 1
    Text block 2
    Image 2
    Text block 3
    Image 3
    Text block 4
    Image 4
    Text block 5
    Image 5
    Text block 6
    Image 6
    Text block 7
    Image 7
    Text block 8
    Image 8
    Text block 9

    This is perfectly normal. And this is perfectly legit. #Friendica, Hubzilla and #Streams were deliberately designed to make this possible. And while Hubzilla has an optional extra functionality for long-form articles, Friendica and (streams) only have this one way of long-form posting. So, again, this is normal and legit and intentional.

    On Mastodon, however, the very same post looks like this:
    Text block 1

    Text block 2

    Text block 3

    Text block 4

    Text block 5

    Text block 6

    Text block 7

    Text block 8

    Text block 9
    Image 8 | Image 7
    Image 6 | Image 5

    The images are ripped out of their context, reversed in their order, and only four even make it into what Mastodon displays.

    The only thing a "translator" could possibly do here is put the images in the correct order. Still, only four would make it onto Mastodon timelines due to Mastodon's limitations, only that it'll be the first four instead of the last four. And also due to Mastodon's limitations, they will still end up after the end of the post instead of embedded between text blocks where they belong.

    In the opposite direction, from Mastodon to Hubzilla, a "translator" could be a bit more useful. Currently, when a Mastodon toot with multiple images appears on Hubzilla, the images are put ahead of the text and in reverse order. What the "translator" could do (unless Hubzilla introduces that first) is embed the images at the end of the post in "reverse reverse" order. I'd suggest to also resize them (non-destructively; Hubzilla does that by default with its own images) so that four of them can be shown in a 2x2 arrangement just like on Mastodon, but on Hubzilla, that would cost them the alt-text.
    #fediverse #friendica #mastodon #richtext #markdown #hubzilla
  30. Steve Frenzel @[email protected] ·

    When using @astro and #storyblok: Does anyone know if it's possible target the children of an element containing #RichText?

    I'm able to target the "content" class shown in the screenshot, but anything within it is not reachable. I assume it's because the content isn't ready yet but Astro is done with compiling already?

    The purpose is to style the content of my blog post. Any help and boosts appreciated, thank you in advance! 🙌

    #astro #html #css #JavaScript #WebDev #frontend #WebDesign

    #webdesign #frontend #webdev #javascript #css #html
  31. Aljoscha Rittner (beandev) @[email protected] ·

    Oh, das ist toll. Eventuell werden nicht alle begeistert sein, aber ich freue mich sehr auf das neue Feature von #Mastodon :mastodon:.

    Es wurde nun implementiert, dass #RichText #Formatierungen teilweise von der Mastodon-Instanz akzeptiert und in Clients angezeigt werden. Kommen also von anderen Services Auszeichnungen, wie Fett, Kursiv, Code oder auch Listen, werden diese auch tatsächlich angezeigt. :awesome:

    Bisher hat Mastodon fast alles in Plain Text (ausgenommen URLs) gewandelt.

    #formatierungen #richtext #mastodon
  32. sudokill @sudokill ·

    Xwriter V0.4.1 is out

    This release contains :
    1. Files inclusion with the syntax : {{include filepath/filelink}}
    2. Bug fix/User-interface improvement
    3. Markdown archive .mdz works with more than 1 markdown file at the root ( tested with github zip file )

    codeberg.org/sudokill/Xwriter

    #xwriter #markdown #markdock #richtext #richtexteditor
  33. sudokill @sudokill ·

    In the next release of coming soon, I changed 2 rules :
    1. HTML alias as :
    `Text`{serif ...}
    2. Paragraph indentation as :
    |1/2/3Tabs+Text

    These syntax are just better in plain-text and are closer to the syntax already used in pandoc

    #xwriter #red #markdown #markdock #editor #richtext
  34. GNU/Linux.ch @[email protected] ·

    Dokumente gemeinsam online bearbeiten mit CryptPad

    Ein Erfahrungsbericht, wie man Google Docs durch freie Lösungen ersetzen kann.

    #Google_Docs #CryptPad #RichText #Mobile

    gnulinux.ch/dokumente-gemeinsa

    #mobile #richtext #cryptpad #google_docs