11:25:04 <selsta> ErCiccione[m]: the @wallet and @daemon link don’t seem to work in the blog post
11:25:49 <ErCiccione[m]> Yeah sarang removed them with his patch which correct some mistakes
11:25:59 <ErCiccione[m]> We are waiting on binaryfate to deploy the new master
11:30:37 <ErCiccione[m]> *waiting for
11:30:43 <ErCiccione[m]> I need an english course
11:31:48 <selsta> btw I found out that the free version of grammarly.com is quite nice for checking blog posts
11:34:45 <selsta> (just don’t download any browser extension)
11:42:42 <ErCiccione[m]> Thanks, i'll check it out
16:58:39 <niocbrrrrrr> ErCiccione[m]: people use both waiting on and waiting for.  I guess waiting for is more correct.
16:58:42 <niocbrrrrrr> btw you English has noticeable improved and although you sometimes get confused with idioms your ability to clearly communicate ideas is excellent
17:23:08 <moneromooo> I'd say waiting on has a vague implication of a dependency. Waiting for is the more common everyday usage.
17:23:58 <sarang> Sure. You might wait on someone, but wait for the bus
17:24:35 <moneromooo> Yeah, I wouldn't say waiting on the bus, that feels wrong.
17:27:45 <niocbrrrrrr> disclaimer: english is my second and only language
17:27:49 <niocbrrrrrr> my sister still corrects me to this day
17:30:10 <moneromooo> lol
17:43:15 <ErCiccione[m]> niocbrrrrrr: Thank you really much for the info and for the compliment. I learned english by myself, so sometimes i completely mess up the structure of the sentence. I also make words up, but that's just me :P
17:46:03 <ErCiccione[m]> My initial work as translator for Monero is what teached me the most. Before Monero i couldn't even watch a movie in English (even with subtitle) or talk to an english speaker. Now i often read books in english and i have no problem reading technical papers. It's an achievement i'm quite proud of, even if english is not really an hard language to learn.
17:46:32 * ErCiccione[m] self high five and goes to hide
17:53:12 <ErCiccione[m]> luigi1111: btw you were right. Squashing and merging doesn't create a merge commit
17:53:51 <ErCiccione[m]> don't know how you want to deal with that. Should we ask people to always squash their commit or not having a merge commit is not a big deal?
17:54:35 <ErCiccione[m]> i can squash PRs for people like i used to do with translations some years ago (before weblate was a thing) if necessary
18:02:32 <luigi1111> probably just case by case. if really messy rebasing would be nice. not having a merge commit isn't the end of the world either. I know some people that contribute aren't familiar with git etc and the website doesn't need to push them away over that IMO
19:07:22 <ErCiccione[m]> I agree