This might be quite unpopular, but I truly dislike Wordle. The reason isn’t rooted on any psychological issue, it is much, much more simple: people share their Wordle result(s)—I figure they feel good about themselves—and for me it is only uneven, unaligned, wasteful noise. I don’t even want to show you an example, but I am sure you know what I am talking about.

Thank gods those posting their hideous squares have finally quieted down. LOL.

@aelaraji@aelaraji.com this is the little script I am using on my publish_command:

#!/usr/bin/env bash

twtxt2html -t "Quark's twtxt feed" /var/www/sites/ferengi.one/twtxt.txt > /var/www/sites/ferengi.one/index.html

I named it twtxtit. :-)

@quark@ferengi.one It looks like the part about traditional topics has been removed from that page. Here is an old version that mentions it: https://web.archive.org/web/20221211165458/https://dev.twtxt.net/doc/twtsubjectextension.html . Still, I don’t see any description of what is actually allowed between the parentheses. May be worth noting that twtxt.net is displaying the twts with the subject stripped, so some piece of code is recognizing it as a subject (or, at least, something to be removed).

@falsifian@www.falsifian.org based on Twt Subject Extension, your subject is invalid. You can have custom subjects, that is, not a valid hash, but you simply can’t put anything, and expect it to be treated as a TwtSubject, me thinks.

Ignite Realtime Blog: Openfire HTTP File Upload plugin v1.4.1 release!
We have now released version 1.4.1 of the HTTP File Upload plugin!

This plugin adds functionality to Openfire that allows clients to share files, as defined in the XEP-0363 ‘HTTP File Upload’ specification.

This release brings two changes, both provided by community … ⌘ Read more

Trying to figure out how to use the publish_command to vomit the HTML into a file, using twtxt2html.

It should be fixed now. Just needed some unusual quoting in my httpd.conf: https://mail-archive.com/misc@openbsd.org/msg169795.html

On my blog: Developer Diary, Ozone Day https://john.colagioia.net/blog/2024/09/16/ozone-layer.html #programming #project #devjournal

On my blog: Chosen https://john.colagioia.net/blog/2024/09/15/chosen.html #fiction #freeculture

On my blog: Free Culture Book Club — Aumyr, part 2 https://john.colagioia.net/blog/2024/09/14/aumyr-2.html #freeculture #bookclub

@mckinley@twtxt.net

HTTPS is supposed to do [verification] anyway.

TLS provides verification that nobody is tampering with or snooping on your connection to a server. It doesn’t, for example, verify that a file downloaded from server A is from the same entity as the one from server B.

I was confused by this response for a while, but now I think I understand what you’re getting at. You are pointing out that with signed feeds, I can verify the authenticity of a feed without accessing the original server, whereas with HTTPS I can’t verify a feed unless I download it myself from the origin server. Is that right?

I.e. if the HTTPS origin server is online and I don’t mind taking the time and bandwidth to contact it, then perhaps signed feeds offer no advantage, but if the origin server might not be online, or I want to download a big archive of lots of feeds at once without contacting each server individually, then I need signed feeds.

feed locations [being] URLs gives some flexibility

It does give flexibility, but perhaps we should have made them URIs instead for even more flexibility. Then, you could use a tag URI, urn:uuid:*, or a regular old URL if you wanted to. The spec seems to indicate that the url tag should be a working URL that clients can use to find a copy of the feed, optionally at multiple locations. I’m not very familiar with IP{F,N}S but if it ensures you own an identifier forever and that identifier points to a current copy of your feed, it could be a great way to fix it on an individual basis without breaking any specs :)

I’m also not very familiar with IPFS or IPNS.

I haven’t been following the other twts about signatures carefully. I just hope whatever you smart people come up with will be backwards-compatible so it still works if I’m too lazy to change how I publish my feed :-)

On my blog: Toots 🦣 from 09/09 to 09/13 https://john.colagioia.net/blog/2024/09/13/week.html #linkdump #socialmedia #quotes #week

On my blog: Real Life in Star Trek, Cause and Effect https://john.colagioia.net/blog/2024/09/12/cause-effect.html #scifi #startrek #closereading

On my blog: Developer Diary, Chrysanthemum Day https://john.colagioia.net/blog/2024/09/09/chrysanthemum.html #programming #project #devjournal

On my blog: Holding Universal Access to All Knowledge Hostage https://john.colagioia.net/blog/2024/09/08/internet-archive.html #politics #rant

On my blog: Free Culture Book Club — Aumyr, part 1 https://john.colagioia.net/blog/2024/09/07/aumyr-1.html #freeculture #bookclub

On my blog: Toots 🦣 from 09/02 to 09/06 https://john.colagioia.net/blog/2024/09/06/week.html #linkdump #socialmedia #quotes #week

On my blog: Real Life in Star Trek, The Outcast https://john.colagioia.net/blog/2024/09/05/outcast.html #scifi #startrek #closereading

@prologic@twtxt.net I believe you when you say registries as designed today do not crawl. But when I first read the spec, it conjured in my mind a search engine. Now I don’t know how things work out in practice, but just based on reading, I don’t see why it can’t be an API for a crawling search engine. (In fact I don’t see anything in the spec indicating registry servers shouldn’t crawl.)

(I also noticed that https://twtxt.readthedocs.io/en/latest/user/registry.html recommends “The registries should sync each others user list by using the users endpoint”. If I understood that right, registering with one should be enough to appear on others, even if they don’t crawl.)

Does yarnd provide an API for finding twts? Is it similar?

I just manually followed the steps at https://dev.twtxt.net/doc/twthashextension.html and got 6mdqxrq. I wonder what happened. Did @cuaxolo@sunshinegardens.org edit the twt in some subtle way after twtxt.net downloaded it? I couldn’t spot a diff, other than ‘ appearing as ’ on yarn.social, which I assume is a transformation done by twtxt.net.

On my blog: Developer Diary, Emma Nutt Day, Belated https://john.colagioia.net/blog/2024/09/02/emma-nutt.html #programming #project #devjournal

On my blog: Weird Enough? https://john.colagioia.net/blog/2024/09/01/weird.html #harm #politics #rant

On my blog: Free Culture Book Club — Geiko Eien Ni https://john.colagioia.net/blog/2024/08/31/geiko-eien-ni.html #freeculture #bookclub

On my blog: Toots 🦣 from 08/26 to 08/30 https://john.colagioia.net/blog/2024/08/30/week.html #linkdump #socialmedia #quotes #week

On my blog: Real Life in Star Trek, Ethics https://john.colagioia.net/blog/2024/08/29/ethics.html #scifi #startrek #closereading

@prologic@twtxt.net My pod, which is running the same commit you are, does not return an error like that. It returns the same HTML it always has. Try it. I nuked my cache before restarting.

Edit: Oh wait, the plot thickens. I do get an error if I use curl or if I use a web browser that isn’t logged in. That’s good!

@prologic@twtxt.net I believe you are not seeing the problem I am describing.

Hit this URL in your web browser:

https://twtxt.net/external?nick=lovetocode999&uri=https://socialmphl.com/story19510368/doujin

That’s your pod. I assume you don’t have a user named lovetocode999 on your pod. Yet that URL returns HTTP status 200, and generates HTML, complete with a link to https://socialmphl.com/story19510368/doujin, which is not a twtxt feed (that’s where the twtxt.txt link goes if you click it). That link could be to anything, including porn, criminal stuff, etc, and it will appear to be coming from your twtxt.net domain.

What I am saying is that this is a bug. If there is no user lovetocode999 on the pod, hitting this URL should not return HTTP 200 status, and it should definitely not be generating valid HTML with links in it.

Edit: Oops, I misunderstood the purpose of this /external endpoint. Still, since the uri is not a yarn pod, let alone one with a user named lovetocode999 on it, I stand by the belief that URLs like this should be be generating valid HTML with links to unknown sites. Shouldn’t it be possible to construct a valid target URL from the nick and uri instead of using the pod’s /external endpoint?

@prologic@twtxt.net @bender@twtxt.net I partially agree with bender on this one I think. The way this person is abusing the /external endpoint on my pod seems to be to generate legitimate-looking HTML content for external sites, using a username that does not exist on my pod. One “semantically correct” thing to do would be to error out if that username does not exist on the pod. It’s not unlike having a mail server configured as an open relay at this point.

It would also be very helpful to give the pod administrator control over what’s being fetched this way. I don’t want people using my pod to redirect porn sites or whatever. If I could have something as simple as the ability to blacklist URLs that’d already help.

On my blog: Developer Diary, Women’s Equality Day https://john.colagioia.net/blog/2024/08/26/womens-equality.html #programming #project #devjournal

There is a bug in yarnd that’s been around for awhile and is still present in the current version I’m running that lets a person hit a constructed URL like

YOUR_POD/external?nick=lovetocode999&uri=https://socialmphl.com/story19510368/doujin

and see a legitimate-looking page on YOUR_POD, with an HTTP code 200 (success). From that fake page you can even follow an external feed. Try it yourself, replacing “YOUR_POD” with the URL of any yarnd pod you know. Try following the feed.

I think URLs like this should return errors. They should not render HTML, nor produce legitimate-looking pages. This mechanism is ripe for DDoS attacks. My pod gets roughly 70,000 hits per day to URLs like this. Many are porn or other types of content I do not want. At this point, if it’s not fixed soon I am going to have to shut down my pod. @prologic@twtxt.net please have a look.

On my blog: Free Culture Book Club — Morrisa Jeanine https://john.colagioia.net/blog/2024/08/24/morrisa-jeanine.html #freeculture #bookclub

https://galusik.fr/log/2024-08-23-frm.html Tonight #fridayrockmetal playlist

On my blog: Toots 🦣 from 08/19 to 08/23 https://john.colagioia.net/blog/2024/08/23/week.html #linkdump #socialmedia #quotes #week

On my blog: Real Life in Star Trek, Power Play https://john.colagioia.net/blog/2024/08/22/power-play.html #scifi #startrek #closereading

On my blog: Developer Diary, World Humanitarian Day https://john.colagioia.net/blog/2024/08/19/humanitarian.html #programming #project #devjournal

On my blog: Free Culture Book Club — Antumbra, chapter 0 https://john.colagioia.net/blog/2024/08/17/antumbra.html #freeculture #bookclub

On my blog: Toots 🦣 from 08/12 to 08/16 https://john.colagioia.net/blog/2024/08/16/week.html #linkdump #mastodon #socialmedia #week

On my blog: Real Life in Star Trek, Conundrum https://john.colagioia.net/blog/2024/08/15/conundrum.html #scifi #startrek #closereading

On my blog: Yet Another Dark Mode Post https://john.colagioia.net/blog/2024/08/14/dark-mode-again.html #programming #techtips

Morphotrophic by Greg Egan is built around an idea for how life on Earth could have worked out differently. It gets increasingly strange and interesting as the story progresses. My partner and I finished it last night and thoroughly enjoyed it. The beginning is free online: https://gregegan.net/MORPHOTROPHIC/00/MorphotrophicExcerpt.html #scifi #reading

On my blog: Developer Diary, World Elephant Day https://john.colagioia.net/blog/2024/08/12/elephant.html #programming #project #devjournal

On my blog: Open Source Characters https://john.colagioia.net/blog/2024/08/11/open-source-characters.html #freeculture #licenses #rant

On my blog: Free Culture Book Club — Viaje a la Tierra del Quebracho https://john.colagioia.net/blog/2024/08/10/quebracho.html #freeculture #bookclub

On my blog: Toots 🦣 from 08/05 to 08/09 https://john.colagioia.net/blog/2024/08/09/week.html #linkdump #mastodon #socialmedia #week

On my blog: Real Life in Star Trek, The Masterpiece Society https://john.colagioia.net/blog/2024/08/08/masterpiece-society.html #scifi #startrek #closereading

On my blog: Developer Diary, Coast Guard Day (belated) https://john.colagioia.net/blog/2024/08/05/coast-guard.html #programming #project #devjournal

On my blog: Free Culture Book Club — Aether Age Codex - Helios, part 3 https://john.colagioia.net/blog/2024/08/03/helios-3.html #freeculture #bookclub

On my blog: Toots 🦣 from 07/29 to 08/02 https://john.colagioia.net/blog/2024/08/02/week.html #linkdump #mastodon #socialmedia #week

On my blog: Real Life in Star Trek, Violations https://john.colagioia.net/blog/2024/08/01/violations.html #scifi #startrek #closereading

I learnt how to display a txt file in a html page in a pretty way: https://melyanna.ichi.city/twtxt.html