url to be used for hashing. No matter if it points to a different feed or whatever. Just unsubscribe from malicious feeds and you're done.Since the first
url is used for hashing, it must never change. Otherwise, it will break threading, as you already noticed. If your feed moves and you wanna keep the old messages in the same new feed, you still have to point to the old url location and keep that forever. But you can add more urls. As I said several times in the past, in hindsight, using the first url was a big mistake. It would have been much better, if the last encountered url were used for hashing onwards. This way, feed moves would be relatively straightforward. However, that ship has sailed. Luckily, feeds typically don't relocate.
Sois la leche, os gusta más la idea de mi madre haciendo de castañera que hayamos conseguido una relatoria de la ONU ⌘ Read more****
En Star Trek, cuando viajan a nuestra era no usan Google como navegador sino DuckDuckGo.
Star Trek New Horizon. T2E3 ⌘ Read more****
Mira, me ha llamado mi madre contándome una buena historia.
Le han llamado del colegio del pueblo para que se disfrace de castañera y vaya a contarles historias a les niñes.
Les ha dicho que sí, pero que hablará de bellotas, que no hay castañas en la zona.
Está ilusionada, haciendo el mandil, buscando los cucuruchos y las trébedes.
Es muy ilusionante, porque este año iba a cerrar el colegio por falta de niñes. Y gracias a dos familias migrantes se ha mantenido abierto. ⌘ Read more****
(#abcdefghijkl https://example.com/tw.txt#:~:text=2025-10-01T10:28:00Z), because it can be simply hacked in to clients currently on hashv1 and provides an off-ramp to location-based addressing (though i still think the format should be changed to smth like #<abc... http://example.com/...> so it's cleaner once we finally drop hashes)
Handling it via the pod might work but I think it's not the best approach, external feeds and clients don't usually use a pod api but their own implementation, so any workaround won't work there.
That's why my proposals addressed those issues:
- the idea of using a "key" instead of the
url (with the url as a fallback), the key could even be a public key so it can be used verifieable in crypto functions- using the timestamp to prevent content changes to break threads (plus being simpler to implement)
- using an explicit thread reference with an alternative subject format (like
[#THREAD_ID] Hello world and replies with (#REPLY_ID) Ahoy) so the content can change without affecting the thread reference, and anyone can use their own schemes freely
The eye candy is always good to have.
cors-anywhere via docker in a minute and it would work the same.Still, I could write one with just a dozen lines of Go or Node.js, I might consider writing one after the client is working decently.
Há 33 anos atrás, ainda era a Internet Portuguesa uma criança, nasceu o primeiro #Talker Português, uma comunidade virtual que, 33 anos depois, continua activa.
Parabéns, #SelvaVirtual !
https://selva.grogue.org
Há 33 anos atrás, ainda era a Internet Portuguesa uma criança, nasceu o primeiro #Talker Português, uma comunidade virtual que, 33 anos depois, continua activa.
Parabéns, #SelvaVirtual !
https://selva.grogue.org
Há 33 anos atrás, ainda era a Internet Portuguesa uma criança, nasceu o primeiro #Talker Português, uma comunidade virtual que, 33 anos depois, continua activa.
Parabéns, #SelvaVirtual !
https://selva.grogue.org
url metadata field unequivocally treated as the canon feed url when calculating hashes, or are they ignored if they're not *at least* proper urls? do you just tolerate it if they're impersonating someone else's feed, or pointing to something that isn't even a feed at all?and if the first
url metadata field changes, should it be logged with a time so we can still calculate hashes for old posts? or should it never be updated? (in the case of a pod, where the end user has no choice in how such events are treated) or do we redirect all the old hashes to the new ones (probably this, since it would be helpful for edits too)
Como os comentaba el otro día, hemos participado como @tunubesecamirio en una relatoría de la ONU que habla del impacto en derechos humanos de los Centros de Datos, por su impacto en energía y agua
Es decir, un informe detallado donde explora como afecta este sector al derecho al agua y energía, y otros derechos humanos.
Podéis leerlo por aquí:
[https://tunubesecamirio.com/2025/09/30/el-relator-de-la-onu-muestra-el-impacto-en-los-derechos-humanos-al-agua-de-los-centro ... ⌘ [Read more](https://mastodon.social/@CorioPsicologia/115297635064585049)****
Hoy tengo la preocupación por la flotilla por las nubes.
https://globalsumudflotilla.org/tracker/ ⌘ Read more****
Using a copper wire or a similarly malleable material, pass it through a drilled hole, hammer it on one end until flat, then do the same on the other side.
It does the same job of a rivet but it's flatter and look nicer on both sides, it's of course weaker but still strong enough for small objects.
It's sometimes used to reduce risk of deformities due to heat in hand-crafted jewelry and to reduce costs of small tools.
Giving the user multiple choices to do the same things is what is great about protocols in general.
I too had the same issue being a browser-based request, so the only solution is using a proxy.
For testing (and real personal use) I rely on this one https://corsproxy.io/.
In my client, I first check if the source allows me to fetch it without issues first and fallback to prefixing with a proxy if it gives an error.
For security reasons the client don't give you a readable error for CORS, so you must use a catch-all for that, if it fails again with the proxy you can deal with any other errors it throws as you normally would (preferably outside of the fetch function).
After the fetching responded, I store the
response.url value to fetch it again for updates without having to do extra calls (you can store it verbatim or as a flag to be able to change the proxy later).Here an extract of my code:
t
export async function fetchWithProxy(url, proxy=null) {
return await fetch(url).catch(err => {
if (!proxy) throw err;
return fetch(`${proxy}${encodeURIComponent(url)}`);
});
}
// Using it with
const res = await fetchWithProxy('https://twtxt.net/user/zvava/twtxt.txt', 'https://corsproxy.io/?');
// Get the working url (direct or through proxy)
const fetchingURL = res.url;
// Get the twtxt feed content (or handle errors)
const text = await res.text();
I also plan to allow the user to define a custom proxy field, I like the solution used by Delta.chat in their android app, where you can define the URL format with a variable
https://my-proxy?$TWTXT_URL since it allows you to define with more freedom any proxy without a prefix format.If the idea of using a third-party proxy is not to the user liking they can use a self-hosted solution like
cors-anywhere or build their own (with twtxt it should just be a GET).
Qué bien que por fin se tipifíque como delito la violencia vicaria como violencia de género. ⌘ Read more****
Collection of purple poppy seeds and two of the pods they came from. The seeds are in a labeled packet with the date, useful for when we decide to plant them
Collection of purple poppy seeds and two of the pods they came from. The seeds are in a labeled packet with the date, useful for when we decide to plant them
Collection of purple poppy seeds and two of the pods they came from. The seeds are in a labeled packet with the date, useful for when we decide to plant them
He visto gorros por la calle...
#felizOtoño #felizMartes ⌘ Read more****
¡Mastdodón! ⌘ Read more****
A couple of weeks ago, I added CORS support, which is the source of the OPTIONS call. What I _didn't_ do was store the result so it stops trying to make further attempts. I'll get that in tomorrow.
As for the "If-Modified-Since" header, the server-based component of TwtStrm should be sending that (along with its user-agent tag and my user info). I wasn't sure if that could be sent with CORS requests, so I'll need to look into that a bit more.
Thanks, I appreciate the feedback!
#OpenStreetMap #FreeMaps #MapCarta
A ver, que se me ha olvidado lo de la ONU.
Este año hemos participado en una relatoria de la ONU, que hicieron especial sobre Agua y Energía sobre Derechos Humanos. Tenía un apartado especial sobre el tema del agua y los #centrosdedatos donde colaboramos como @tunubesecamirio
El informe había salido, y se me había pasado.
Mañana publicamos el tema. ⌘ Read more****
Ostrás, se me olvidó lo de la ONU 🫣 ⌘ Read more****
Access-Control-Allow-Origin header, so i just jumped into building a backend instead. did you find away around this limitation? :o
Em outubro vou dar este curso quintas à tarde com 4 encontros:
https://www.sescsp.org.br/programacao/ilustracoes-vetoriais-para-grandes-formatos-com-programacao/
#SescSP #TecnologiasEArtes
Captura de tela da página do curso no site do Sesc
Put up lots of thermometers and hygrometers in the apartment, have them report their readings wireless to a database.
I suspect that I’ll have to “build” these myself, because ready-to-use kits most like require some sort of cloud service. Dunno, haven’t checked yet.
Financial Times ha sacado esta pieza donde analiza la desaparición de los trabajos de iniciación al mercado laboral.
Uno de los elementos que analiza es la irrupción de la IA.
Como anécdota personal, puedo contar que el 30% de las tareas que realizaba en mis primeros 5 años de trabajo ahora las hacen IA, y me contrataron precisamente por esas tareas.
https://www.youtube.com/watch?v=IeTFpsuCor8
#JobApocalipsis [ ... ⌘ [Read more](https://mastodon.social/@CorioPsicologia/115288689770963537)****
El final de temporada, y serie? de Andor se está volviendo súper emocionante!
#andor2 ⌘ Read more****
I decided against blind rivets, because they leave ugly looking and sharp backsides, which can also interfer with the contents of the box. However, they would be an easy solution to make the corners more rigid and prevent any movement from the short sides.
Unfortunately, I can't weld or solder, so that's not an option. It would be the by far best solution. I wanna learn it one day, though.
Yes, Ken is a really great dude. He's the reason I gave this a shot in the first place. :-)
I can confirm, the
User-Agent header appears to be fixed. \o/Two other things I noticed, though:
1. There's now an
OPTIONS request for my feed coming from something that claims to be Firefox, pointing to your feed URL in the query. No clue what this is about. In any case, it's rejected with a 405 Method Not Allowed.2. Not that these few requests bother me at all, but you might wanna implement caching next with either the
If-Modified-Since or If-None-Match request headers. This way, if the feed hasn't changed, the web server can reply with a 304 Not Modified and no body at all, saving unnecessary traffic. But again, this is really not an issue for me at all. I just wanted to make sure you're aware of it, that's all. It might be even already on your agenda. Or you might decide to never do anything about it, which is also fine for me. :-)
No entanto, muitos nutrem uma tóxica noção de superioridade em relação aos pedestres: furam a sinalização, cruzam de qualquer jeito a faixa de pedestre, assustam a gente e tiram finas. É detestável isso.
Não seja ciclista com a mente carrocrata.
Bueno bueno, como no se atreve a quitarme el día de teletrabajo que pacté con él, me pone las reuniones ese día.
Bien jugado Boss!
#felizLunes ⌘ Read more****
Si alguien quiere prepararse unas oposiciones, y no puede permitirse academias privadas, está esta maravillosa iniciativa:
Funcionarios públicos dando formación gratis para que haya más opositores de clase obrera:
https://www.eldiario.es/sociedad/academia-prepara-opositores-forma-gratuita-hay-evitar-haya-funcionarios-clase-social\_1\_12622767.html ⌘ Read more****
BTW - I promise, I intended it to be pronounced like "TweetStream" (or as written, "TwtStrm"), rather than "TweetStorm". Sorry again. 😊
After another round of coding this weekend, I'm happy to report that it now renders _all_ the twts (with markdown parsing), complete with
localstorage and server-based file caching.
zs looks pretty cool! I love simple static site generators, and look forward to trying it on my next web site project. Kudos!
To build a compliant PWA you need to provide a webmanifest json and a service worker.
Those requirements are not directly part of this project.
You can build the client as a standalone PWA or even as a widget inside an existing page.
The general steps are closer to how you would include a third-party library in an existing project, by importing it as a dependency and using it in your website.
I'm pretty sure most users would expect a PWA (me included) so I plan to provide a ready-made template ready to be deployed as is.
Después de días incubando, el resfriado/gripe se ha manifestado con toda su fuerza.
Me alegro que me haya dado tiempo para disfrutar de la manifestación en Zgz. ⌘ Read more****
The client I'm developing is a single tenant project that runs entirely in the browser (it might use an optional backend).
It's entirely based on native web-components and vanilla JS, it is designed to act closer to a toolkit than a full-fledged client, allowing users to "DIY" their own interface with pure html or plain javascript functions.
Users can also build their own *engines* by including a global javascript object that implement the defined internal API (TBD).
I'm planning to build a system that is easy enough to build and use with any skill level, using only pure html (with a homebrew minimal template engine) or via plain JS (I'll be also providing some pre-made templates too).
Everything can be self-hosted on any static hosting provider, this allows to spread twtxt within communities like Neocities and similarly hosted websites (basically any Indieweb/Smallweb/Digital garden website and any of the common GitHub/Lab/Berg/lify Pages).
It will be probably named something like TxtCraft or craf.txt but I'm not really sure yet... 🤔 (Maybe some suggestions could help)
I'm still in the experimental phase, so there's no decent source-code to share yet, but it will soon enough!
BTW, That Sheet Metal Dude is something else himself, skilled enough to teach others, can work properly with self-imposed contraints, care about safety and is humble enough to be wiling to learn from others, a true craftman worthy of respect.
The new blog for prologic.blog soon to be powered by zs using the zs-blog-template is coming along very nicely 👌 It was _actually_ pretty easy to do the migration/conversation in the end. The results are not to shabby either.
Before:
- ~50MB repo
- ~267 files
After:
- ~20MB repo
- ~88 files