#wdu6cca eaplmx > Related with my current conversation, what do you think of using twtxt.txt as a format for feeds?

@mckinley I guess I didn’t say it correctly.

I didn’t know about that page, it’s cool!

About how do they use Twtxt as a feed, I agree on the problem you mention, and of the lack of a convention (unless we use the title/subject as someone suggested later) for automated parsing

#ybjlgha mckinley > 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.

Agree with @lyse here too 👌 It adds little value to the spec when we already have mechanisms to share titles by convention.

#oa6727a prologic > Hello Google

@darch As I said in the issue, I’m guessing Simple CSS doesn’t have any styles for modal dialog(s)? 🤔

Also as an aside, I realied I can actually turn off Link Verification and Set my preference to Original Media, so at least there’s a work-around on per-user Settings until we fix this 👌

#adrpwna darch > @prologic I made a new PR (#998) that I hope will fix the issues you have pointed out: - Link Verification not working (due to missing modal from pico.css) - Lightbox not working (due to missing modal from pico.css) - In-reply-to now only show max 3 lines of the root post

@darch You need to rebase it like I showed you.

#ybjlgha mckinley > 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.

@mckinley we already got a title field in form of (subject) – it’s just hidden here on yarn by design

I agree with @lyse on this. It is outside the scope of twtxt as a microbloging protocol to start including more formel metadata fields such as titles

@prologic I made a new PR (#998) that I hope will fix the issues you have pointed out:

  • Link Verification not working (due to missing modal from pico.css)
  • Lightbox not working (due to missing modal from pico.css)
  • In-reply-to now only show max 3 lines of the root post

But the “(…) pull request has changes conflicting with the target branch.”

#ybjlgha mckinley > 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.

@mckinley Even though I miss a title for general purposes, I’m not sold of cramming it into twtxt. It’s just not made for it. To only announce new articles, that format would work, though. It’s basically what some people already do, except a space rather than a tab is used between the title and link.

#j6ldm5q prologic > @darch Also the pop-up when you click on external links in a Twt is broken. I tried to for example in the Twt (screenshot attached) and it didn't work :/

@prologic The lightbox is also using the modal feature from pico.css…

#sax4t6a eaplmx > For people born after the 90s (no one here I suppose), this was Active Desktop: Instead of a static image, show a Dynamic Web page refreshed every X minutes. Good memories of the old .com web portals of that age

@eaplmx Ahh, right, that’s it! 😲 🧓

#wdu6cca eaplmx > Related with my current conversation, what do you think of using twtxt.txt as a format for feeds?

@eaplmx 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.

#jdl5x5a prologic > @darch There are a few minor regressions. But maybe they were intentional? The "In-Reply-To" used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.

@prologic Allready did that, because I found it confusing too:

#jdl5x5a prologic > @darch There are a few minor regressions. But maybe they were intentional? The "In-Reply-To" used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.

@darch If that’s intention, that’s fine 👌 However it is visually different to tell apart the ‘In Reply To …” with for example an actual quote:

This is a quote…

Can we do something here?

#jdl5x5a prologic > @darch There are a few minor regressions. But maybe they were intentional? The "In-Reply-To" used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.

@prologic Yes that is an new “feature” (not a bug™️) - I have made it to be limited to 3 lines after I made the PR.

Anything else you have found to be off/odd?

#zogehjq mckinley > @prologic 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:

@mckinley In that case maybe we should adopt the GoldMark library which I think implements CommonMark?

#zogehjq mckinley > @prologic 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:

@prologic 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.

#zogehjq mckinley > @prologic 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:

Probably yhe sanitizer doesn’t allow it 🤔 (for web)

#zogehjq mckinley > @prologic 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:

@mckinley It actually did work in the mobile app Goryon

#rbkm6dq lyse > Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. 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. 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. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.

@mckinley So… What are you proposing exactly? 🤔 If not some kind of metadata field declaration?

(#xvx7mta) 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…

#zogehjq mckinley > @prologic 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:

Nope, no horizontal rule. What about referenced links?

My website

#rbkm6dq lyse > Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. 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. 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. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.

@prologic 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


#y3bp7ga mckinley > Recent updates to LibWeb have fixed the icons on the Yarn web client in Ladybird and the SerenityOS browser! Unfortunately, it still isn't possible to post using LibWeb browsers but we'll get there. :^)

@mckinley Looks not too bad 👌

#y3bp7ga mckinley > Recent updates to LibWeb have fixed the icons on the Yarn web client in Ladybird and the SerenityOS browser! Unfortunately, it still isn't possible to post using LibWeb browsers but we'll get there. :^)

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

#j6ldm5q prologic > @darch Also the pop-up when you click on external links in a Twt is broken. I tried to for example in the Twt (screenshot attached) and it didn't work :/

In fact even in this Yarn, the whole Image Gallery feature that @ullarah originally did is not completely broken 😅 I’ll let you ponder on that for a while, but we should probably do something about this before cutting a new release for sure 👌

#rbkm6dq lyse > Not sure which conversation you mean, @eaplmx (it's already quite late here), but here's my take: I think twtxt it's not heavy enough. 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. 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. To make things worse, I actually prefer reStructuredText over markdown. For podcasts some enclosure-like thing would be nice as well. Twtxt being line based also really limits structuring of longer content by hand. Just can't produce a nice source file.

@mckinley We’ve talked about this once before and in fact even tried to formalize it but in the end we couldn’t agree on a way to do it or even if it was a good idea… Worth revisiting this again? Like @lyse I’ve also looked at JSON Feed and wasn’t entirely convinced either.

#pk6tyua lyse > (#gsewnyq) @tkanos So basically it counts the mentions? We definitely need some feed normalization database, too many broken mentions out there. :-)

@lyse

We definitely need some feed normalization database, too many broken mentions out there

What if we use some kind of heuristics based on a client’s cache? Or some kind of similarity search? Hmm 🤔

#ix64jaa prologic > 💡 TIL: Today I learned that there is nothing special about pkg/ inside of Go projects. It is just like any other sub-package structure you might otherwise define in your project. It just adds an extra part to your imports. I think it's actually confusing at best and just unnecessary typing and an unnecessary sub-structure. Just keep your packages in the top-level and be done with it 👌

@lyse Yeah I agree, and that does happen.

@darch There are a few minor regressions. But maybe they were intentional? The “In-Reply-To” used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.

#wdu6cca eaplmx > Related with my current conversation, what do you think of using twtxt.txt as a format for feeds?

@akoizumi 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.