I’m sorry, I didn’t explain this properly and that has led to a misunderstanding of my actual proposal. I was not intending for the title to be a special field unless the client explicitly understood my syndication format.

The original twtxt format specification gives no special meaning to the tab character, excluding the one that separates the timestamp from the text. I was under the impression that the tab character could appear in a twt so it would be interpreted as follows, replacing ␉ with a tab character.

2022-09-22T14:53:26-07:00␉Bringing Back a Useful Browser Feature With a Bookmarklet␉https://mckinley.cc/blog/20220922.html
#^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
#|                        |
# ```- Timestamp             `- Message

Although, I just remembered that the tab character is technically a control code, so it shouldn’t be allowed.

@eaplmx@twtxt.net I wasn’t making a criticism, I was just pointing out the difference in the format. I agree, there’s some great stuff on there.

@prologic@twtxt.net $ nc kyoko-project.wer.ee 1234 in your terminal, it’s a remake of Among Us as a multiplayer text adventure.

@prologic@twtxt.net Referenced links also work on the Web client, but I tried both CommonMark syntax options for the horizontal rule and only one worked on Goryon.

This is exactly what I’m talking about. We should have a concrete specification so Markdown can be rendered consistently between client implementations.

I think I broke it, though, because I started a game alone and then accidentally pressed ctrl+c. When I try to log back in, it says there’s a game in progress and I can’t start a new one. Sorry about that…

@akoizumi@social.kyoko-project.wer.ee That looks fun. I’d play if we could get some more people in the game.

Nope, no horizontal rule. What about referenced links?

My website

@prologic@twtxt.net I don’t know if a metadata field is strictly necessary. I think there ought to be a defined set of syntax that all clients with Markdown support can be expected to handle in the same way. CommonMark maybe? It looks like Yarn supports most of CommonMark already, though I’ve never seen a horizontal rule. Let’s try it:

Some text here

Of course I pick the day before simple.css gets merged into main to get a new Ladybird screenshot. Here’s one post-merge.

@akoizumi@social.kyoko-project.wer.ee It looks like that feed uses TIMESTAMP\tTITLE: PERMALINK which would be harder to parse programmatically.

This discussion has me thinking of a serious syndication format built on top of twtxt that could be implemented in normal feed readers. It would be limited, but extremely easy for a Webmaster to implement. Users could also receive updates with a normal twtxt client. I think there could be some utility in it.

For a real feed format I would like to have a clear separation between titles and content. And more options for the content. Plaintext and HTML at least.

I don’t think it’s a very good idea to include content when using twtxt as a syndication format. Anything based on twtxt, in my opinion, should retain the spirit of the original specification, especially readability by humans and machines. 10K of HTML in one line absolutely breaks human readability.

What about TIMESTAMP\tTITLE\tPERMALINK, like the following?

2022-09-22T14:53:26-07:00	Bringing Back a Useful Browser Feature With a Bookmarklet	https://mckinley.cc/blog/20220922.html

@lyse@lyse.isobeef.org

Twtxt is plaintext, but lots of folks (me included) actually use markdown in their yarns. However, the actual format being used is not advertised anywhere.

That’s a really good point. We should formalize a Markdown flavor as a format extension on https://dev.twtxt.net/.

yarnd appears to use gomarkdown with a few extensions. I’m not sure what else gomarkdown translates by default.

There should definitely be a concrete specification on what syntax should be supported by twtxt clients with “Markdown” support. cc @prologic@twtxt.net and @darch@neotxt.dk

@tkanos@twtxt.net This is really interesting stuff. Do you plan on sharing the code, or at least a more detailed write-up of your process?

@eaplmx@twtxt.net I think twtxt is a fine feed format, especially if you’re allergic to XML.

LibWeb font handling has greatly improved. We’re no longer stuck with that terrible bitmap font. It looks like there are still a few font-related issues to iron out, but here is what the Yarn discover page looks like on Ladybird. A huge improvement in only a week, though it really can’t decide where it should put that search box.

@movq@www.uninformativ.de I use it in some of my blog posts for inline code snippets so they don’t get wrapped where it would make it hard to read. Other places, too, but I can’t remember right now.

A nice chat tonight with @prologic@twtxt.net, @ocdtrekkie@twtxt.net, and @darch@neotxt.dk. Some things we talked about:

• Markdown isn’t rendered to HTML in Atom feeds (#989)
• A look at @darch@neotxt.dk’s branch to replace Pico.css with Simple.css
• 100 monthly active users on yarn.social
• Sandstorm proxy authentication for yarnd (Allows one set of credentials across programs hosted on Sandstorm)
• Sandstorm support for Tube (#26)
• Future improvements to Sandstorm

@movq@www.uninformativ.de I use the no-break space all the time, I only just learned about its horizontal brother.

@prologic@twtxt.net are we having the call tonight?

@abucci@anthony.buc.ci @lyse@lyse.isobeef.org I hope the bookmarklet can be of use. :)

@darch@neotxt.dk I’d like to add pixelblog to groovy-twtxt but I would rather not include software without a formal license.

@tkanos@twtxt.net I’m 6th, 57th, and 1280th. What metric did you use, total number of mentions? Also, is this supposed to be a continuation of mdom’s project of the same name?

@eaplmx@twtxt.net That’s the surprise. Take a look at view-source:https://mckinley.cc/blog/atom.xml

You know, I thought you had to use a Duopoly browser if you wanted client-side XSLT but I just learned WebKit supports it as well! That means it works on Otter Browser and WebPositive. Safari too, probably, but we don’t talk about that one.

@lyse@lyse.isobeef.org Thank you, that’s a great compliment. I’m quite proud of that stylesheet, especially the bit that converts RFC 3339 timestamps to the friendly date format I use.