🧮 USERS:1 FEEDS:2 TWTS:946 ARCHIVED:71458 CACHE:2406 FOLLOWERS:15 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:945 ARCHIVED:71398 CACHE:2368 FOLLOWERS:15 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:944 ARCHIVED:71348 CACHE:2369 FOLLOWERS:15 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:943 ARCHIVED:71337 CACHE:2359 FOLLOWERS:15 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:942 ARCHIVED:71335 CACHE:2365 FOLLOWERS:15 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:940 ARCHIVED:71319 CACHE:2367 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:939 ARCHIVED:71305 CACHE:2358 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:938 ARCHIVED:71290 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:937 ARCHIVED:71270 CACHE:2338 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:936 ARCHIVED:71237 CACHE:2310 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:935 ARCHIVED:71213 CACHE:2307 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:934 ARCHIVED:71209 CACHE:2308 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:933 ARCHIVED:71205 CACHE:2320 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:932 ARCHIVED:71203 CACHE:2322 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:931 ARCHIVED:71183 CACHE:2306 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:930 ARCHIVED:71168 CACHE:2308 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:929 ARCHIVED:71161 CACHE:2310 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:928 ARCHIVED:71156 CACHE:2307 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:927 ARCHIVED:71151 CACHE:2303 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:926 ARCHIVED:71144 CACHE:2297 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:925 ARCHIVED:71138 CACHE:2297 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:924 ARCHIVED:71129 CACHE:2289 FOLLOWERS:14 FOLLOWING:14
Hey @sorenpeter@darch.dk, I’m sorry to tell you, but the prev field in your feed’s headers is invalid. 😅
First, it doesn’t include the hash of the last twt in the archive. Second, and that’s probably more important, it forms an infinite loop: The prev field of your main feed specifies http://darch.dk/twtxt-archive.txt and that file then again specifies http://darch.dk/twtxt-archive.txt. Some clients might choke on this, mine for example. 😂 I’ll push a fix soon, though.
For reference, the prev field is described here: https://dev.twtxt.net/doc/archivefeedsextension.html
🧮 USERS:1 FEEDS:2 TWTS:923 ARCHIVED:71116 CACHE:2282 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:922 ARCHIVED:71109 CACHE:2276 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:921 ARCHIVED:71099 CACHE:2286 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:920 ARCHIVED:71093 CACHE:2296 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:919 ARCHIVED:71078 CACHE:2288 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:918 ARCHIVED:71068 CACHE:2285 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:917 ARCHIVED:71066 CACHE:2307 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:916 ARCHIVED:71065 CACHE:2307 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:915 ARCHIVED:71057 CACHE:2304 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:914 ARCHIVED:71044 CACHE:2302 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:913 ARCHIVED:71035 CACHE:2342 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:912 ARCHIVED:71033 CACHE:2345 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:911 ARCHIVED:71029 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:910 ARCHIVED:71023 CACHE:2355 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:909 ARCHIVED:71016 CACHE:2349 FOLLOWERS:14 FOLLOWING:14
↳
In-reply-to
»
post with no mentions
⤋ Read More
It not that easy @xuu@txt.sour.is since I implemented webmentions in a different way that how it have been done in yarnd to work with txt-files. You can find the code in webmention_endpoint.php and new_twt.php at main · sorenpeter/timeline
🧮 USERS:1 FEEDS:2 TWTS:908 ARCHIVED:71001 CACHE:2339 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:907 ARCHIVED:70996 CACHE:2339 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:906 ARCHIVED:70905 CACHE:2344 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:905 ARCHIVED:70892 CACHE:2334 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:904 ARCHIVED:70855 CACHE:2315 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:903 ARCHIVED:70846 CACHE:2324 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:902 ARCHIVED:70837 CACHE:2329 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:901 ARCHIVED:70813 CACHE:2323 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:900 ARCHIVED:70303 CACHE:2308 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:899 ARCHIVED:70294 CACHE:2303 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:898 ARCHIVED:70290 CACHE:2302 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:897 ARCHIVED:70282 CACHE:2300 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:896 ARCHIVED:70270 CACHE:2292 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:895 ARCHIVED:70265 CACHE:2291 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:894 ARCHIVED:70260 CACHE:2287 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:893 ARCHIVED:70242 CACHE:2279 FOLLOWERS:14 FOLLOWING:14
↳
In-reply-to
»
yarn should define its own federation protocol that extends the basic twtxt in ways that twtxt doesn't allow. it's time. and i've got ideas!
⤋ Read More
@shreyan@twtxt.net What do you mean when you say federation protocol?
Either use webfinger for identity like mastodon etc. or use ATproto from Bluesky (or both?)
We can use webmentions or create our own twt-mentions for notifying someones feed (WIP code at: https://github.com/sorenpeter/timeline/tree/webmention/views)
I’m not sure we need much else. I would not even bother with encryption since other platforms does that better, and for me twtxt/yarn/timeline is for making things public
🧮 USERS:1 FEEDS:2 TWTS:892 ARCHIVED:70205 CACHE:2272 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:891 ARCHIVED:70188 CACHE:2269 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:890 ARCHIVED:70178 CACHE:2292 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:889 ARCHIVED:70170 CACHE:2311 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:888 ARCHIVED:70167 CACHE:2310 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:887 ARCHIVED:70164 CACHE:2312 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:886 ARCHIVED:70157 CACHE:2312 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:885 ARCHIVED:70154 CACHE:2316 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:884 ARCHIVED:70151 CACHE:2315 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:883 ARCHIVED:70145 CACHE:2313 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:882 ARCHIVED:70141 CACHE:2312 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:881 ARCHIVED:70120 CACHE:2296 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:880 ARCHIVED:70099 CACHE:2282 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:879 ARCHIVED:70077 CACHE:2273 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:878 ARCHIVED:70058 CACHE:2275 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:877 ARCHIVED:70054 CACHE:2298 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:876 ARCHIVED:70052 CACHE:2299 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:875 ARCHIVED:70043 CACHE:2300 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:874 ARCHIVED:70038 CACHE:2303 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:873 ARCHIVED:70010 CACHE:2305 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:872 ARCHIVED:70008 CACHE:2307 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:871 ARCHIVED:70003 CACHE:2308 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:870 ARCHIVED:69995 CACHE:2302 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:869 ARCHIVED:69983 CACHE:2292 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:868 ARCHIVED:69971 CACHE:2284 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:867 ARCHIVED:69961 CACHE:2296 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:866 ARCHIVED:69948 CACHE:2286 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:865 ARCHIVED:69931 CACHE:2280 FOLLOWERS:14 FOLLOWING:14
Twtxt spec enhancement proposal thread 🧵
Adding attributes to individual twts similar to adding feed attributes in the heading comments.
https://git.mills.io/yarnsocial/go-lextwt/pulls/17
The basic use case would be for multilingual feeds where there is a default language and some twts will be written a different language.
As seen in the wild: https://eapl.mx/twtxt.txt
The attributes are formatted as [key=value]
They can show up in the twt anywhere it is not enclosed by another element such as codeblock or part of a markdown link.
Twtxt spec enhancement proposal thread 🧵
Adding attributes to individual twts similar to adding feed attributes in the heading comments.
https://git.mills.io/yarnsocial/go-lextwt/pulls/17
The basic use case would be for multilingual feeds where there is a default language and some twts will be written a different language.
As seen in the wild: https://eapl.mx/twtxt.txt
The attributes are formatted as [key=value]
They can show up in the twt anywhere it is not enclosed by another element such as codeblock or part of a markdown link.
↳
In-reply-to
»
(#fytbg6a) What about using the blockquote format with
⤋ Read More
> ?
@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.
i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.
The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.
The format is also how iphone does reactions to SMS messages with +number liked: original SMS
↳
In-reply-to
»
(#fytbg6a) What about using the blockquote format with
⤋ Read More
> ?
@sorenpeter@darch.dk this makes sense as a quote twt that references a direct URL. If we go back to how it developed on twitter originally it was RT @nick: original text because it contained the original text the twitter algorithm would boost that text into trending.
i like the format (#hash) @<nick url> > "Quoted text"\nThen a comment
as it preserves the human read able. and has the hash for linking to the yarn. The comment part could be optional for just boosting the twt.
The only issue i think i would have would be that that yarn could then become a mess of repeated quotes. Unless the client knows to interpret them as multiple users have reposted/boosted the thread.
The format is also how iphone does reactions to SMS messages with +number liked: original SMS
↳
In-reply-to
»
(#fytbg6a) What about using the blockquote format with
⤋ Read More
> ?
@eapl.me@eapl.me this is interesting. Is the square bracket something used in the wild for multilingual twts?
@prologic@twtxt.net what are your thoughts? Should we extend the parser to handle [lang] and [boost] ? Or a generic attribute spec. Single word is a boolean attribute. And one with an = is a string key/value.
↳
In-reply-to
»
(#fytbg6a) What about using the blockquote format with
⤋ Read More
> ?
@eapl.me@eapl.me this is interesting. Is the square bracket something used in the wild for multilingual twts?
@prologic@twtxt.net what are your thoughts? Should we extend the parser to handle [lang] and [boost] ? Or a generic attribute spec. Single word is a boolean attribute. And one with an = is a string key/value.
🧮 USERS:1 FEEDS:2 TWTS:864 ARCHIVED:69917 CACHE:2269 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:863 ARCHIVED:69914 CACHE:2280 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:862 ARCHIVED:69910 CACHE:2289 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:861 ARCHIVED:69900 CACHE:2293 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:860 ARCHIVED:69897 CACHE:2298 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:859 ARCHIVED:69896 CACHE:2298 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:858 ARCHIVED:69891 CACHE:2300 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:857 ARCHIVED:69876 CACHE:2288 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:856 ARCHIVED:69871 CACHE:2289 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:855 ARCHIVED:69866 CACHE:2286 FOLLOWERS:14 FOLLOWING:14