\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
![An image on my website][2]
\n\n\n\n\n\n\n\n: https://mckinley.cc/
\n\n\n\n\n\n\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
![An image on my website][2]
\n\n\n\n\n\n\n\n: https://mckinley.cc/
\n\n\n\n\n\n\n\n: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
[My website][My website=][1][1=]
![An image on my website][2]
[1][1=]: https://mckinley.cc/
[2][2=]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
[My website][My website=][My website][My website=][My website][My website=][My website][My website=][1][1=][1][1=][1][1=][1][1=]
![An image on my website][2]
[1][1=][1][1=][1][1=][1][1=]: https://mckinley.cc/
[2][2=][2][2=][2][2=][2][2=]: https://mckinley.cc/img/ladybird-yarn-20220924-2.png
***
Some text here
---***
twtxt.net's Discover page viewed in Ladybird, post-merge, on 2022-09-24
twtxt.net's Discover page viewed in Ladybird, post-merge, on 2022-09-24
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.
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.
TIMESTAMP\\tTITLE: PERMALINK which would be harder to parse programmatically.This discussion has me thinking of a serious syndication format built on 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.
TIMESTAMP\\tTITLE: PERMALINK which would be harder to parse programmatically.This discussion has me thinking of a serious syndication format built on twtxt that could be implemented in normal feed readers. It would be limited, but extremely easy for a Webmaster to implement. You could also receive updates with a normal twtxt client. I think there could be some utility in it.
TIMESTAMP\\tTITLE: PERMALINK which would be harder to parse programmatically.This discussion has me thinking of a serious syndication format built on twtxt that could be implemented in normal feed readers. It would be limited, but extremely easy for a Webmaster to implement. You could also receive updates with a normal twtxt client. I think there could be some utility in it.
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
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\tBringing Back a Useful Browser Feature With a Bookmarklet\thttps://mckinley.cc/blog/20220922.html
> 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.
> 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 and @darch
twtxt.net's Discover page viewed in Ladybird on 2022-09-24
twtxt.net's Discover page viewed in Ladybird on 2022-09-24
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.
inline code snippets so they don't get wrapped where it would make it hard to read.
* Markdown isn't rendered to HTML in Atom feeds (#989)
* A look at @darch'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
Take a look at view-source:https://mckinley.cc/blog/atom.xml
view-source:https://mckinley.cc/blog/atom.xml
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
*
<summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug\t* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
*
<summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug\t* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certa*
* Something in the pipeline is adding U+FFFD Replacement Characters to the ends of certain twts
* Markdown isn't rendered to HTML in the Atom feed, but mentions are.
*
<summary> elements (which should probably be <contents> instead) are type="html", escaped HTML. It wouldn't be possible to embed twt contents in the generated page on Firefox-based browsers due to my favorite bug* The other options are either plain text or inline XHTML which means you have to make sure every twt is valid XHTML.
* I don't know how to handle different themes short of JavaScript which can be buggy when used with client-side XSLT or dynamically generated XSLT which is completely and utterly ridiculous.*
The third theme (black/yellow) uses the accent color for those buttons. I was using that as an example.
I did find that the original path on Reddit is in the page inside a stringified JSON object as a global variable.
JSON.parse(window.scrolllerConfig).item.redditPath will return the path.I suppose this could be done with a userscript, but the whole point is to not load the Scrolller page. Interestingly, the first one you posted has been deleted from Reddit.
I did find that the original path on Reddit is in the page inside a stringified JSON object as a global variable defined in a
script element. JSON.parse(window.scrolllerConfig).item.redditPath will return the path.I suppose this could be done with a userscript, but the whole point is to not load the Scrolller page. Interestingly, the first one you posted has been deleted from Reddit.
unless statement.
unless statement.
unless statement.
* The rationale behind GoNix
* @darch's thoughts on social networking (https://blog.neotxt.dk/)
* Bringing people on to free platforms
* Bot prevention on Yarn.social (#981)
* Funding for Yarn.social
* Goryon, material design, and satanism
twtxt.net's Discover page viewed in Ladybird on 2022-09-15For comparison, here's a screenshot from 2022-07-22:
twtxt.net's Discover page viewed in Ladybird on 2022-07-22
Lately, I've been thinking about a wrapper script for MPV that tries to find a copy of the video on disk before it lets MPV use yt-dlp to stream it. This would be used in conjunction with another program that grabs a list of articles in Newsboat with a specific tag to filter videos from non-videos. Videos marked unread are queued for download with yt-dlp if there isn't already a local copy. Videos marked read are deleted if there is a local copy. I think this could be done by interacting with Newsboat's database directly, but that isn't preferable.
How does ybeuter work? Is the source available?
Lately, I've been thinking about a wrapper script for MPV that tries to find a copy of the video on disk before it lets MPV use yt-dlp to stream it. This would be used in conjunction with another program that grabs a list of articles in Newsboat with a specific tag to filter videos from non-videos.
Videos marked unread are queued for download with yt-dlp if there isn't already a local copy. Videos marked read are deleted if there is a local copy. I think this could be done by interacting with Newsboat's database directly, but that isn't preferable.
How does ybeuter work? Is the source available?
Lately, I've been thinking about a wrapper script for MPV that tries to find a copy of the video on disk before it lets MPV use yt-dlp to stream it. This would be used in conjunction with another program that grabs a list of articles in Newsboat with a specific tag to filter videos from non-videos. Videos marked unread are queued for download with yt-dlp if there isn't already a local copy. Videos marked unread are deleted if there is a local copy. I think this could be done by interacting with Newsboat's database directly, but that isn't preferable.
How does ybeuter work? Is the source available?