🧮 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.
> ?
@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
> ?
@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
> ?
@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.
> ?
@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
🧮 USERS:1 FEEDS:2 TWTS:854 ARCHIVED:69854 CACHE:2286 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:853 ARCHIVED:69849 CACHE:2287 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:852 ARCHIVED:69835 CACHE:2282 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:851 ARCHIVED:69819 CACHE:2281 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:850 ARCHIVED:69811 CACHE:2290 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:849 ARCHIVED:69806 CACHE:2291 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:848 ARCHIVED:69796 CACHE:2309 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:847 ARCHIVED:69793 CACHE:2312 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:846 ARCHIVED:69788 CACHE:2341 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:845 ARCHIVED:69784 CACHE:2343 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:844 ARCHIVED:69775 CACHE:2342 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:843 ARCHIVED:69768 CACHE:2344 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:842 ARCHIVED:69763 CACHE:2359 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:841 ARCHIVED:69752 CACHE:2361 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:840 ARCHIVED:69731 CACHE:2356 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:839 ARCHIVED:69718 CACHE:2353 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:838 ARCHIVED:69711 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:837 ARCHIVED:69697 CACHE:2349 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:836 ARCHIVED:69681 CACHE:2340 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:835 ARCHIVED:69661 CACHE:2328 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:834 ARCHIVED:69649 CACHE:2319 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:833 ARCHIVED:69635 CACHE:2313 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:832 ARCHIVED:69610 CACHE:2296 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:831 ARCHIVED:69593 CACHE:2327 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:830 ARCHIVED:69471 CACHE:2326 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:829 ARCHIVED:69292 CACHE:2339 FOLLOWERS:14 FOLLOWING:14
hmm all my old twts disappeared from the yarn webview, is that normal?
🧮 USERS:1 FEEDS:2 TWTS:828 ARCHIVED:69285 CACHE:2336 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:827 ARCHIVED:69267 CACHE:2334 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:826 ARCHIVED:69257 CACHE:2326 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:825 ARCHIVED:69247 CACHE:2328 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:824 ARCHIVED:69243 CACHE:2325 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:823 ARCHIVED:69234 CACHE:2317 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:822 ARCHIVED:69227 CACHE:2322 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:821 ARCHIVED:69220 CACHE:2317 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:820 ARCHIVED:69210 CACHE:2311 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:819 ARCHIVED:69205 CACHE:2316 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:818 ARCHIVED:69182 CACHE:2294 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:817 ARCHIVED:69169 CACHE:2291 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:816 ARCHIVED:69167 CACHE:2290 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:815 ARCHIVED:69155 CACHE:2289 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:814 ARCHIVED:69151 CACHE:2357 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:813 ARCHIVED:69147 CACHE:2363 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:812 ARCHIVED:69113 CACHE:2363 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:811 ARCHIVED:68251 CACHE:2361 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:810 ARCHIVED:68241 CACHE:2363 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:809 ARCHIVED:68235 CACHE:2359 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:808 ARCHIVED:68225 CACHE:2353 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:807 ARCHIVED:68213 CACHE:2360 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:806 ARCHIVED:68196 CACHE:2363 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:805 ARCHIVED:68180 CACHE:2356 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:804 ARCHIVED:68150 CACHE:2335 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:803 ARCHIVED:68118 CACHE:2311 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:802 ARCHIVED:68081 CACHE:2317 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:801 ARCHIVED:68068 CACHE:2341 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:800 ARCHIVED:68056 CACHE:2339 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:799 ARCHIVED:68051 CACHE:2345 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:798 ARCHIVED:68042 CACHE:2352 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:797 ARCHIVED:68036 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:796 ARCHIVED:68030 CACHE:2390 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:795 ARCHIVED:68004 CACHE:2372 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:794 ARCHIVED:67993 CACHE:2365 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:793 ARCHIVED:67940 CACHE:2351 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:792 ARCHIVED:67928 CACHE:2341 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:791 ARCHIVED:67915 CACHE:2346 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:790 ARCHIVED:67896 CACHE:2335 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:789 ARCHIVED:67870 CACHE:2323 FOLLOWERS:14 FOLLOWING:14
I’ve been thinking of how to notify someone else that you’ve replied to their twts.
Is there something already developed, for example on yarn.social?
Let’s say I want to notify https://sour.is/tiktok/America/Denver.txt that I’ve replied to some twt. They don’t follow me back, so they won’t see my reply.
I would send my URL to, could be, https://sour.is/tiktok/replies?url=MY_URL and they’ll check that I have a reply to some of their twts, and could decide to follow me back (after seeing my twtxt profile to avoid spam)
Another option could be having a metadata like
follow-request=https://sour.is/tiktok/America/Denver.txt TIMESTAMP_IN_SECONDS
that the other client has to look for, to ensure that the request comes from that URL (again, to avoid spam)
This could be deleted after the other .txt has your URL in the follow list, or auto-expire after X days to clean-up old requests.
What do you think?
🧮 USERS:1 FEEDS:2 TWTS:788 ARCHIVED:67853 CACHE:2309 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:787 ARCHIVED:67826 CACHE:2291 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:786 ARCHIVED:67815 CACHE:2285 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:785 ARCHIVED:67802 CACHE:2295 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:784 ARCHIVED:67794 CACHE:2289 FOLLOWERS:14 FOLLOWING:14
My cli work-apps: note, plan, dlog (daily log), status and twt.
🧮 USERS:1 FEEDS:2 TWTS:783 ARCHIVED:67789 CACHE:2321 FOLLOWERS:14 FOLLOWING:14
🧮 USERS:1 FEEDS:2 TWTS:782 ARCHIVED:67782 CACHE:2342 FOLLOWERS:14 FOLLOWING:14