# 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 194848
# self = https://watcher.sour.is?offset=194848
# prev = https://watcher.sour.is?offset=194748
[47°09′34″S, 126°43′36″W] --bad checksum--
[47°09′15″S, 126°43′43″W] --white noise--
@prologic I know you were away, but were you under a rock?! 😅
«Welcome to the #AutomatingGIS processes course! Through interactive lessons and hands-on exercises, this course introduces you to #GeographicDataAnalysis using the #Python programming language. If you are new to Python, we recommend you first start with the Geo-Python course (geo-python.readthedocs.io) before diving into using it for GIS analyses in this course.
Geo-Python and Automating GIS Processes (‘#AutoGIS’) have been developed by the Department of Geosciences and Geography at the University of Helsinki, Finland. The course has been planned and organized by the #DigitalGeographyLab. The teaching materials are openly accessible for anyone interested in learning.»
https://autogis-site.readthedocs.io/en/latest/
(via Paul Walter no linkedin)
#GIS #geoPython #geopandas #shapely #osmnx #networkx
«Welcome to the #AutomatingGIS processes course! Through interactive lessons and hands-on exercises, this course introduces you to #GeographicDataAnalysis using the #Python programming language. If you are new to Python, we recommend you first start with the Geo-Python course (geo-python.readthedocs.io) before diving into using it for GIS analyses in this course.
Geo-Python and Automating GIS Processes (‘#AutoGIS’) have been developed by the Department of Geosciences and Geography at the University of Helsinki, Finland. The course has been planned and organized by the #DigitalGeographyLab. The teaching materials are openly accessible for anyone interested in learning.»
https://autogis-site.readthedocs.io/en/latest/
#GIS #geoPython #geopandas #shapely #osmnx #networkx
Attention, bientôt l'équinoxe : un évènement cosmique si puissant qu'il pourrait faire changer la saison!
idée peut-être pas si con du jour : ajouter des entrées sur mon twtxt à partir de mon téléphone en utilisant markor + syncthing pour la publication
[47°09′17″S, 126°43′24″W] Storm recedes -- back to normal work
Did something bad happen in the world today? 🧐
[47°09′24″S, 126°43′47″W] Wind speed: 79kph -- batteries low
Doing a bit of 2018 Advent of Code now to relax. 🎄
@lyse Some stuff is actually more reliable, that’s true. It’s also waaaaaaaaaaay more expensive, though … :-)
I called it a day, yes. \o/
The worst thing you can do is make your infrastructure (switches, wifi, ...) depend on some cloud service. Because someone else is maintaining that service; you have no control over it. You 100% depend on that other person now. Very stupid idea.
Now guess what manufacturers are pushing for ...
Now guess who couldn't complete a task at work this Saturday morning, because a certain cloud service was down ...
IT is fucked. Throw it all away and start over.
[47°09′34″S, 126°43′01″W] Wind speed: N/A -- Cannot comunicate
@lyse Yep! Super fast and efficient! 😃
🧮 USERS:1 FEEDS:2 TWTS:1469 ARCHIVED:89989 CACHE:2669 FOLLOWERS:22 FOLLOWING:14
[47°09′36″S, 126°43′16″W] Wind speed: 75kph -- batteries low
[47°09′21″S, 126°43′27″W] Working impossible due to heavy rain
I would like to wish everyone, including all haters and losers (of which, sadly, there are many) a truly happy and enjoyable weekend!
Only plebeians and shabbos goyim care about politics, however. Naturally, the Jews *would* want you to sperg out about Trump in a hipster-protocol chat.
[47°09′40″S, 126°43′26″W] Working impossible due to blizzard
[47°09′26″S, 126°43′59″W] Working impossible due to thunderstorm
[47°09′01″S, 126°43′14″W] Automatic systems disengaged due to thunderstorm
🧮 USERS:1 FEEDS:2 TWTS:1468 ARCHIVED:89982 CACHE:2683 FOLLOWERS:22 FOLLOWING:14
@prologic ah! Well, keeping fingers crossed for you and family on that RV, for sure! 🤞🏻
@bender I wish 🤣 Nah work on-site thingy😆
[47°09′30″S, 126°43′37″W] Automatic systems disengaged due to blizzard
[47°09′55″S, 126°43′43″W] Weather forecast alert -- storm from NE
@prologic ah, I was wondering! Hoping you are having a good time, mate! Christening the new RV? :-)
[47°09′13″S, 126°43′25″W] Reading: 0.35000 PPM
God BLESS USA and mr. Trump
#musiquinta #DadRock
Não é um tema de que saiba muito para conseguir musicar apropriadamente, mas julgo que a "Fuel for Fire" dos #Metallica não fica mal:
https://youtu.be/PvF9PAxe5Ng
[47°09′32″S, 126°43′49″W] Reading: 1.64 Sv
[47°09′31″S, 126°43′42″W] --interrupted--
I'm out of town folks and away until tomorrow (have been all week)
Someone please ban 2929b's autistic spamming ass.
🧮 USERS:1 FEEDS:2 TWTS:1467 ARCHIVED:89975 CACHE:2680 FOLLOWERS:22 FOLLOWING:14
I know it doesn’t need to be said, but “Texudus” is not twtxt. It is an attempt to create a, arguably, “better way™️”. 🤭
@zvava ah, yes, that’s the only Texudus feed. It also seems it is a one way only feed.
@bender https://andros.dev/texudus.txt
, its url doesn't correspond to the feed either
@zvava which Texodus feed? That I know of, there is only one, or am I wrong?
@lyse @movq bbycll's nickname regex is /^([-_\p{N}\p{L}])+$/iu
because i don't like how english-centric only allowing ascii letters/numbers is though this only applies to local users as of now, currently all nicknames are tolerated when parsing remote feeds and i just do mentions how yarn does (just the feed url)
in the wild, i've noticed a texedus feed with spaces in the nick (where its spec explicitly disallows whitespace in the nick) and feeds with other symbols in the nick too. honestly, i think we should just tolerate arbitrary nicknames for sake of user expression (while stripping or converting unreasonable characters) and just leave them out of mentions
Sometimes, I wonder how my desktop looks to other people. Normal sighted people, I mean. For me, everything is much smaller and always slightly blurry (almost antialiased) because of my eyesight.
Maybe it *does* look horribly pixelated and super ugly to other people, and that’s why everyone prefers smoothed fonts and UIs and all that … ? 😂
[47°09′59″S, 126°43′08″W] --no signal--
@arne Hm, noch nie gemacht. 🤔 Machst du das von Hand oder mit Code?
@zvava Good question. This is the spec, I think:
https://twtxt.dev/exts/metadata.html#nick
It doesn’t say much. 🤔
In the wild, I’ve only seen “traditional” nick names, i.e. ASCII 0x21 thru 0x7E.
My client removes anything but r'[a-zA-Z0-9]'
from nick names.
is there consensus on what characters should(n't) be allowed in nick
s? i remember reading somewhere whitespace should not be allowed, but i don't see it in the spec on twtxt.dev — in fact, are there any other resources on twtxt extensions outside of twtxt.dev?
[47°09′38″S, 126°43′58″W] Dosimeter fixed
Pqp! A carteira de trabalho digital, um aplicativo do governo brasileiro, fazendo propaganda de um curso de IA. Quero socar (metaforicamente) todos que aprovaram e executaram essa *palhaçada*!*
For what I can gather, kind of a waste of time, not a good solution. I might be missing bits, or may haven't grasp the entire "story".
@rrraksamam someone has a huge crush on Emily Blunt, eh? 🤭
[47°09′37″S, 126°43′47″W] Dosimeter overflow
#MaradoWeekly #WeeklyPlant Week 37
Oxalis corniculata is growing and blossoming on my strawberries vase, giving it some unplanned color
[47°09′20″S, 126°43′10″W] Resetting dosimeter
[47°09′41″S, 126°43′59″W] Dosimeter malfunction
🧮 USERS:1 FEEDS:2 TWTS:1466 ARCHIVED:89964 CACHE:2691 FOLLOWERS:22 FOLLOWING:14
[47°09′28″S, 126°43′11″W] Reading: 1.36 Sv
You can still help sponsor the Brazilian national #Python conference!
You can also donate a ticket so that a student can attend!
#PythonBrasil2025
Python Brasil banner with QR codes for registration and the sponsorship information.
[47°09′18″S, 126°43′31″W] --bad checksum--
@lyse Omg, that is great. 😃
@lyse Omg, that is great. 😃
@zvava There would be only one hash for a message. Some to be defined magic date selects which hash to use. If the message creation timestamp is before this epoch, hash it with v1, otherwise hammer it through v2. Eventually, support for v1 could be dropped as nobody interacts with the old stuff anymore. But I'd keep it around in my client, because why not.
If users choose a client which supports the extensions, they don't have to mess around with v1 and v2 hashing, just like today.
As for the school of thought, personally, I'd prefer something else, too. I'm in camp location-based addressing, or whatever it is called. There more I think about it, a complete redesign of twtxt and its extensions would be necessary in my opinion. Retrofitting has its limits. Of course, this is much more work, though.
@thecanine Id like that too, it just can't come from me, because native mobile dev just isn't my thing 😢
@zvava And yes yarnd
does have a well documented API and two clients (CLI and unmaintained Flutter App)
[47°09′45″S, 126°43′45″W] Transfer 75% complete...
Interesting! The Great Firewall's leak from 11.9.2025.
[47°09′46″S, 126°43′50″W] Transfer 50% complete...
[47°09′18″S, 126°43′00″W] Transfer 25% complete...
🧮 USERS:1 FEEDS:2 TWTS:1465 ARCHIVED:89956 CACHE:2696 FOLLOWERS:22 FOLLOWING:14
@lyse i dont mind if the hash is not backward compatible but im not sure if this is the right way to proceed because the added complexity dealing with two hash versions isnt justified
regular end users wont care to understand how twt hashes are formed, they just want to use twtxt! so i guess i could work in protecting users from themselves by disallowing post edits on old posts or posts with replies, but i'm not fond of this either really. if they want to break a thread, they can just delete the post (though i've noticed yarn handling post deletes dubiously...)
on activitypub i do genuinely find myself looking through several month or even year old posts sometimes and deciding to edit/reword them a little to be slightly less confusing, this should be trivial to handle on twtxt which is an infinitely simpler specification
@bender @thecanine well now this has me thinking abt the feasibility of making an android twtxt app for pods, the actual apis of pods would have to be standardized (or the fucked up way that activitypub does it, where the "mastodon api" is the defacto client api (does yarn even have an api reference?)) or the client is just simply..a client..but editing feeds via PUT, PATCH, DELETE etc. is standardized!...? (not to mention i dont even know where to begin making an android app lmao)
@bender @thecanine well now this has me thinking abt the feasibility of making an android twtxt app for pods, the actual apis of pods would have to be standardized (or a fucked up version of how activitypub does it, where the "mastodon api" is the defacto client api (does yarn even have an api reference?)) or the client is just simply..a client..but editing feeds via PUT, PATCH, DELETE etc. is standardized!...? (not to mention i dont even know where to begin making an android app lmao)