@falsifian@www.falsifian.org In my opinion it was a mistake that we defined the first url field in the feed to define the URL for hashing. It should have been the last encountered one. Then, assuming append-style feeds, you could override the old URL with a new one from a certain point on:

# url = https://example.com/alias/txtxt.txt
# url = https://example.com/initial/twtxt.txt
<message 1 uses the initial URL>
<message 2 uses the initial URL, too>
# url = https://example.com/new/twtxt.txt
<message 3 uses the new URL>
# url = https://example.com/brand-new/twtxt.txt
<message 4 uses the brand new URL>

In theory, the same could be done for prepend-style feeds. They do exist, I’ve come around them. The parser would just have to calculate the hashes afterwards and not immediately.

@prologic@twtxt.net Some criticisms and a possible alternative direction:

1. Key rotation. I’m not a security person, but my understanding is that it’s good to be able to give keys an expiry date and replace them with new ones periodically.

2. It makes maintaining a feed more complicated. Now instead of just needing to put a file on a web server (and scan the logs for user agents) I also need to do this. What brought me to twtxt was its radical simplicity.

Instead, maybe we should think about a way to allow old urls to be rotated out? Like, my metadata could somehow say that X used to be my primary URL, but going forward from date D onward my primary url is Y. (Or, if you really want to use public key cryptography, maybe something similar could be used for key rotation there.)

It’s nice that your scheme would add a way to verify the twts you download, but https is supposed to do that anyway. If you don’t trust https to do that (maybe you don’t like relying on root CAs?) then maybe your preferred solution should be reflected by your primary feed url. E.g. if you prefer the security offered by IPFS, then maybe an IPNS url would do the trick. The fact that feed locations are URLs gives some flexibility. (But then rotation is still an issue, if I understand ipns right.)

On the Subject of Feed Identities; I propose the following:

1. Generate a Private/Public ED25519 key pair
   
2. Use this key pair to sign your Twtxt feed
   
3. Use it as your feed’s identity in place of # url = as # key = ...
   

For example:

$ ssh-keygen -f prologic@twtxt.net
$ ssh-keygen -Y sign -n prologic@twtxt.net -f prologic@twtxt.net twtxt.txt

And your feed would looke like:

# nick        = prologic
# key         = SHA256:23OiSfuPC4zT0lVh1Y+XKh+KjP59brhZfxFHIYZkbZs
# sig         = twtxt.txt.sig
# prev        = j6bmlgq twtxt.txt/1
# avatar      = https://twtxt.net/user/prologic/avatar#gdoicerjkh3nynyxnxawwwkearr4qllkoevtwb3req4hojx5z43q
# description = "Problems are Solved by Method" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)

2024-06-14T18:22:17Z	(#nef6byq) @<bender https://twtxt.net/user/bender/twtxt.txt>  Hehe thanks! 😅 Still gotta sort out some other bugs, but that's tomorrows job 🤞
...

Twt Hash extension would change of course to use a feed’s ED25519 public key fingerprint.

Bluesky Adds 2 Million New Users After Brazil’s X Ban
In the days following Brazil’s shutdown of X, the decentralized social networking startup Bluesky added over 2 million new users, up from just half a million as of Friday. “This rapid growth led some users to encounter the occasional error that would state there were ‘Not Enough Resources’ to handle requests, as Bluesky engineers scrambled to keep the servers stable un … ⌘ Read more

trying to be alive, part 2: in the city of angels

@prologic@twtxt.net This does not seem to fix the problem for me, or I’ve done something wrong. I did the following:

1. Pull the latest version from git (I have commit 7ad848, same as on twtxt.net I believe).
   
2. make build and make install
   
3. Restart yarnd
   
4. Refresh cache in Poderator Settings
   

Yet I still see these bogus /external things on my pod when I hit URLs like the one I sent you recently. When I hit such a URL with curl I think it’s giving an error? But in a web browser, the (buggy) response is the same as it was before I updated.

So, this problem is not fixed for me.

@quark@ferengi.one We’re having a nice day out here, Clear sky, 26.2 °C (altough it feels like a ~30 °C) … no storms! And the most annoying thing is, THIS happens to my monitor whenever there is a power outage:

Image

With each one a row of pixels gets chipped out … and no I can’t afford a UPS at the moment.

POWER EFFIN’ OUTAGE!!! Electricity came back after ~10 min like… no beggie BUT, Internet stayed out for like 2 more hrs 😅

Base: 6.79 miles, 00:08:27 average pace, 00:57:20 duration
i was actually planning on running at a 11:00 or so pace, but felt so good i just kept increasing the pace each ¼ - ½ mile. in my own little world and ended it feeling great. hopefully i am not peaking too early again… just 12 more days until the PTC!
#running #treadmill

HTTP/2 differs from 1.x by becoming a binary protocol, it also multiplexes multiple channels over the same connection and has the ability to prefetch related content to the browser to lower the perceived latency.

HTTP/3 moves the binary protocol from HTTP/2 over to QUIC which is based on UDP instead of TCP. This makes it better suited to mobile or unstable networks where handling of transmission errors can be handled at a higher level.

Does anyone know what the differences between HTTP/1.1 HTTP/2 and HTTP/3 are? 🤔

Voici 2 illustrations de David Revoy @<@davidrevoy@framapiaf.org> qui risquent fort de me servir pour les expérience et les activités type tâche complexe dans mes cours de #physique-chimie. Merci! https://www.peppercarrot.com/fr/viewer/sketchbook__2022-10-31_Huge-Machine-to-Maintain_by-David-Revoy.html https://www.peppercarrot.com/fr/viewer/sketchbook__2022-10-31_Experimentations_by-David-Revoy.html

@prologic@twtxt.net the whole thing took less than 2 min 🤣

Pinellas County - Zone 2: 5.86 miles, 00:13:01 average pace, 01:16:16 duration
just some “training” in the humidity and such trying to keep it in the blue zone. frustrating! felt fine though.
#running

my memex db is 2.7GiB… which is a bit much

Modèle de distillateur solaire en forme de pyramide: https://www.universalis.fr/encyclopedie/eau-dessalement-de-l-eau-de-mer/2-la-distillation/

@stigatle@yarn.stigatle.no @prologic@twtxt.net testing 1 2 3 can either of you see this?

@prologic@twtxt.net There are a lot of logs being generated by yarnd, which is something I haven’t seen before too:

Jul 25 14:32:42 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:42 (162.211.155.2) "GET /twt/ubhq33a HTTP/1.1" 404 29 643.251µs
Jul 25 14:32:43 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:43 (162.211.155.2) "GET /twt/112073211746755451 HTTP/1.1" 400 12 505.333µs
Jul 25 14:32:44 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:44 (111.119.213.103) "GET /twt/whau6pa HTTP/1.1" 200 37360 35.173255ms
Jul 25 14:32:44 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:44 (162.211.155.2) "GET /twt/112343305123858004 HTTP/1.1" 400 12 455.069µs
Jul 25 14:32:44 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:44 (168.199.225.19) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Fwww.palapa.pl%2Fbaners.php%3Flink%3Dhttps%3A%2F%2Fwww.dwnewstoday.com HTTP/1.1" 200 36167 19.582077ms
Jul 25 14:32:44 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:44 (162.211.155.2) "GET /twt/112503061785024494 HTTP/1.1" 400 12 619.152µs
Jul 25 14:32:46 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:46 (162.211.155.2) "GET /twt/111863876118553837 HTTP/1.1" 400 12 817.678µs
Jul 25 14:32:46 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:46 (162.211.155.2) "GET /twt/112749994821704400 HTTP/1.1" 400 12 540.616µs
Jul 25 14:32:47 buc yarnd[1911318]: [yarnd] 2024/07/25 14:32:47 (103.204.109.150) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Fampurify.com%2Fbbs%2Fboard.php%3Fbo_table%3Dfree%26wr_id%3D113858 HTTP/1.1" 200 36187 15.95329ms

I’ve seen that nick=lovetocode999 a bunch.

There are also a bunch of log messages scrolling by. I’ve never seen this much activity in the log:

Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (149.71.56.69) "GET /external?nick=lovetocode999&uri=https://pagez.co.uk/services/your-own-100-fully-owned-online-vi>
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (162.211.155.2) "GET /twt/112135496802692324 HTTP/1.1" 400 12 826.65µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (51.222.253.14) "GET /conv/muttriq HTTP/1.1" 200 36881 20.448309ms
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/112730114943543514 HTTP/1.1" 400 12 663.493µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (27.75.213.253) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Falfarah.jo%2FHome%2FChangeCulture%3FlangCode%3Den>
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=error msg="http://bynet.com.br/log_envio.asp?cod=335&email=%21%2AEMAIL%2A%21&url=https%3A%2F%2Fwww.almanacar.c>
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/111674756400660911 HTTP/1.1" 400 12 545.106µs
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=warning msg="feed FetchFeedRequest: @<lovetocode999 http://alfarah.jo/Home/ChangeCulture?langCode=en&returnUrl>
Jul 25 01:37:41 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:41 (162.211.155.2) "GET /twt/112507964696096567 HTTP/1.1" 400 12 838.946µs

Something really weird is going on?

I deleted them all right before I sent my previous message, and already, a few minutes later, there are two more:

abucci@buc:~$ du -sh /tmp/yarnd-avatar-3*
1.8G    /tmp/yarnd-avatar-3122347915
2.4G    /tmp/yarnd-avatar-3533381443

What is this?

Avant d’oublier: des fiches persos pour #trouilleville à imprimer, 2 pages par feuilles. #jdr https://0x0.st/Xp4W.pdf

Pinellas County Running: 6.01 miles, 00:10:20 average pace, 01:02:05 duration
was feeling in the flow for the first 2.5 miles and then some lady stopped me in her car to help her get a turtle to the pond. could not get it back afterwards but it was still a fun time out albeit exhausting.
#running

Pinellas County - Cool down: 2.35 miles, 00:09:59 average pace, 00:23:27 duration
walked about ¾ mile and then started c/d run. felt strong so endurance is in a great spot!
#running

Pinellas County - Warm up: 2.41 miles, 00:09:08 average pace, 00:21:59 duration
included some strides and felt pretty strong
#running

Easy: 5.00 miles, 00:09:14 average pace, 00:46:11 duration
kept it in zone 2 pretty well
#running #treadmill

Indeed /post is referrer…

GET /post HTTP/2
Host: we.loveprivacy.club
[…]
HX-Request: true
HX-Target: content
HX-Current-URL: https://we.loveprivacy.club/conv/vcpt7gq
Referer: https://we.loveprivacy.club/post

1.2 Kilofives
⌘ Read more

Perso, je me suis arrêté à 2! Je ne regrette vraiment pas @im-in.space@im-in.space

@prologic@twtxt.net 1. allow only members of your pod to submit feeds

1. some kind of captcha (eew)
   
2. probationary status after submittal which requires review of some sort
   
3. rate limiting to slow down submissions from the same source

En attendant de stabiliser pizero, son panneau et sa batterie, le site est synchronisé sur 2 machines 3r1c.net (rpi4 sur alimentation standard) et solaire.3r1c.net (sur pizero et pijuice).

Le pi zero 2 est maintenant alimenté par un panneau solaire et son pijuice :-) Il héberge le site web.

@prologic@twtxt.net

1. The “Story of my life” (the less serious answer)
   
2. Being “The Black Sheep” from the old tale ? (the serious answer)

Nouvel article avec au menu du #retrogaming, des #citations et du bazar https://si3t.ch/log/2024-05-06-vagues-2.txt

Whoo! 🥳 I won 2 of my 3 singles tonight! 🏓

@bender@twtxt.net TBH It was quite late (where I am) when I wrote that twt, way past 2 AM … 😅
But there wasn’t much activity during the day either. It got me wondering if there was something wrong with my cron task for fetching your feeds.

Maybe it’s just the weekends. + there isn’t much bloat content around this space as on the usual platforms anyway.

Hah 🤣 @dfaria@twtxt.net Your @dfaria.eu@dfaria.eu feed really does consume about >50% of a “Discover” search with filters “Without replies” and “Hide my posts”. 🤣

Image

Pinellas County Running: 2.01 miles, 00:08:06 average pace, 00:16:18 duration
started running again… pretty much said fuck it and tested what would happen with a little speed. no pain. not even afterwards. i don’t know.
#running

Voidlinux : mes retours sont très positifs. 3 points : 1 - les paquets sont rapidement publiés, la vuln du paquet xz a donc été rapidement installée. 2 - Suite install de openssl en v3-3, authent 802.1x HS avec wpa_suppliant. J’ai dû rollback. 3 - Sur laptop HS mon écran scintille parfois quand la souris passe vers le bas de l’écran, étrange.

Pinellas County - Recovery: 3.13 miles, 00:10:05 average pace, 00:31:35 duration
easy run to blow off steam and test out the leg and hip. after the squats and lunges today my body was happy with a 10:00 pace. had some discomfort in the left hip at around 2.60 miles but it quickly went away. overall it was a pleasant run in the evening.
#running

sloweb partie 2 : les flux. https://si3t.ch/log/2024-03-14-sloweb-part-2-feeds.txt

Heureusement que j’ai 2 épisodes de la bonne auberge en stock pour me motiver à me lever et aller au boulot demain. #jdr https://labonneauberge.fandom.com/fr/wiki/Wiki_La_Bonne_Auberge

J’ai compté, il faudrait un peu plus de 2 semaines pour envoyer tout le livre 2 de dune au rythme d’1 SMS toutes les 5 5 minutes 👼

Easy: 2.34 miles, 00:09:32 average pace, 00:22:18 duration
quick and easy run. cut short by work meeting.
#running #treadmill

Tant mieux pour vous 2 alors :). Je reste déçu, surtout après le premier volet vraiment excellent, intelligent et fidèle au livre. Là, on surnage, il manque ce qui pour moi est essentiel. <@https://im-in.space/@solene@bsd.network/112020839027331041>

Fallait que ça sorte : Dune partie 2, le garçon pas content qui voulait se venger. https://si3t.ch/log/2024-03-01-dune-partie-2.txt #dune

Easy: 3.00 miles, 00:10:01 average pace, 00:30:02 duration
just an easy run after a few days resting the knee. had a few pings the first half mile and then it went away until about 2.75 miles in. called it soon after.
#running #treadmill

I finally found the NASM assembler.

https://nasm.us/index.php

I had heard that name before, many times, but somehow never looked into it. Weird. 🤨🤔

This is the kind of program I was looking for.

1. It is free software. Especially in the DOS ecosystem, free/libre software is a very scarce resource.
   
2. It’s a small command line program, not a huge behemoth.
   
3. Documentation appears to be well written.
   
4. It can even cross-compile DOS binaries from Linux.

Pinellas County - Tempo: 5.00 miles, 00:08:27 average pace, 00:42:16 duration
looks like my HR did it again… at about 2 miles in it went from 137 to 150. something must be wrong which sucks because now i cannot trust it. the run was pretty good and definitely felt like a tempo.
#running

Pinellas County - Long Run (part II): 2.65 miles, 00:10:47 average pace, 00:28:35 duration
continued the death march to cool down but was very hard to breathe. felt tight chest similar to hyper tension
#running

Pinellas County - Easy: 5.05 miles, 00:09:08 average pace, 00:46:08 duration
everything clicked today. kept a steady but mildly progressive pace whilst keeping the heart rate in zone 2 for the most part. nothing felt strained and breathing was easy. this one was a great boost in confidence seeing the progress made in the training and very happy with it.
#running