Will Hunt
Will Hunt
It's a bit confusing. I tend to call them User Timelines (Streams internally, but that's possibly more confusing) and then you have regular timelines. Either way, will fix.
>about the fact of getting the parameter from the db for every tweet This is fine. You are unlikely to exceed any disk IO barriers, plus I believe sqlite caches...
I've made it so that profiles are waited on before we send tweets. Obviously this will slow things down a bit, but it will stop the rather rubbish looking user...
Yup, need to repackage the latest for nuget.
Ah...it used to be ``contains()`` didn't it. I think I might have jumped the gun with ``includes`` which is fairly modern. I'll see what I can do to make both...
f300cc446ae0f375c37a110a077d86f3c32d3993 updates the type definition file to something actually recent in the hopes it will include the right stuff.
Yes sure! I will probably switch to a better logger (probs `Serilog`). I'm going to be a little busy for a while yet, so if you want to go ahead...
Yeah, it was missing some stuff, commited those.
- Read account_data (or a subset of) - Write account_data (or a subset of)
Okay, then I think we probably need a way to raise the non-ready state so the tile isn't presented as ready until we have our URL.