In-reply-to » 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.

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

⤋ Read More
In-reply-to » 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@lyse.isobeef.org here too 👌 It adds little value to the spec when we already have mechanisms to share titles by convention.

⤋ Read More
In-reply-to » Hello Google

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

⤋ Read More
In-reply-to » @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@neotxt.dk You need to rebase it like I showed you.

⤋ Read More

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

⤋ Read More
In-reply-to » 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@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.

⤋ Read More
In-reply-to » For people born after the 90s (no one here I suppose), this was Active Desktop: Media 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 Ahh, right, that’s it! 😲 🧓

⤋ Read More
In-reply-to » @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@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?

⤋ Read More
In-reply-to » @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@twtxt.net In that case maybe we should adopt the GoldMark library which I think implements CommonMark?

⤋ Read More
In-reply-to » @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)

⤋ Read More
In-reply-to » @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@twtxt.net It actually did work in the mobile app Goryon

⤋ Read More
In-reply-to » 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@twtxt.net So… What are you proposing exactly? 🤔 If not some kind of metadata field declaration?

⤋ Read More
In-reply-to » 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@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

⤋ Read More
In-reply-to » 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@twtxt.net Looks not too bad 👌

⤋ Read More
In-reply-to » @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@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 👌

⤋ Read More
In-reply-to » 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@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.

⤋ Read More
In-reply-to » @tkanos So basically it counts the mentions? We definitely need some feed normalization database, too many broken mentions out there. :-)

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

⤋ Read More
In-reply-to » 💡 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@lyse.isobeef.org Yeah I agree, and that does happen.

⤋ Read More

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

⤋ Read More
In-reply-to » Related with my current conversation, what do you think of using twtxt.txt as a format for feeds?

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

⤋ Read More
In-reply-to » Related with my current conversation, what do you think of using twtxt.txt as a format for feeds?

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.

⤋ Read More
In-reply-to » Guys, I have a bad news, I went through the twtxt-osphere : - I found 1289 twtxt account - among those 721 are accessible ( 712 http / 9 gemini / 0 gopher) - but only 111 account are still active in 2022 :S (107 http / 4 gemini / 0 gopher).

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

⤋ Read More

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

⤋ Read More
In-reply-to » For people born after the 90s (no one here I suppose), this was Active Desktop: Media 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 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. 😅

⤋ Read More
In-reply-to » Just noticed that Firefox now downloads feeds (Atom, RSS), which is a little less than helpful. 🙄

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

⤋ Read More
In-reply-to » Just noticed that Firefox now downloads feeds (Atom, RSS), which is a little less than helpful. 🙄

@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?)

⤋ Read More
In-reply-to » Just noticed that Firefox now downloads feeds (Atom, RSS), which is a little less than helpful. 🙄

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

⤋ Read More