# 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 238097
# self = https://watcher.sour.is?offset=232649
# next = https://watcher.sour.is?offset=232749
# prev = https://watcher.sour.is?offset=232549
I’ve never liked the behavior of OpenBSD’s shell where it just scrolls horizontally:
https://movq.de/v/1371f7efbc/vid-1741714971.mp4
But now I’m *this close* to implementing the same thing in my own shell – because it’s probably *much, much easier* than multiline stuff. 😅
@aelaraji That's nice, enjoy it while it lasts! Rain can be something wonderful. Stay safe.
@aelaraji That’s how twtxt started: As microblogging. Yarn shifted up some gears and now it’s more like social media – more powerful, but a bit different. 😅
@aelaraji That’s how twtxt started: As microblogging. Yarn shifted up some gears and now it’s more like social media – more powerful, but a bit different. 😅
Black swans occur when an event with a high negative impact but low probability occurs.
regardless of the technical maintenance and creating backdoors for the sake of the maintenance and put the risk in front of the security calls the black swans immedietly.
looks like CVE-2025-27840 can't be triggered remotely by Bluetooth, radio signals, or over the Internet, meaning they do not pose a risk of remote compromise of ESP32 devices
@kat @prologic When I make dev on current master, I get a proper version. Same with make server. Assuming you cloned the repo, do you have any (uncommited) changes? What does git status tell you?
Of course, @bender, anytime! <3 As our number one bug finder, your service has to be rewarded. :-)
[47°09′10″S, 126°43′16″W] Dosimeter malfunction
> twtxt is a decentralised, minimalist microblogging service for hackers.
The keyword here is microblogging. But it doesn't feel like we've been (relatively speaking) doing much of that lately... maybe I go the concept of microblogging wrong.
It's been ages since the last time we've had as much and as frequent of a rainfall as we've been having this week. The smell, the sounds, the wind pushing against my body ... are taking over my senses with joy, leaving no room for worry™ (about the possibility of a flood).
i am awake and my headache is gone yayyy
i am awake and my headache is gone yayyy
@prologic make server actually because i don't need the client on my server, also i run make deps before just in case lol
@prologic make server actually because i don't need the client on my server, also i run make deps before just in case lol
@prologic huh interesting! yeah i was stumped for a bit i was like WHAT config.json file are these logs talking about.... but then it worked after i moved the old meta.json file lol!
@prologic huh interesting! yeah i was stumped for a bit i was like WHAT config.json file are these logs talking about.... but then it worked after i moved the old meta.json file lol!
[47°09′16″S, 126°43′23″W] 4345 days without news from Herve
this esp32 issue is tracked under CVE-2025-27840... Looks like I should try alternative chips for meshtastic!
whoa! esp32 = 29 undocumented commands, collectively characterized as a backdoor, that could be used for memory manipulation, MAC address spoofing and packet injection=
meshtastic looks promising, i'm starting to explore esp32 platforms and it doesn't look that dificult to setup.
@doesnm Actually that's a fantastic idea 🙌
@kat Actually that's' a known bug I haven't worked out yet hmmm 🧐
@kat Arw you running make build or go build?
[47°09′10″S, 126°43′25″W] Raw reading: 0x67CFED82, offset +/-4
[47°09′13″S, 126°43′47″W] Weather forecast alert -- storm from SW
👋 Hello @death, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @death, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
i rebuilt the yarnd binary several times and yet the version print is still omitting the first letter lol? wtf
i rebuilt the yarnd binary several times and yet the version print is still omitting the first letter lol? wtf
oh god i have a horrible headache i know it'll only go away if i sleep but i don't wanna sleep yet T_T
oh god i have a horrible headache i know it'll only go away if i sleep but i don't wanna sleep yet T_T
👋 Hello @radiantgarden, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @radiantgarden, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @hydaelyn, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
👋 Hello @hydaelyn, welcome to yarn, a Yarn.social Pod! To get started you may want to check out the pod's Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗
idfk where the error came from it just broke one day, maybe from one of my many server crashes which are becoming frequent and UGH i have to fix that too but i have a headache right now so one thing at a time. the error was 'unexpected end of JSON input' or something, for a while i thought oh permission error but turns out i can't read the error that clearly indicated something syntax related (i did double check my env file though)
idfk where the error came from it just broke one day, maybe from one of my many server crashes which are becoming frequent and UGH i have to fix that too but i have a headache right now so one thing at a time. the error was 'unexpected end of JSON input' or something, for a while i thought oh permission error but turns out i can't read the error that clearly indicated something syntax related (i did double check my env file though)
@kat it was like.... meta.json was corrupt or well it was empty actually whatever idk. ended up moving that elsewhere temporarily, rebuilding the binary, restarting server... and it worked?!?!? shit was confusing
@kat it was like.... meta.json was corrupt or well it was empty actually whatever idk. ended up moving that elsewhere temporarily, rebuilding the binary, restarting server... and it worked?!?!? shit was confusing
HI EVERYONE MY INSTANCE DIED FOR A WHILE AND MY LIFE TURNED TO SHIT SO I COULDN'T FIX IT BUT I JUST DID YAYYYYYYYY
HI EVERYONE MY INSTANCE DIED FOR A WHILE AND MY LIFE TURNED TO SHIT SO I COULDN'T FIX IT BUT I JUST DID YAYYYYYYYY
Detesto cuando me quieren imponer las cosas, si no puede elegir entonces no quiero.
🧮 USERS:1 FEEDS:2 TWTS:1272 ARCHIVED:85120 CACHE:2798 FOLLOWERS:18 FOLLOWING:14
It is super cool to be listed as a "contributor" for having chimed in (constructively) on a project's issue :D
https://github.com/nathanrooy/taxicab/releases/tag/v0.1.1
#taxicab is a library that improves on #OSMnx route-finding function, giving more useful results, specially on short routes.
#geopython #python
@prologic oops, I'm sorry to see disagreement leading to draining emotions.
It remind me a bit of the Conclave movie where every part wanted to defend their vision and there is only a winner. If one wins the other loses. Like the political side of many leaders and volunteers representing a broad community. I don't think that's the case here. Most of us (in not all) should 'win'.
I can only add that isn't nice to listen that 'my idea and effort' is not what the rest of the people expect. I personally have a kind of issue with public rejection, but I also like to argue, discuss and even fight a bit. "A gem cannot be polished without friction, nor a man perfected without trials," they say.
This exercise and belonging to this community also brings me good feelings of smart people trying to solve a human and technical problem, which is insanely difficult to get 'right'.
I genuinely hope we can understand each other, and even with our different and respectful thoughts on the same thing, we might reach an agreement on what's the best for most people.
Good vibes to everyone!
#testing @ Hi Bob, nice to meet you!
#testing @ Hi Bob, nice to meet you!
#testing @ Hi Bob, nice to meet you!
#testing @ Hi Bob, nice to meet you!
[47°09′34″S, 126°43′13″W] Transfer aborted
@lyse deeply honored to be used as an example, when illustrating things that will break! :-D <3
[47°09′48″S, 126°43′32″W] Transfer 75% complete...
Why not just use registry? It can be personal or hosted by someone like registry.twtxt.org. Just need to be adapt to support hashes
If we don't keep insisting on simplify and "The beauty of twtxt is, you put one file on your server, done. One.", then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.
If we don't keep insisting on simplify and "The beauty of twtxt is, you put one file on your server, done. One.", then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.
If we don't keep insisting on simplify and "The beauty of twtxt is, you put one file on your server, done. One.", then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.
If we don't keep insisting on simplify and "The beauty of twtxt is, you put one file on your server, done. One.", then people should just use ActivityPub-based software like Mastodon, PixelFed, etc. which are getting a lot of attention and uses migrating to the fediverse from meta/x here in Denmark over the last couple of months.
[47°09′24″S, 126°43′33″W] Transfer 50% complete...
@lyse I also think we need to remove ourselves a bit from the "Twtxt" format as it was originally designed by Buckket.
> The beauty of twtxt is, you put one file on your server, done. One.
I'm not talking (_nor ever was here_) about that. We should be allowed to and encourage dot evolve its usage and our own.
It would be far better as a community to focus on the utility of our tools, services, protocols, formats and specifications as well as our own clients and usages thereof rather than this "idealised" design from (c) 2016.
If you strongly disagree with this, then I think I'll just honestly step away from all of this as the back 'n forth on this whole "beaty" and "simplify" argument is honestly wearing me down 😢
@lyse Sorry I didn't mean to upset you or anyone here in the community. I am/was merely trying to solve what I perceive to be a problem and an ask in the community:
> How do I know what a hash refers to?
I believe the reason for this stems from a curiosity of the user of whether they _might_ find that thread interesting or whether there are new interested feeds to follow?
Although my idea increases complexity slightly (_introducing a new concept_) I don't think it's particular hard to understand, reason about or implement (_complicated_). One could even even make the implementation quite simple in fact.
Either way, the idea of a service (_cantralised_) or participating clients/registries (_distributed_) providing reverse hash lookups doesn't sound too bad really.
What do you propose to solve the above problem? 🤔
I went for a run this morning after months of not running and it feels so good!
@prologic We can't agree on this idea because that makes things even more complicated than it already is today. The beauty of twtxt is, you put one file on your server, done. One. Not five million. Granted, there might be archive feeds, so it might be already a bit more, but still faaaaaaar less than one file per message.
Also, you would need to host not your own hash files, but everybody else's as well you follow. Otherwise, what is that supposed to achieve? If people are already following my feed, they know what hashes I have, so this is to no use of them (unless they want to look up a message from an archive feed and don't process them). But the far more common scenario is that an unknown hash originates from a feed that they have not subscribed to.
Additionally, yarnd's URL schema would then also break, because https://twtxt.net/twt/<hash> now becomes https://twtxt.net/user/prologic/<hash>, https://twtxt.net/user/bender/<hash> and so on. To me, that looks like you would only get hashes if they belonged to this particular user. Of course, you could define rules that if there is a /user/ part in the path, then use a different URL, but this complicates things even more.
Sorry, I don't like that idea.
[47°09′14″S, 126°43′22″W] Transfer 25% complete...
Das Gemälde eines Waldgasthofes vor einer holzvertäfelten Wand Das mitteldeutsche Twin Peaks.
[47°09′31″S, 126°43′51″W] Carrier too weak
One of the biggest gripes of the community with the way the threading model _currently_ works with Twtxt v1.2 (https://twtxt.dev) is this notion of:
> What is this hash?
> What does it refer to?
Idea: Why can't we all agree to implement a simple URI scheme where we host our Twtxt feeds?
That is, if you host your feed at https://example.com/twtxt.txt -- Why can't or could you not also host various JSON files (_let's agree on the spec of course_) at https://example.com/twt/<hash> ? 🤔
That way we solve this problem in a truly decentralised way, rather than every relying on yarnd pods alone.
Power outages throughout south east queensland (map) 
5 miles: 5.18 miles, 00:09:18 average pace, 00:48:08 duration
finishing the 13 miles. this felt really easy on tired legs.
#running #treadmill
5 miles: 5.18 miles, 00:09:18 average pace, 00:48:08 duration
finishing the 13 miles. this felt really easy on tired legs.
#running #treadmill
5 miles: 5.18 miles, 00:09:18 average pace, 00:48:08 duration
finishing the 13 miles. this felt really easy on tired legs.
#running #treadmill
🧮 USERS:1 FEEDS:2 TWTS:1271 ARCHIVED:85113 CACHE:2793 FOLLOWERS:18 FOLLOWING:14
Ontem voltei a pegar no Django depois de 10 anos para um side-project. É como se fosse um regresso a um lugar onde um dia se foi feliz.
Tem a sua personalidade e tal, mas continuo a adorar os seus pormenores e as suas escolhas sobre como deve funcionar uma framework web.
Também fiquei muito agradado de ver que muito pouco mudou desde há uma década no que toca à forma fundamental como o Django faz as coisas. Talvez isso não seja apreciado pela juventude habituada a ciclos de upgrade rápidos e drásticos, mas pra mim foi um grande alívio ver que não tenho de me atualizar muito para montar um pequeno projeto.
Há gente djangueira por aí?
#python #django