(#djhawzq) > What is the difference between twtxt-php and timeline from sorenpeter? twtxt-php is a minimalistic client based on another PHP project, you can see it on timeline is a better-looking Web app, with support for markdown, images gallery... you can see it here twtxt-php is not actively developed, its core was merged into timeline > Does it have a way to follow feeds from the web ui? Yes, but you have to be logged in. Currently can only add URLs, not edit or unfollow. > I was looking at it and what prevents someone from downloading the .config file and getting the password? An .htaccess file > Also how would I generate a totp password to use? That part is missing on the Web side, there is a commented PHP code to do that Although you can find a better TOTP onboarding on

(#djhawzq) > [...] my server logs it shows that your site pulled in the useragent as with bytesypider from bytedance? Didn't know of bytesypider and bytedance, I assume those are bots, although I no idea why they are pointing to that address to your site twtxt-php isn't sending User-Agent headers as it's in the original spec: Or the discussion there: I think it could be easy to implement 🤔 Since relying on HTTP logs could be inconvenient on some servers, there were ideas of using WebMention or some HTTP endpoint to inform who's following your URL (like on Gemini Antenna). From what I've read, timeline and yarn has experimental support for Webmention. Could @prologic or @darch share some insights on that?

(#djhawzq) @eaplme I could try and host timetime it does look nice. >That part is missing on the Web side, there is a commented PHP code to do that > That code would end up generating an totp secret that I could put into the config? > > Does it have a way to follow feeds from the web ui? > Yes, but you have to be logged in. Currently can only add URLs, not edit or unfollow. How would I edit or unfollow? That fit website would be nice to just genete a secret and put it into the .config and then using the totp code to login.

(#djhawzq) @eaplme > Didn't know of bytesypider and bytedance, I assume those are bots, although I no idea why they are pointing to that address to your site > You gave me a good idea to block bytespider. Its just weird what it pulls in. > twtxt-php isn't sending User-Agent headers as it's in the original spec: > sending user agent would be a nice thing to have so that people using regular twtxt clients can find you and anyone else hosting twtxt-php or timeline HTTP logs are annoying but webmention has an issue that it needs a server to check for webmentions. The server can be an external one or hosted on the same server as far as I can find. But also HTTP logs need a server that one can view the logs.