Hey @apex :) If you're reading this: In your twtxt feed, make sure to put a literal tab (0x09) between the timestamp and the text. You're currently using a space (0x20) -- some parsers trip on that.

(#xf5vlxq) @apex Yeah, that whole “keep an eye on the logfiles” thingy doesn’t really work with gemini (or gopher). There are ideas to fix that. Maybe I should formalize them and create a PR. 🤔

(#szpq4ca) btw, ping @ @benk @jdtron @apex and other Gemini folk. You probably know Gemini a lot better than I do, so feel free to chime in! :)

(#75uxnxq) @apex None that I'm aware of sorry 😢

(#75uxnxq) @apex Well hopefully you've also discovered Yarn.social and the many pods that now exists with great folks like @david 🤗 -- It is my hope/plan that `yarnd` (_the software behind each Yarn.social pod_) will eventually grow a biltin registry -- Bt for now the "discovery" is working pretty well really. Besides a registry (_which I believe @gbmor is working on a rewrite of gettwtxt_) we also utilise WebMentions too if you're interested in implementing that? 🤔

(#jhncnpq) @apex So we solve this in Yarn.social pods by peering with neighbouring pods and injecting Twts by hash which we can retrieve by simple JSON endpoints. This means we can avoid the need to "soft-follow" or "follow" the world just to get a complete "thread". In case this works quite well. -- Technically any client can peer with a Yarn.social pod too actually -- Might be worthwhile documenting the protocol, it's quite simple really.

(#75uxnxq) @apex Once @gbmor gets his getwtxt rewritten into a reuse-able library I can import, I'll add a builtin registry to all Yarn.social pods -- For now you are welcome to (_and others do_ hit _any_ pod anonymous and discover others for yourself 🤗 -- I've sort of lost count (_its hard to measure in a decentralised system_) but there are hundreds of new folks to discover 😂 If the number on search.twtxt.net, there are over ~400 active feeds ot there 😅

(#jhncnpq) @apex Sorry, what's what called? The WebMention handlers or the Peering code that handles injection of Twts amongst peers to "fill in missing" gaps without requiring users to "follow the world"? 🤔

(#jhncnpq) @apex It is mostly all in `internal/cache.go` if you're looking at the source tree already. The "magic"™ all happens here: => [Cache.Converage()]() It's called internally "Cache Convergence". Every time we fetch feeds, we converge the globally shared cache (_shared amongst users of a pod_) with other peers for things like "missing roots" and (TBD) "missing side of a conversation"

(#z4vwpjq) @apex that sounds interesting. Is you client offline first?