(11-10-2020, 08:36 AM)vain Wrote: I have ignored twtxt in the past, but now I'm hooked.

As for twtxt.net, I think it's a great initiative. I won't use it myself because I always prefer self-hosting, but lowering the bar for non-tech people is a good thing in my book.

(Just make sure to retain full compatibility with self-hosted twtxt files, now and in the future. At the moment, this works fine. If, at some point, it became kind of mandatory to use twtxt.net, because important features $a, $b, and $c don't really work with self-hosting, then you'll probably be facing the wrath of some angry nerds. :-))

Hello! 👋 (again!)

Couple of things:

- We fully intend to keep to the original `twtxt.txt` spec.
- We have however extended it slightly (we plan to document this)
- The goal is to always remain compatible. We're pretty much feature-complete at this stage.

In terms of your comment on self-hosting; actually twtxt.net is just one of a few pods today, and the idea is to self-host it! There is for example https://twt.u53.us/ that someone that goes by @etux spun up :)

https://twtxt.net/ just happens to be my pod, the first one (inoggral if you will). There is also a hosting service we provide (again for convenience of non-tech folks).

Ultimately I feel like we would be very successful if two things were to happen:

- A sufficient number of ordinary folks paid for a hosted pod. We intend t make this as inexpensive as possible. e.g: $1.99/month -- This helps us continue development, maintenance, etc
- An equal no. (or more) pods from folks like @etux and maybe you? :D

I've blogged about the why's and how's of our project at https://twtxt.net/blogs/prologic which you're welcome to have a read of! You're even welcome to comment on them (just include the hash in your Twt's subject if you do so from your own client since I follow you!)