# nick = david # avatar = https://collantes.us/resources/david_collantes.png # description = “A lifetime Apple user. Partner says I am fastidious, sarcastic, and cynic. I just want to be me.” # url = https://raw.githubusercontent.com/Fastidious/fastidious.github.com/master/twtxt.txt # link = Notes https://netbros.com/ # link = Blog https://collantes.us/ 2026-07-05T15:23:08Z 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”! 2026-07-05T15:24:05Z (#7ooxzqo4e4pa) It looks like it worked. Now I need to get someone to follow me, to be fully sure. 2026-07-05T15:27:37Z (#7ooxzqo4e4pa) OK, pinging @ to see how long does this takes to go across. I will have to test Markdown at certain point, but baby steps! 2026-07-05T15:39:59Z (#bcoki3ldl7bb) This is a fork, coming from the [twtxt.app](https://twtxt.app) (yes, @ is going to be bankrupt on domain registrations, I know). Let’s see how forks fork! 2026-07-05T15:46:59Z (#opfyyfuds2lb) Hahaha! I thought the idea was to bend'em, no? 🤪 2026-07-05T15:55:47Z (#2z5saducasqc) This is pretty cool, @! 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! 2026-07-05T18:32:23Z (#tz62go5twlrz) Hmm, what broke this is puzzling my mind. 2026-07-05T18:33:23Z (#hky6mzvn4gpg) I see this thread just fine on twtxt.app. But @ didn’t, nor it shows fine on twtxt.net. Hmm 🤔. 2026-07-06T12:18:58Z Testing forks here again, to see at which point it breaks on TWTXT.net. 2026-07-06T12:19:48Z (#ucojr6a25xvv) This is the first reply to the OP. 2026-07-06T12:20:54Z (#nyhysiy2be56) This is the first fork (to the first reply). 2026-07-06T12:21:48Z (#32j6kliegicc) Forking the first fork. Is this possible? How? 2026-07-06T12:23:18Z (#o2vg2f4jolqs) I just hit “fork” on a previous fork. 2026-07-06T12:30:58Z (#o2vg2f4jolqs) Hmm, so, one fork of a fork is missing now. This one:
```
2026-07-06T12:23:18Z (#o2vg2f4jolqs) I just hit “fork” on a previous fork.
``` 2026-07-06T14:23:16Z (#jyp5m5z4gaq4) 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. 2026-07-06T14:26:54Z (#hw2vzrov4mdi) OK, I think I have now truly disabled Pages. Sending the reply, and looking at the repository to see if actions run. 2026-07-06T14:29:28Z (#hw2vzrov4mdi) 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. 🤔 2026-07-11T13:34:19Z (#uoypprbpvos2) 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, @. 2026-07-11T13:41:22Z (#5bpwpdcjnhcz) 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)