Blackle Morisanchetto

I think the unfortunate state of things is if we don't format things like "2.7.2 (compatible; ourversion)," then the "version" field is practically useless for the clients, since otherwise there...

that sounds good to me! I'll try doing this tomorrow (saturday EST)

you can close it. I ran out of brain juice and can't work on it rn >.

I reproduced this today and used delve to figure out what's going on. I found a *ton* of goroutines that are all stuck trying to lock mutexes in the KVStore....

[goroutines_after_timeline_lockup.txt](https://github.com/superseriousbusiness/gotosocial/files/9906808/goroutines_after_timeline_lockup.txt) here's a stack trace (generated with ctrl+\\) after the timeline had been locked up for ~38 minutes. might be useful when someone looks at it. I'm trying to parse...

still reproducing this with that latest PR. here's a dump of the goroutines after it had been locked up for about 15 mins [goroutines_after_timeline_lockup_2.txt](https://github.com/superseriousbusiness/gotosocial/files/9935568/goroutines_after_timeline_lockup_2.txt)

For some reason "reset all runtimes" wasn't an option for me, but "restart runtime" worked just the same

looks pretty good! I can't remember the issue I fixed, but I did add a test case for it. If all the tests are still passing, then I'm good with...

One idea, which would require adding extra model parameters and doing some training: Because llama (and other transformer language models) are residual networks, i.e. each block *adds* to the output...

I agree this would be useful. I don't have the time to implement this but if you want to I would accept a PR, as long as it doesn't break...