# 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 194447
# self = https://watcher.sour.is?offset=194447
# prev = https://watcher.sour.is?offset=194347
wait....so i'm like nearly done? it just _works_? and it's _fast_? this feels like the end of the first all-nighter i pulled where i just got post creation done, unaware of the three weeks that would follow — like looking at the roadmap i'm definitely not _done_ but bbycll is like actually kind of usable now o.o
ok so i have found a genuine twt hash collision. what do i do.
internally, bbycll relies on a post lookup table with post hashes as keys, this is really fast but i knew i'd inevitably run into this issue (just not so soon) so now i have to either: 1) pick the newer post over the other 2) break from specification and not lowercase hashes 3) secretly associate canonical urls or additional entropy with post hashes in the backend without a sizeable performance impact somehow
Great. Yet another messed up plain text e-mail part. The URL was actually HTML-escaped. Took me five attempts to figure this out, because of course it had to be several kilometers long. In fact, the e-mail stated: "Please do not be surprised that the link is particularly long. It contains your personal configuration."
A normal person is completely lost (that's why I got involved). Visting the broken URL opens a popup dialog suggesting to deactivate script blockers. Which I had already done upfront as a matter of prudence.
Fun bonus on top: The JWT in the link has identical iat (issued at) and exp (expiry) claims. The expiry is definitely not checked, it's well in the past.
Medical software just has to be horrible. It's a law.
@kat@kat Pretty sure I have many more mentions in the database than the one and only one I see hmmm 🤔 -- I'll have a look at the code when I can and the SQL query it's using
@bender Absolutely. My computer science teacher was really great and in a lot of aspects very similar. Especially combining the theoretical and practical parts. He's also the main reason I ended up where I am today. I'm very grateful to him. Mr. Burger, however, takes this on a whole new level.
@kat The duck was in a darker spot, so my camera wasn't all that happy with the lighting. Upon further inspection, you're right, now that you pointed it out, I can see it too! The feathers do look like an oil painting. ;-)
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases....my friend's feed with like four posts parsed correctly so i tried this account's feed and well now im not going to bed on time
we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases....my friend's feed with like four posts parsed correctly so i tried this account's feed and well now im not going to bed on time
@bender ty for attempting to test, though, it means a lot! lmk if u find any more silly things i need to clarify or fix :> be prepared for everything breaking during beta :p
@bender i also recently discovered there was a bug causing new users to initialize wrong leading to their posts not being saved :p ..and made breaking changes to how the config and database files are stored so um, make sure to clear your local tree before updating!
@bender as the host (eg twtxt.net) determines the canonical url of the instance in generated feed url metadata as well as every hash of every post made on the instance internally, i added this error message to make sure people don't accidentally set up their instance on localhost :p for testing i set it to localhost:31212 and protocols to ["http"], it's a recent addition that could definitely do with documenting in the getting started section
Já cá canta a 7ª edição do #SHIFTER em formato revista! Todos os números são bons e têm o seu quê de especial - este com o tema "RIP INTERNET" promete não ser diferente nisso...
It was nice to start a walk in the woods with sunshine. The last times it was all soupy. It was quite windy, autumn is certainly here. Soon, the leaves will begin to turn. https://lyse.isobeef.org/waldspaziergang-2025-09-11/
Cheers @mkennedy@mkennedy & @brianokken@brianokken , listening late to @pythonbytes@pythonbytes episode 446, great as usual!
Listening to the JetBrains survey thing I always worry about the sampling bias... All the cool scientists using Python, all the journalists doing data journalism, the urban planners and geospace people, the blender people, the people doing movie post-production pipelines, all the hobbyists... I think the survey doesn't reach or represent a large chunk of Python users.
@lyse retwts are a discovery feature! on federated platforms with no algorithm where you only ever see posts from accounts you explicitly follow, the element of "hey look at this!" helps users to find other accounts they might like organically
i agree quoting and replying forum-style is generally a much better way of doing things even though im a heathen and i revel in the dark patterns inspired by quote posts but when you have nothing to add and you just want to share a twt with your followers it'd be good to have a standardized way of linking to twt
@bender@kat after implementing cws in bbycll (parsing them the way i described in op) i understand why <details> aren't rendered. firstly they're not actually markdown, and secondly they style weird — details are forced onto a new line as a block element but you can't make the <summary> inline because it is inside <details>, and making <details> inline will also indent everything inside it
@mozilla@mozilla must have some telemetry or metrics or something to know how many #32bit firefox users are out there. I bet that, as a percentage, they aren't more than a blip. Still, there has to be several thousand machines out there, running on 32bit hardware, connected to the internet, using #Firefox as its web browser.
And now Mozilla decided to hand those users over to #chromium, by stopping 32-bit support and telling them the alternative is to install a 64bit OS instead.
A música "My Monkey" de #MarilynManson deveria ser a mais óbvia escolha para esta #musiquinta sobre #macaco - mas desde quando é que temos e ir pelo óbvio? E assim sendo, escolho em vez disso outra música da banda - podia ser a Organ Grinder (que também refere o 'funny little monkey' que depois tem a sua própria música), mas em vez disso escolho a "Cruci-fiction In Space", da mesma banda mas já do seu quarto album, publicado após o massacre de Columbine - sobre o qual o artista foi indevidamente crucificado. De certa forma, parece-me uma escolha adequada para os dias de hoje...
Sou eu que já estou muito cansado, ou este texto no DN deve ter sido escrito por IA e não faz sentido nenhum?
"Se uma greve geral chegar a acontecer, será a primeira vez nos últimos 12 anos, pois a última paralisação convocada por ambas as centrais sindicais ocorreu em junho de 2023."
What #TheLEFT had to say about #vonderleyen 's #SOTU speech?
There are several news stories going around saying that there are two no-confidence votes to Von Der Leyen about to be submitted, saying little to nothing about them, and even filing them together as if they both want or mean the same.
It might be useful to know exactly what the criticisms are, so here is a link to The Left's comment to today's speech. Read it in full, but here is my summary:
* "acts as the guardian of the interests of the most powerful, at the expense of democracy, justice, and the future of the planet";
* Gaza: "The bare minimum is ending military cooperation and fully suspending the EU–Israel Association Agreement. This is genocide and we need to do everything to stop it"
* pushing the MERCOSUR deal (they are actually light on their criticism of this treaty, but I'll leave my rant about ot on a another toot)
* the EU-US deal: "subjugation of European policy to the economic and military interests of the USA. You are sacrificing energy, digital policy, security, and climate protection on the altar of the hollow phrase of transatlantic partnership"
* "Europeans’ living standards are falling, jobs are lost, authoritarianism grows, and social systems are under pressure"
@kat I reckon the original <details> need to have the open attribute set in order to expand it, so I cannot just define some custom CSS rules to do that in my browser.
But in regards to twtxt, my client won't hide anything in that realm anyway. :-) It's just more noise.
On m'a fait remarquer que mon serveur n'était pas accessible en ipv6... Merci! Je ne m'en apercevais pas depuis chez moi. Encore une histoire du firewall obscur de mon routeur :/. Là, normalement, c'est bon. ???
On m'a fait remarquer que mon serveur n'était pas accessible en ipv6... Merci! Je ne m'en apercevais pas depuis chez moi. Encore une histoire du firewall obscur de mon routeur :/. Là, normalement, c'est bon. ???
@dce Nope. 😃 What’s that genre called? Sounds like old horror movies from the 70'ies (or it could be a soundtrack to Salad Fingers, if anyone remembers that).
@kat Ta. The only good use for <details> is to collapse long logs in bug analysis reports. Other than that, I find it rather annoying to expand sections manually.
As for spoilers, personally, I don't care at all. Not the slightest bit. If there is something that I don't wanna read, I just stop reading. ¯\_(ツ)_/¯
But I've got the feeling that I've got an unpopular opinion on that matter. ;-)_
@bender I see, thanks. Well, I never found these warnings useful. To hide answers to conundrums or the like, ROT13ing or base64-encoding them is plenty sufficient.
Hahaha, I never heard of Poopgate before. :-D Poor passengers.
@lyse a content warning is kind of like a forum spoiler cut, or like the
<details>
tag in HTML; it lets you write a sentence or so that someone can then click to expand to see the actual post. it's called a CW because most people use it to warn for potentially triggering/harmful subjects, but you can really use it for anything, like spoilers in a TV show or even for joke punchlines
Sunset
Cartaz para o dia 12  
Uma pilha de revistas e autocolantes SHIFTER
Privacy-concerned duck in a creek