I'm not sure I understand your comment, mind elaborating on the details?
froztbyte
it’s the holidays, it’s okay: you don’t have to go near the c++ right now
I haven't really got enough information about that side of it, the details I have to go on are mostly about things particularly around the values CCC has tried to hold/build (and even there I am absolutely not intimately familiar, for reasons of distance and exposure and such)
yep, have made the same critique. the way people "overcommit" on this is a fascinating interplay of sunk cost fallacy combined with some other shit
why they even are there
(from observation over some years) congress orga more than occasionally fucks up on paradox of tolerance by letting shit like this through
it's been a thing I've noticed and have wanted to actually discuss with some folks, but never really gotten to yet on account of life stuff
there were also the much, much less grey-area instances a couple of years back where they were far too open to a number of abusers (this was around the time the appelbaum shit hit wide daylight), so there is a possibility that the issue runs deeper (in a structural sense, at best; personal sense, at worst) too but I possess insufficient information to know one way or the other what exactly may constitute the problem here
full service plagiarism! bet you we'll see whiteglove variant of it next
I was trying to remember at which point I unfollowed him, and I think it was exactly this nonsense
tangentially: I've been getting reminded of a bunch of services existing, by way of pointless "your year in review" bullshit
fuck spotify for starting that misfeature, and fuck everyone else for falling over themselves to get On Trend
let me spell it out for you: don't be such an ass.
a swing with a double miss
I've seen what effort goes into it at somewhere else, it's a lot
not sure I'd say it's unprofitable though, given just how goddamn much money google does make from its advertising monopoly. but I get what you meant with the conversion angle nonetheless
what are you basing that prefix length decision off? whois/NIC allocation data?
is the decision loop running locally to any given f2b instance, or do you aggregate for processing then distribute blocklist?
either way, seems like an interesting approach for catching the type of shit that likes to snowshoe from random cloud providers while lying in agent signature