# 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 194066
# self = https://watcher.sour.is?offset=189735
# next = https://watcher.sour.is?offset=189835
# prev = https://watcher.sour.is?offset=189635
Bon bah, cet aprèm, c'est sysupgrade #openbsd
Bon bah, cet aprèm, c'est sysupgrade #openbsd
@kat what did i fuck up this time lol
@kat what did i fuck up this time lol
i don't think it's normal to have to restart my yarnd instance every time i wanna see new posts right
i don't think it's normal to have to restart my yarnd instance every time i wanna see new posts right
@movq oh this would be handy! i think my feed's busted after the migration lol
@movq oh this would be handy! i think my feed's busted after the migration lol
[47°09′40″S, 126°43′51″W] --no signal--
If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?
Instead of
(#123467) hello foo bar
you would have
(#123467 http://foo.com/tw.txt) hello foo bar
or maybe even:
(#123467 2025-04-30T12:30:31Z http://foo.com/tw.txt) hello foo bar
This would greatly help in reconstructing broken threads, since hashes are obviously unfortunately one-way tickets. The URL/timestamp would *not* be used for threading, just for discovery of feeds that you don’t already follow.
I don’t insist on including the timestamp, but having *some idea* which feed we’re talking about would help a lot.
If we must stick to hashes for threading, can we maybe make it mandatory to always include a reference to the original twt URL when writing replies?
Instead of
(#123467) hello foo bar
you would have
(#123467 http://foo.com/tw.txt) hello foo bar
or maybe even:
(#123467 2025-04-30T12:30:31Z http://foo.com/tw.txt) hello foo bar
This would greatly help in reconstructing broken threads, since hashes are obviously unfortunately one-way tickets. The URL/timestamp would *not* be used for threading, just for discovery of feeds that you don’t already follow.
I don’t insist on including the timestamp, but having *some idea* which feed we’re talking about would help a lot.
@sorenpeter You're welcome 🤗 We'll run into each other again. I'm sure! 🤞
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
I'm with @andros and @eapl.me on this one. But I have also lost interest in twtxt lately and currently rethinking what digital tools truly add value to my life. So I will not spending my time on adding more complexity to Timeline. Still a big thanks to you @prologic for all the great work you have done and all the nice conversations both here and on our video calls.
i'm using netcat installed on an android phone as a gopher client rn lol
In my company we are using MinIO for local development.
Are there people who use Duolingo?
I am very agree with the article. For me, Kagi is the best search engine. A premium experience.
@movq Yes! There is a cause: The renewable energies.
In Spain there is a lot of dependence on renewable energies and this is a problem for maintaining the voltage in the network. Thus, a 60% loss was lost for 5 seconds. In cascade, the circuit breakers were automatically switched off.
The B-side of renewable energies. They produce electricity but not dynamic energy.
[47°09′03″S, 126°43′47″W] --bad checksum--
[47°09′42″S, 126°43′31″W] Wind speed: N/A -- Cannot comunicate
@peron wow 1650 cd??? ahi tiene que estar hasta la lambada. xD cuanto emites? quiero escucharlo! xD
🧮 USERS:1 FEEDS:2 TWTS:1326 ARCHIVED:86801 CACHE:2903 FOLLOWERS:22 FOLLOWING:14
He contado 1650 CDs en mi coleccion. Algunos pienso emitirlos en la radio de TP.
@kat which was your last post? 😊
A história do SIRESP é tão confusa que toda a gente se confunde. O governo do PS decretou a "nacionalização" do SIRESP - extinção da empresa e as suas funções sendo atribuídas à Secretaria-Geral do Ministério da Administração Interna (SGMAI).
Só que o governo caiu, e o governo em gestão adiou esta medida (indemnizando). Quando o governo AD tomou posse, retomou este processo, pagou à empresa para trabalhar até Abril de 2025 enquanto prepara a SGMAI para ficar com a pasta, o que deveria acontecer até Março de 2025.
O SGMAI não ficou com a pasta no primeiro trimeste, o Governo caiu, e portanto decidiu - em gestão - adiar essa nacionalização até ao fim do ano (pagando nova indemnização).
Mas é só uma questão de tempo?
Num debate na RTP3 entre deputados de PS e PSD, o do PSD queixou-se de como o SIRESP funciona, e disse que é porque o PS o nacionalizou. Só que isso ainda não aconteceu...
...e o PSD não disse que não quer que aconteça. Mas mais do que isso, diz o programa da AD: "A SIRESP, SA será integrada num instituto público, por forma a assegurar que as competências tecnológicas críticas estão internalizadas no Estado e devidamente financiadas".
Isto é, a nacionalização que não conseguiu fazer a tempo quer agora fazê-la (até ao fim do ano, suponho).
Mas então... de que se queixa o deputado do PSD, mesmo?
A história do SIRESP é tão confusa que toda a gente se confunde. O governo do PS decretou a "nacionalização" do SIRESP - extinção da empresa e as suas funções sendo atribuídas à Secretaria-Geral do Ministério da Administração Interna (SGMAI).
Só que o governo caiu, e o governo em gestão adiou esta medida (indemnizando). Quando o governo AD tomou posse, retomou este processo, pagou à empresa para trabalhar até Abril de 2025 enquanto prepara a SGMAI para ficar com a pasta, o que deveria acontecer até Março de 2025.
O SGMAI não ficou com a pasta no primeiro trimeste, o Governo caiu, e portanto decidiu - em gestão - adiar essa nacionalização até ao fim do ano (pagando nova indemnização).
Mas é só uma questão de tempo?
Num debate na RTP3 entre deputados de PS e PSD, o do PSD queixou-se de como o SIRESP funciona, e disse que é porque o PS o nacionalizou. Só que isso ainda não aconteceu...
...e o PSD não disse que não quer que aconteça. Mas mais do que isso, diz o programa da AD: "A SIRESP, SA será integrada num instituto público, por forma a assegurar que as competências tecnológicas críticas estão internalizadas no Estado e devidamente financiadas".
Isto é, a nacionalização que não conseguiu fazer a tempo quer agora fazê-la (até ao fim do ano, suponho).
Mas então... de que se queixa o deputado do PSD, mesmo?
help why didn't my last post go through
help why didn't my last post go through
@kat you are OK. Taking a deep breath, everything’s gonna be irie, mon. 😅
@kat i just did the migration to stuff on the cacher branch so i'm like WHAT IS HAPPENING
@kat i just did the migration to stuff on the cacher branch so i'm like WHAT IS HAPPENING
@kat oh ok i think it's slowly rebuilding stuff
@kat oh ok i think it's slowly rebuilding stuff
@prologic I'm very sorry but my feelings are similar to @eapl.me . For a long time I thought that Yarn was part of the Twtxt ecosystem, and not that Twtxt is an extension of Yarn. I don't feel comfortable with what has happened. I didn't expect this change of direction.
The nice part of Twtxt is that it is read by humans, with a simpler format. It's the heart of the social network.
I need to think for a little time, but I'm thinking of stopping my involvement in the community.
@kat I CAN'T SEE TWTXT.NET ANYMORE?! WHAT'D I DO IN THE MIGRATION HELP LOL
@kat I CAN'T SEE TWTXT.NET ANYMORE?! WHAT'D I DO IN THE MIGRATION HELP LOL
test can anyone see this pls reply if u can
test can anyone see this pls reply if u can
Or lynx on a linux/unix terminal .
My favorit browser fir gopher is overbite for android from gopher.floodgap.com or DiggieDog from Google Apps.
[47°09′55″S, 126°43′14″W] Wind speed: 54kph -- batteries low
@movq oh dear lord, take it away, take it away! LOL.
"El abuso de un niño es asunto de cualquiera que lo sepa" Esto lo mencionan en la docuserie de Netflix, El programa. Hay que parar con estos abusos.
@thecanine Yeah this is where I think all the _hype_ really falls down. It's all just a really really expensive search engine and auto-complete 🤦♂️ That's it!
@kat My eyes hurt, though. 🥴
@kat My eyes hurt, though. 🥴
@xuu, see this. The italics didn't come out.
@kat MinIO is a good choice for a self-hosted Object Storage (_compatible with S3 APIs_) 👌
@kat Don't be nervous, I make sure I test the shit™ out of things before anyone else does 🤣
gah i've been so busy working on love4eva! TL;DR i switched image backends from the test/dev only module i was using to the S3 one, but with a catch - i'm not using S3 or cloud shit!!! i instead got it to work with minio, so it's a middle ground between self hosting the image uploads & being compatible with the highly efficient S3 module. i'm super happy with it :)
i posted a patreon update that details the changes more: https://www.patreon.com/posts/i-am-now-working-127687614
that post says i didn't update my guide yet but i actually did like right after i made that post lol so you can CTRL+F
for minio stuff there!
gah i've been so busy working on love4eva! TL;DR i switched image backends from the test/dev only module i was using to the S3 one, but with a catch - i'm not using S3 or cloud shit!!! i instead got it to work with minio, so it's a middle ground between self hosting the image uploads & being compatible with the highly efficient S3 module. i'm super happy with it :)
i posted a patreon update that details the changes more: https://www.patreon.com/posts/i-am-now-working-127687614
that post says i didn't update my guide yet but i actually did like right after i made that post lol so you can CTRL+F
for minio stuff there!
@prologic exciting!!!!!! i'm SO SORRY i didn't get to doing the migration for my instance though - i've been really busy! TT but i hope to get to it sometime this week <3 i really wanna upgrade i think i'm just a bit nervous for whatever reason lol
@prologic exciting!!!!!! i'm SO SORRY i didn't get to doing the migration for my instance though - i've been really busy! TT but i hope to get to it sometime this week <3 i really wanna upgrade i think i'm just a bit nervous for whatever reason lol
@thecanine do you read ed zitron's newsletter? he writes in depth about how AI is a crock of shit it makes me feel normal for once
@thecanine do you read ed zitron's newsletter? he writes in depth about how AI is a crock of shit it makes me feel normal for once
@movq this looks really cool
@movq this looks really cool
@Yarn yo, what's up? I am busy running my business here!
@thecanine "*BuT cAnInE, tHe A(G)i ReVoLuTiOn Is NoW*” Hahahaha! Thanks for good laugh! 🤣
@thecanine Sorry, but you were expecting what now?! 🤣
@eapl.me this would be, what, the third time you leave? 😅 I jest around quite a bit, act as Devil's advocate, and am an overall maligned phaun, but please know that I appreciate you, and enjoy your engagement.
We will be here (maybe) if you ever decide to come back.
Once or twice a year, I make an effort to switch from dark mode / black terminals to light mode again.
It usually doesn’t end well, because the contrast is just not as good. There’s a reason that things like professional DAWs or CAD software use a dark theme.
With a heavy bold font, it’s much better:
https://movq.de/v/331aa40bde/s.png
My font doesn’t get any bolder than this, though. I’d have to make a new variant of it. Mhh. 🤔
Once or twice a year, I make an effort to switch from dark mode / black terminals to light mode again.
It usually doesn’t end well, because the contrast is just not as good. There’s a reason that things like professional DAWs or CAD software use a dark theme.
With a heavy bold font, it’s much better:
https://movq.de/v/331aa40bde/s.png
My font doesn’t get any bolder than this, though. I’d have to make a new variant of it. Mhh. 🤔
I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We've thrown this "argument" around in support of some of the proposals, and I just don't buy it (_sorry_). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.
@eapl.me I honestly believe you are overreacting here a little bit 🤣 I completely emphasize with you, it can be pretty tough to feel part of a community at times and run a project with a kind of "democracy" or "vote by committee". But one thing that life has taught me about open source projects and especially decentralised ecosystems is that this doesn't really work.
It isn't that I've not considered all the other options on the table (_which can still be_), it's just that I've made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and don't consider all the possible things that _could_ go wrong.
July 1st. 63 days from now to implement a backward-incompatible change, apparently not open to other ideas like replacing blake with SHA, or discussing implementation challenges for other languages and platforms.
Finally just closing #18, #19 and #20 without starting a proper discussion and ignoring a 'micro consensus' feels... not right.
I don't know what to think rather than letting it rest (May will be busy here) and focus on other stuff in the future.
twt-hash-v2.md#implementation-timeline
Vuelta a Starting Forth, ahora con el manejo de memoria
Vuelta a Starting Forth, ahora con el manejo de memoria
[47°09′03″S, 126°43′23″W] Wind speed: 94kph -- batteries low
@movq Oh, I see. I reckon I accidentally late April-fooled myself. :-D
It's an interesting comparison. I really should have thought about that.
You're right, the rendering would not be very spectacular. :-)
@prologic if I tell you I will lose the edge. I want to mass produce them, as a business venture. LOL.
@andros We don’t know the cause, yet, do we? 🤔
@andros We don’t know the cause, yet, do we? 🤔
@prologic that mechanical magical ball I built is doing a good job, thus far. :-P
AD - 32% PS - 26% CH - 19% IL - 6% L - 5% CDU - 4% BE - 3% PAN - 1%