# 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=174238
# next = https://watcher.sour.is?offset=174338
# prev = https://watcher.sour.is?offset=174138
[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 …
beginnings of a little self-paced flash-card app for learning programming: https://akkartik.name/post/2024-10-26-devlog
beginnings of a little self-paced flash-card app for learning programming: https://akkartik.name/post/2024-10-26-devlog
Haha, 13 years later I got the response that my reported bug in GNAT (GNU Ada compiler) had been fixed a long time ago: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50263
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:-)
Un internet convivial | https://deuxfleurs.fr/
Un internet convivial | https://deuxfleurs.fr/
[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.
On my blog: Free Culture Book Club — Restoration Day, part 3 https://john.colagioia.net/blog/2024/10/26/restoration-day-3.html #freeculture #bookclub
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.
The call is on! Come join us!

https://meet.mills.io/call/Yarn.social
The call is on! Come join us!

https://meet.mills.io/call/Yarn.social
https://d3ward.github.io/toolz/adblock test adblock
https://blog.terminal.pink/
https://blog.terminal.pink/
@stigatle Cominf yo yhe call? 🤔🤗
@stigatle Cominf yo yhe call? 🤔🤗
[47°09′28″S, 126°43′39″W] Reading: 1.05 Sv
Hope you all enjoy the weekend!
AWESOME ! ! !
Windows Endpoint Forensics Readiness Booster https://profero.io/blog/microsoft-windows-endpoint-forensics-readiness-booster
Windows Endpoint Forensics Readiness Booster https://profero.io/blog/microsoft-windows-endpoint-forensics-readiness-booster
@xuu Thanks!
@xuu Thanks!
Malicious Processes Creating Network Traffic | https://hackforlab.com/hunting-strategies-and-techniques-of-malicious-processes-creating-network-traffic/
Malicious Processes Creating Network Traffic | https://hackforlab.com/hunting-strategies-and-techniques-of-malicious-processes-creating-network-traffic/
RDP artifacts | https://www.magnetforensics.com/blog/rdp-artifacts-in-incident-response/
RDP artifacts | https://www.magnetforensics.com/blog/rdp-artifacts-in-incident-response/
Unmasking Hidden Threats: Using Velociraptor for Process Hollowing Analysis | https://daniyyell.com/threat%20hunting/tools/malware%20analysis/Utilising-Velociraptor-for-Effective-Malware-Detection-and-Response/
Unmasking Hidden Threats: Using Velociraptor for Process Hollowing Analysis | https://daniyyell.com/threat%20hunting/tools/malware%20analysis/Utilising-Velociraptor-for-Effective-Malware-Detection-and-Response/
@prologic that should be right
@prologic that should be right
@rodolpho Hey 👋
@rodolpho Hey 👋
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?
@doesnm No I'm just frustrated 🤗
@doesnm No I'm just frustrated 🤗
@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
@prologic I haven’t changed anything, either. 😅 jenny uses the first URL: https://www.uninformativ.de/git/jenny/file/jenny.html#l191
@prologic I haven’t changed anything, either. 😅 jenny uses the first URL: https://www.uninformativ.de/git/jenny/file/jenny.html#l191
@prologic I haven’t changed anything, either. 😅 jenny uses the first URL: https://www.uninformativ.de/git/jenny/file/jenny.html#l191
@prologic I haven’t changed anything, either. 😅 jenny uses the first URL: https://www.uninformativ.de/git/jenny/file/jenny.html#l191
@prologic Yes. 😅
@prologic Yes. 😅
@prologic Yes. 😅
@prologic Yes. 😅
@gallowsgryph Very nice 👌
@gallowsgryph Very nice 👌
@movq Only because I build and maintain additional services right? 🤔
@movq Only because I build and maintain additional services right? 🤔
@gallowsgryph That's mixh better 🥳
@gallowsgryph That's mixh better 🥳
@gallowsgryph Thays mixh better 🥳
@gallowsgryph Thays mixh better 🥳
@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. 🫤
@prologic As per https://dev.twtxt.net/doc/metadataextension.html, it’s the first URL. 😅 I think using the *last* URL was one of the new proposals. Or has that already been implemented? 🤯
@prologic As per https://dev.twtxt.net/doc/metadataextension.html, it’s the first URL. 😅 I think using the *last* URL was one of the new proposals. Or has that already been implemented? 🤯
@prologic As per https://dev.twtxt.net/doc/metadataextension.html, it’s the first URL. 😅 I think using the *last* URL was one of the new proposals. Or has that already been implemented? 🤯
@prologic As per https://dev.twtxt.net/doc/metadataextension.html, it’s the first URL. 😅 I think using the *last* URL was one of the new proposals. Or has that already been implemented? 🤯
@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.
@prologic I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s *inconsistent* now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to *either* know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔
@prologic I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s *inconsistent* now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to *either* know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔
@prologic I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s *inconsistent* now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to *either* know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔
@prologic I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s *inconsistent* now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again *now* using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to *either* know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) *or* about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔
@gallowsgryph Cool! 👌