(#22dnnkq) @email@example.com Harder to refactor on an existing project. So I will refactor here, with the goal you assigned to me, (copying a lot of code of original yarnc), once it will be over, we can try to merge on your yarnc or keep it separate, it will be up to you.
(#7wdfdva) @firstname.lastname@example.org I saw that in France with the family protest “Manif pour tous”, and more recently in Canada with the Trucker convoy. Basically you are free to express yourself as long as you go along the president willing.
(#pwprzqq) I see that you Nuke everything on February 16th, since then I don’t see any reference to quickstart on the code.
Are you rebuilding everything and the go install duriny.envs.sh/twtr@latest comes from a version before the Nuke ?
(#tuizh4q) Sorry I’m late, on the discussion, but as I see it. A big redis cluster will solve that issue (Twitter uses it) and a bit of js for the pagination client side. BUT the ability to be able to edit a post (impossible in twitter) makes it hard to have a big redis cluster.
The hardest part will mainly be for the client command line app.
Sorry @email@example.com to disturb you, but using types.MakeTwt(mainTwter, time.Now(), "Hello") for some unit tests, I found that panic("twt manager not configured"), I searched in the code without seeing where you use SetManager ??