Yes it work: 2024-12-01T19:38:35Z twtxt/1.2.3 (+https://eapl.mx/twtxt.txt; @eapl) :D

The .log is just a simple append each request. The idea with the .cvs is to have it tally up how many request there have been from each client as a way to avoid having the log file grow too big. And that you can open the .cvs as a spreadsheet and have an easy overview and filtering options.

Access to those files are closed to the public.

Some more arguments for a local-based treading model over a content-based one:

1. The format: `or(@DATE)both makes sense: # as prefix is for a hashtag like we allredy got with the(#twthash)` and @ as prefix denotes that this is mention of a specific post in a feed, and not just the feed in general. Using either can make implementation easier, since most clients already got this kind of filtering.

2. Having something like `will also make mentions via [webmetions for twtxt](https://darch.dk/mentions-twtxt) easier to implement, since there is no need for looking up the#twthash`. This will also make it possible to make 3th part twt-mentions services.

3. Supporting twt/webmentions will also increase discoverability as a way to know about both replies and feed mentions from feeds that you don't follow.

I fixed it by adding (?<!\S) to the regex filter. But what is going on with the ?nick=dbucklin anyhow?

And now added #filter for replies too:

What about using the blockquote format with > ?

Snippet from someone else's post by: @eapl.me

Would it not also make sense to have the repost be a reply to the original post using the (<a href="?search=twthash" class="tag">#twthash</a>), and maybe using a tag like #repost so it eaier to filter them out?