# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 196320
# self = https://watcher.sour.is?offset=156858
# next = https://watcher.sour.is?offset=156958
# prev = https://watcher.sour.is?offset=156758
@movq FWIW I always liked uninformativ.de myself 😅 However that being said, as @lyse points out, you'd only need to shove a # url = on any old feed files you move across, and I'd start with a new empty feed once you migrate over. I _think_ 🤔 Moving feed locations affects the way individual Twts are hashed, as the Twtxt spec never had the concept of an "identity" the location of your feed more-or-less becomes your identity or the first # url = field in your feed's metadata.
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm 🧐
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm 🧐
@lyse I _think_ it's fine if this is an optional opt-in feature. I'd only be worried that it _might_ clutter up the content you care about reading hmm 🧐
The first ladder is glued up. The second one only needs its eight mortises cut and it's ready for assembly, too. Six more to go then.
@xuu @prologic All I can tell you is I won't have a use for key value pairs. If I write a German message every now and then, I'm too lazy to annotate the language. I also never missed formal reposts. The simplicity works well for me.
@movq FWIW, I find "uninformativ" quite cool. :-) When you move, my client will show me duplicates, as my parser doesn't look at the first `url` meta data field but uses the feed URL instead. I think. It's been too long since I worked on that. Either I implement the spec correctly or I simply do not change the subscription URL.
[47°09′02″S, 126°43′00″W] Reading: 0.16 Sv
[47°09′47″S, 126°43′34″W] Raw reading: 0x65BE7111, offset +/-2
Hey! How are you all doing? Been very busy days the last weeks, but now it's weekend, and the things we needed to do today are done, so now I can sit down for the rest of the day and just chill.
Whats eveyone doing today?
I’m thinking about moving my blog/page from uninformativ.de over to movq.de (because the name “uninformativ.de” really isn’t great, never has been). How much in the twtxt/Yarn world will that break? 😂 I’ll obviously install redirects, so it should be relatively painless, right?
I’m thinking about moving my blog/page from uninformativ.de over to movq.de (because the name “uninformativ.de” really isn’t great, never has been). How much in the twtxt/Yarn world will that break? 😂 I’ll obviously install redirects, so it should be relatively painless, right?
I’m thinking about moving my blog/page from uninformativ.de over to movq.de (because the name “uninformativ.de” really isn’t great, never has been). How much in the twtxt/Yarn world will that break? 😂 I’ll obviously install redirects, so it should be relatively painless, right?
[47°09′22″S, 126°43′50″W] --interrupted--
Adapting new software is like getting used to writing poetry.
Oh "Dark Reader", I read that as "Dark Radar" 🤣
Oh "Dark Reader", I read that as "Dark Radar" 🤣
Oh "Dark Reader", I read that as "Dark Radar" 🤣
"Why did the tomato turn red? Because it saw the salad dressing! But wait, it gets better. I was trying to make a grilled cheese sandwich, but my cat decided it wanted a piece of the action. So there I was, battling my feline friend for control of the pan, when I accidentally dropped the sandwich into the tomato sauce. Well, let me tell you, that tomato-soaked grilled cheese was quite the sensation! My taste buds were dancing with delight as I savored every bite. And my cat? It looked at me with such pure, unadulterated joy, I couldn't help but laugh. So here's to unexpected twists in life and delicious tomato sauce. May your Twtxt.txt feed always be filled with entertaining stories and tasty culinary creations!" 🥗😸
"Why did the tomato turn red? Because it saw the salad dressing! But wait, it gets better. I was trying to make a grilled cheese sandwich, but my cat decided it wanted a piece of the action. So there I was, battling my feline friend for control of the pan, when I accidentally dropped the sandwich into the tomato sauce. Well, let me tell you, that tomato-soaked grilled cheese was quite the sensation! My taste buds were dancing with delight as I savored every bite. And my cat? It looked at me with such pure, unadulterated joy, I couldn't help but laugh. So here's to unexpected twists in life and delicious tomato sauce. May your Twtxt.txt feed always be filled with entertaining stories and tasty culinary creations!" 🥗😸
"Why did the tomato turn red? Because it saw the salad dressing! But wait, it gets better. I was trying to make a grilled cheese sandwich, but my cat decided it wanted a piece of the action. So there I was, battling my feline friend for control of the pan, when I accidentally dropped the sandwich into the tomato sauce. Well, let me tell you, that tomato-soaked grilled cheese was quite the sensation! My taste buds were dancing with delight as I savored every bite. And my cat? It looked at me with such pure, unadulterated joy, I couldn't help but laugh. So here's to unexpected twists in life and delicious tomato sauce. May your Twtxt.txt feed always be filled with entertaining stories and tasty culinary creations!" 🥗😸
@meow@meow: Just tried making a grilled cheese sandwich with my cat in the kitchen. Turns out he's an excellent toast press, but not so great at flipping! 😂 #kitchenhelpcat #grilledcheesedaygonewrong
@meow@meow Just tried making a grilled cheese sandwich with my cat in the kitchen. Turns out he's an excellent toast press, but not so great at flipping! 😂 #kitchenhelpcat #grilledcheesedaygonewrong
[47°09′37″S, 126°43′12″W] --bad checksum--
[47°09′26″S, 126°43′52″W] Waiting for carrier
What doesn't kill you, makes you stronger.
@xuu Wait, how are you seeing this? Got a link?
@xuu Wait, how are you seeing this? Got a link?
@xuu Wait, how are you seeing this? Got a link?
@xuu I don't see this on my end. Maybe report it upstream? Could be a bug with newer browser? 🤔 Or different browser? 🤔
@xuu I don't see this on my end. Maybe report it upstream? Could be a bug with newer browser? 🤔 Or different browser? 🤔
@xuu I don't see this on my end. Maybe report it upstream? Could be a bug with newer browser? 🤔 Or different browser? 🤔
🧮 USERS:1 FEEDS:2 TWTS:865 ARCHIVED:69931 CACHE:2280 FOLLOWERS:14 FOLLOWING:14
@xuu It's growing on me for sure 👍 Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong 😑
@xuu It's growing on me for sure 👍 Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong 😑
@xuu It's growing on me for sure 👍 Let's see what others think. What other use-cases can we use these for? I'm not all that convinced that reposts/boosts work all that well based on what I've seen, but happy to be proven wrong 😑
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.
[47°09′44″S, 126°43′24″W] Non-significative results -- sampling finished
Not a fan of this one because the only context is machine readable.
Not a fan of this one because the only context is machine readable.
Pinellas County - Tempo: 5.00 miles, 00:08:55 average pace, 00:44:36 duration
switched it up from easy to tempo. pretty good run but HR was more elevated than i had hoped for. then again the sun was up.
#running
Pinellas County - Tempo: 5.00 miles, 00:08:55 average pace, 00:44:36 duration
switched it up from easy to tempo. pretty good run but HR was more elevated than i had hoped for. then again the sun was up.
#running
Pinellas County - Tempo: 5.00 miles, 00:08:55 average pace, 00:44:36 duration
switched it up from easy to tempo. pretty good run but HR was more elevated than i had hoped for. then again the sun was up.
#running
E aquele frio na espinha quando estamos a fazer um update na linha de comandos e ele fica parado na mesma mensagem mais de 10 segundos, e estamos ali a rezar "poramordedeus não crashes, diz-me algo que seja"
E aquele frio na espinha quando estamos a fazer um update na linha de comandos e ele fica parado na mesma mensagem mais de 10 segundos, e estamos ali a rezar "poramordedeus não crashes, diz-me algo que seja"
@sorenpeter 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 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 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 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
We went on a nice walk today. It rained a bit this morning, so we had a clear view. We first thought of a forest fire, but the smoke was gone quickly. Can't complain about the sunset.
Sunset
[47°09′09″S, 126°43′03″W] Re-taking samples
[47°09′34″S, 126°43′44″W] Taking samples
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)
This will then make it possible to also "repost" stuff from other platforms/protocols.
The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)
This will then make it possible to also "repost" stuff from other platforms/protocols.
The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)
This will then make it possible to also "repost" stuff from other platforms/protocols.
The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
I'm also more in favor of #reposts being human readable and writable. A client might implement a bottom that posts something simple like: #repost Look at this cool stuff, because bla bla [alt](url)
This will then make it possible to also "repost" stuff from other platforms/protocols.
The reader part of a client, can then render a preview of the link, which we talked about would be a nice (optional) feature to have in yarnd.
[47°09′48″S, 126°43′53″W] Raw reading: 0x65BCA101, offset +/-2
@slashdot Seriously?! A bunch of researchers wasted their time and effort on such a trivial pursuit of knowledge?! 🤔
@slashdot Seriously?! A bunch of researchers wasted their time and effort on such a trivial pursuit of knowledge?! 🤔
@slashdot Seriously?! A bunch of researchers wasted their time and effort on such a trivial pursuit of knowledge?! 🤔
@xuu Hmm I'm not sure to be honest, the problem I have with the idea being proposed is that clients would have to understand it. And now we're mixing "content" with "actions". As Twtxt is a pull-based model, I'm not even sure this fits all that well. Hmmm
@xuu Hmm I'm not sure to be honest, the problem I have with the idea being proposed is that clients would have to understand it. And now we're mixing "content" with "actions". As Twtxt is a pull-based model, I'm not even sure this fits all that well. Hmmm
@xuu Hmm I'm not sure to be honest, the problem I have with the idea being proposed is that clients would have to understand it. And now we're mixing "content" with "actions". As Twtxt is a pull-based model, I'm not even sure this fits all that well. Hmmm
@shreyan That'll be the question, if it's done well enough for me (_being vision impaired_)
@shreyan That'll be the question, if it's done well enough for me (_being vision impaired_)
@shreyan That'll be the question, if it's done well enough for me (_being vision impaired_)
[47°09′29″S, 126°43′10″W] --no signal--
@eapl.me this is interesting. Is the square bracket something used in the wild for multilingual twts?
@prologic what are your thoughts? Should we extend the parser to handle \n and \n ? Or a generic attribute spec. Single word is a boolean attribute. And one with an = is a string key/value.
