cabbageears
function modifyElements(pSel, cSel, rxStr) {
const regex = new RegExp(rxStr, 'i');
const pEls = document.querySelectorAll(pSel);
pEls.forEach(pEl => {
const fEl = pEl.querySelector(cSel);
if (fEl && regex.test(fEl.textContent)) {
pEl.style.display = 'none';
}
});
}
let rx = /(hi are u lonely|want (an )?ai gf?)/i;
modifyElements(".athing.comtr", ".comment", rx);
People can add onto the regex as needed, I guess. I haven't seen enough of the comments to be more specific since that seemed to get them. :-/ function modifyElements(pSel, cSel, rxStr) {
const regex = new RegExp(rxStr, 'i');
const pEls = document.querySelectorAll(pSel);
pEls.forEach(pEl => {
const fEl = pEl.querySelector(cSel);
if (fEl && regex.test(fEl.textContent)) {
pEl.style.display = 'none';
}
});
}
let rx = /(hi are u lonely|want (an )?ai gf?)/i;
modifyElements(".athing.comtr", ".comment", rx);The house does not have an advantage with poker. With player games, they earn money from hosting by taking vig(orish). But rapidly rising blinds in tournament poker is a way for them to get more games played, hence introducing turbos in tournament poker and Zone-type cash games.
Better understanding common betting patterns is more useful than hand simulators or whatever. Being able to accurately update your opponent's range throughout the hand is essentially how to play well.
"The reversed sequence of the numbers 473936482738338373926 is 629373833837284639374."
It works like this by using Python. Even when I told it to write a JS function internally to do it and only share the answer, it overruled that. When I asked it to repeat the sequence back in the same order, but starting from the last digit and working backwards, it failed a little bit. It seems like using the language model to pivot to the correct "model" or "logic" to decide to use code is impressive.