well, that's another thing now fully working properly, and it makes a pretty big difference
the issue causing clients to not talk to it is still dangling but i'm not gonna worry about that, i think that a more usefully logging client would clear up the question real fast and i don't think such a thing exists, and if i write it, it will work with this which doesn't help
and since manly front end programmers don't do logs, i don't expect any quick answer to the question that won't involve me pivoting to front end dev for several months to figure it out
no, i'm gonna continue as i was, making #ratel even better, i now am up to changing up the signatures to binary, this probably is going to be a small change because it only affects validation and signing
also, i am more or less currently just working for my own dreams at this point...
this stuff with the git hosting is annoying but i'm pretty sure it's some git-side thing, doesn't make any sense, i fixed it mostly before, but it was the same repo that misbehaved again, or if not, then probably i will continue to have this problem and will have to switch over to working with the C based git http tooling
or i could fork gitea to have a run mode where it does not create a subfolder for users and namespaces can't collide
meh... just gonna continue the tweaks to max out the event encoding, and probably move on to the filter encoding so it is immediately turned into a form that rapidly forms the query indexes required
badger is faster than stink, and i have GC working already, it's just a marginally useful feature without the use of an L2, which i envision as a distributed blossom event store with a distributed search index
anyhow, i've got a VC hunter on the case and the more awesome i make this relay the better we can deliver a product, and i trust his high level vision, even if he does trawl some funding sources that are problematic
Showing page 1 of
1 pages
