buckket

Seems related to the problem regarding `next_max_id`, maybe you could give #306 a try.

I’ve tested the fix successfully with fairly large profiles, getting more than 1000 Users returned. You can check for problems if you call Error() in and after your Next() for...

@kseistrup Had the exact same idea of including twtxt nick and URL in the user-agent string. I’ll open a new issue for this one! :+1:

Using DNS, and the NAPTR record in particular, to point to twtxt files seems like a really cool idea. :neckbeard: Maybe we can/should(?) include support for that even if not...

I really like the idea of signing ones twtxt feed. This would indeed allow for further identification besides the URL of the file itself, so that the URL becomes exchangeable...

Let’s have a look at twtxt’s dependencies: - [x] https://packages.debian.org/source/stretch/python-click - [x] https://packages.debian.org/source/stretch/python-aiohttp - [x] https://packages.debian.org/source/stretch/python-dateutil - [x] https://packages.debian.org/source/stretch/python-humanize Seems like we have everything we need to mitigate all those...

@mdom Do you still know which line caused the error? Trying to reproduce this so I can catch the exception which leads to this.

I’m not able to reproduce this with 1.3.0dev.

Very strange, I get this: `twtxt.parser DEBUG https://kdave.github.io/twtxt-test.txt - Unknown string format` But no exception, twtxt continues processing the other sources and tweets, as intended. Can you provide the `--verbose`...

Okay, using the same version with the exact same arguments I get: ``` $ twtxt -v view https://kdave.github.io/twtxt-test.txt 2016-04-06 15:28:35,265 twtxt.cli DEBUG Not following https://kdave.github.io/twtxt-test.txt, trying as URL 2016-04-06 15:28:35,290...