It works great! (using user.github.io). So, my settings:

1. Token
2. Repo: username.github.io
3. twtxt.txt for feed file name
4. https://username.github.io/twtxt.txt for feed URL (to avoid the ugly, long raw one)

This is a reply using my test Github feed. Let’s see how it shows. I just realised it doesn’t have to be at user.github.io, it could be any repository. So, I will have to try that at some point as well, unless you can run that test, @prologic.

Hmm, it seems username.github.io cannot fully disable pages, so that will always be a delay from the time I hit reply, to when the reply will make it to the twtxt.txt file. 🤔

OK, I think I have now truly disabled Pages. Sending the reply, and looking at the repository to see if actions run.

So, when using GitHub one can’t simply send twtxts one after the other, especially if the default repository (username.github.io) has “pages” enabled, because they need time to build.

This is what I have done. I have disabled pages (because I was not using them anyway), and now I am going to further test to see.

Hmm, so, one fork of a fork is missing now. This one:

2026-07-06T12:23:18Z

I just hit “fork” on a previous fork.

Forking the first fork. Is this possible? How?

This is the first fork (to the first reply).

This is the first reply to the OP.

Testing forks here again, to see at which point it breaks on TWTXT.net.

I see this thread just fine on twtxt.app. But @movq didn’t, nor it shows fine on twtxt.net. Hmm 🤔.

Hmm, what broke this is puzzling my mind.

This is pretty cool, @prologic! I am using it on the desktop now, but will soon try mobile as well. Will test the “connecting” feature, see how it goes.

Not need to say, but this one on GitHub works great. I have to go edit the twtxt.txt file to add nick, url, avatar, and description, and I am sure I have given more permissions than needed to the token, but it works great!

Hahaha! I thought the idea was to bend'em, no? 🤪

This is a fork, coming from the twtxt.app (yes, @prologic is going to be bankrupt on domain registrations, I know). Let’s see how forks fork!

OK, pinging @bender to see how long does this takes to go across. I will have to test Markdown at certain point, but baby steps!

It looks like it worked. Now I need to get someone to follow me, to be fully sure.

OK, so this is on GitHub now. Let’s see how it goes. I am sure it isn’t setup with the right permissions (perhaps too permissive), but I can always fine tune.

Alright, let’s hit “Twt”!