# 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 196277
# self = https://watcher.sour.is?offset=174240
# next = https://watcher.sour.is?offset=174340
# prev = https://watcher.sour.is?offset=174140
#catsoftwtxt
[47°09′38″S, 126°43′23″W] Analyzing samples
Já saiu mais um número do #JornalMapa e, como sempre, está repleto de análises acutilantes.
É de lá que vem esta #qotd :
"Mas cabe-nos perguntar: será que a monocultura do turismo é fundamentalmente diferente da monocultura do açúcar?"
Já saiu mais um número do #JornalMapa e, como sempre, está repleto de análises acutilantes.
É de lá que vem esta #qotd :
"Mas cabe-nos perguntar: será que a monocultura do turismo é fundamentalmente diferente da monocultura do açúcar?"
@lyse Better Nate than lever …
@lyse Better Nate than lever …
@lyse Better Nate than lever …
@lyse Better Nate than lever …
How the afternoon started: .oO( let's spend five minutes and see the status of that project... )
How the afternoon is going: .oO( Oh, this is cool, maybe it is possible to do what I want, let me check the documentation; oh, the documentation is wrong, let's fix it but first let's see what caused it... )
Status: one issue open (on a tool used to debug the issue); three pull requests made (regarding the documentation); does the project do what I want? don't know yet, had no time to actually read the documentation O:-)
How the afternoon started: .oO( let's spend five minutes and see the status of that project... )
How the afternoon is going: .oO( Oh, this is cool, maybe it is possible to do what I want, let me check the documentation; oh, the documentation is wrong, let's fix it but first let's see what caused it... )
Status: one issue open (on a tool used to debug the issue); three pull requests made (regarding the documentation); does the project do what I want? don't know yet, had no time to actually read the documentation O:-)
[47°09′44″S, 126°43′17″W] Taking samples
@cuaxolotl not sure that really applies strictly in a purely decentakised system? 🤔
@cuaxolotl not sure that really applies strictly in a purely decentakised system? 🤔
the test would be: how often does unwanted content get pushed on your feed? do incongruent posters easily disrupt harmonious connections? &c. less about the community, more about how the social dynamics play out as various groups and individuals interact.
posthuman real time strategy game in which you're all the units, buildings etc
Well, as for a new UUID it's a thought to combine the timestamp+username or timestamp+url to create a unique id. In this scenario I think the first would probably be favourable. This way if someone decides to use a different url (most likely they will stick to their nickname) UUID's will still hold up.
Adding to that, we could implement a version variable in the meta, adapt code to either read the old or new format UUID, so older threads won't break.
[47°09′28″S, 126°43′39″W] Reading: 1.05 Sv
Hope you all enjoy the weekend!
I _think_ it uses the first # url too. See here and here -- @xuu Can you confirm this to be the case? 🙏 GetN("url", 0) will return the first found # url comment right?
I _think_ it uses the first # url too. See here and here -- @xuu Can you confirm this to be the case? 🙏 GetN("url", 0) will return the first found # url comment right?
@movq I will check when I get home 😅
@movq I will check when I get home 😅
@movq U will check when I get home 😅
That's very sad... Btw twtxt is more hardly to spam because of bad discovery. So you can only spam to your followers. Did you really want abandon best method of microblogging?
[47°09′46″S, 126°43′52″W] Saalmi, retransmit, please
@movq Only because I build and maintain additional services right? 🤔
@movq Only because I build and maintain additional services right? 🤔
@movq Hmmm now I'm confused 😅 I've made no changes anywhere -- we still need to all agree, especially client authors and maintainers 🤣
@movq Hmmm now I'm confused 😅 I've made no changes anywhere -- we still need to all agree, especially client authors and maintainers 🤣
@prologic Oh, yeah, it certainly is more work for you than it is for me. 🫤
@prologic Oh, yeah, it certainly is more work for you than it is for me. 🫤
@prologic Oh, yeah, it certainly is more work for you than it is for me. 🫤
@prologic Oh, yeah, it certainly is more work for you than it is for me. 🫤
@gallowsgryph do you mind updating the fragment part of your avatar url? 🙏
@gallowsgryph do you mind updating the fragment part of your avatar url? 🙏
@movq Don't we use the last url for hashing? 🤔
@movq Don't we use the last url for hashing? 🤔
@movq you are absolutely right! And it did happen once more in the past as well. The difficulty about this particular new behavior though is that I've also had to blacklist it and remove it from the search engine and crawler for obvious reasons.
@movq you are absolutely right! And it did happen once more in the past as well. The difficulty about this particular new behavior though is that I've also had to blacklist it and remove it from the search engine and crawler for obvious reasons.
[47°09′47″S, 126°43′12″W] --bad checksum--
@prologic I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔
@prologic I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔
@prologic I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔
@prologic I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔
@sorenpeter As a *replacement*, it should be doable. But it won’t work *together* with hashes. So the community has to agree on one or the other first.
@sorenpeter As a *replacement*, it should be doable. But it won’t work *together* with hashes. So the community has to agree on one or the other first.
@sorenpeter As a *replacement*, it should be doable. But it won’t work *together* with hashes. So the community has to agree on one or the other first.
@sorenpeter As a *replacement*, it should be doable. But it won’t work *together* with hashes. So the community has to agree on one or the other first.