@darch@neotxt.dk Titles and subjects are two different things in my opinion. A title is a caption, brief summary or some description of a longer content that follows. A subject is a – in this case human readable – reference in a reply to some topic in order to group several twts to a conversation. Forks aside, the first twt starting a discussion typically doesn’t have a subject. But some article would have a title in most cases. You are right in that the subject mechanism could be abused for a crude title implementation. I wouldn’t do it, though.

@prologic@twtxt.net I reckon there is a some kind of frame or hook tool for these loom bands.

Not sure how my daughter made these but they’re really good 👌

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

@lyse@lyse.isobeef.org Hmmm

@darch@neotxt.dk Ahh I see

@darch@neotxt.dk Cool that’s much better 👌

@darch@neotxt.dk 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 👌

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

@prologic@twtxt.net 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.”

@mckinley@twtxt.net 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.

@movq@www.uninformativ.de Ta, in my ~/.Xmodmap I just set my multi key to Caps Lock, which I had deactivated anyways. Now I can insert a non-breaking space with Caps Lock+Space+Space. Nice.

@prologic@twtxt.net I fear that calls for even more trouble. But you can try.

@lyse@lyse.isobeef.org Oh, of course,   … I’ve used that quite a lot, too. 😅 As for entering that stuff directly: https://en.wikipedia.org/wiki/Compose_key is great

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

@darch@neotxt.dk Try to click on the link above… It doesn’t work in the new theme 😅

Hello Google

@darch@neotxt.dk 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?

Ahh I see! I’ll jump on in 29mins 👌

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

How do I play?

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

@mckinley@twtxt.net It actually did work in the mobile app Goryon

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

@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

@mckinley@twtxt.net Looks not too bad 👌

@akoizumi@kyoko.nerdpol.ovh Yeah there a few things that are broken but most things are okay 👌

In fact even in this Yarn, the whole Image Gallery feature that @ullarah@txt.quisquiliae.com 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 👌

@mckinley@twtxt.net 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@lyse.isobeef.org I’ve also looked at JSON Feed and wasn’t entirely convinced either.

@lyse@lyse.isobeef.org

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 🤔

@darch@neotxt.dk 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 :/

@akoizumi@social.kyoko-project.wer.ee Sorry man, I looked at this briefly last night when I went to bed (on my phone) but I “didn’t get it” 😅 Sorry!

@lyse@lyse.isobeef.org Yeah I agree, and that does happen.

It’s also been merged and my pod upgraded 👌

@darch@neotxt.dk 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.

👋 Hey all users of this pod (twtxt.net – I just merged @darch@neotxt.dk’s PR that replaces PicoCSS with SimpleCSS. You may want to refresh or clear your browser cache to get the new look 😅

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

👋 Hello @evaraini@yarn.zn80.net, welcome to yarn.zn80.net, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗

Not sure which conversation you mean, @eaplmx@twtxt.net (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.

On the other hand, RSS and Atom being XML are way too heavy for my taste. And then there’s JSON feed. It’s been a while since I skimmed over it, can’t remember the details, but I wasn’t sold on this one either. I also never encountered any JSON feed in the wild. So I’m still on my quest to find an optimal feed format.

@tkanos@twtxt.net So basically it counts the mentions? We definitely need some feed normalization database, too many broken mentions out there. :-)

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

Indeed I knew the format since it was used in Gemini capsules as a sort of Atom alternative

@eaplmx@twtxt.net Hmm, so these were just regular web pages? 🤔 Wasn’t there also a thingy called “Channels” or something, which was “special”? That’s what I had in mind … I vaguely remember this showing news from a local TV station …

Image

I really don’t remember anymore. 😅

@eaplmx@twtxt.net Nah, we’re not old – technology just moves fast! 😅

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@twtxt.net That’s such an interesting read – in retrospect.

when browser vendors push RSS so far to the sidelines, companies will respond by replacing RSS with Twitter and Facebook accounts.

That’s pretty much what happened eventually, isn’t it?

The blog post outlines a nice vision of how feeds could have been handled (show them on the browser’s start page and such). That would have been super userful for ordinary users. (Almost reminds me a bit of Microsoft’s “Active Desktop” back in the day. 😅 What did that use under the hood? Probably not RSS, that wasn’t around yet, I think?)

@eaplmx@twtxt.net Ah, yeah, that is a bit older. To be honest, I kind of understand them there. Was the “live bookmark” feature ever useful? That wasn’t an actual feed reader, mostly because it lacked a “notification” mechanism (inform the user about new items).

It would have been nice if they hadn’t removed the indicator icon as well. You know, that little icon in the address bar that informs users when a web site offers a feed. Via that icon, users could discover the mere fact that feeds even exist.

who would like to play a game? https://wiki.kyoko-project.wer.ee/wiki.cgi/among-sus

@lyse@lyse.isobeef.org Hmmm good points but yeah it depends on the program 👌

@mckinley@mckinley.cc Same with me, just learned about them now. :-D

@movq@www.uninformativ.de In hand written HTML I use them in between numbers and units. As  , though, because I haven’t figured out which keys to press on my keyboard for that. I know, I know, there’s even a smaller space for this purpose.