The thing is you don't know that it's got actual future usefulness. You might think or hypothesize that it does, but for various reasons it may turn out to be a dead-end.
Almost every endeavour has non-zero potential future utility - even as a counterexample or lesson to learn from. I think that definition of "useful" is probably too broad to make an argument against, and so not a useful definition.
Deep, paradigm-shifting research often needs decades of deep thought and experimentation, which will not yield weekly, monthly or even annual demonstrations of usefulness to customers or shareholders.
She writes as a VC (I think?) where her job is to allocate capital for shorter-term "useful" (read: profitable) outcomes.
Huh? The bot can communicate with me freely as it sees fit. A "conversation" in telegram parlance is not time-limited, it's ongoing once established, so no it's not only inbound. It can awaken and ping me whenever it wants. This can also work if it's added to a group chat.
If you mean it's not outbound as in it can't message arbitrary random users out of nowhere, well yeah, and that's a very desirable trait.
Once a conversation with a user is established, telegram bots can bleep away at you. Mine pings me whenever it puts a PR up, and when it's done responding to code reviews etc.
There's generally no grey market for XSS vulns. The people buying operationalized exploits generally want things that they can aim very specifically to achieve an outcome against a particular target, without that target knowing about it, and operationalized XSS vulns seldom have that nature.
Your other potential buyers are malware distributors and scammers, who usually want a vuln that has some staying power (e.g. years of exploitability). This one is pretty clearly time-limited once it becomes apparent.
I've seen code persist a long time because it is unmaintainable gloop that takes forever to understand and nobody is brave enough to rebuild it.
So no, I don't think persistence-through-time is a good metric. Probably better to look at cyclomatic complexity, and maybe for a given code path or module or class hierarchy, how many calls it makes within itself vs to things outside the hierarchy - some measure of how many files you need to jump between to understand it
Not really - that 1GB is the seed for a procedural generation mechanism that has been finely tuned to its unfolding in an environment over 4 billion years.
A bunch of us in the rest of the world are making great strides in reducing our greenhouse gas emissions without it tanking our economies. Australia is, per-capita, one of the worst offenders and we're on track to reach net zero by 2050.
I think your position is based on very cynical premises. There is no reason to assume with high confidence that humans will obliterate each other in that next 50 years (especially if we do something about one of the major stressors causing conflict)
There is also no reason to believe that reducing greenhouse gas emissions over 15-20 years will cause "more" damage than the worst impacts of climate change? Can you cite sources on this claim?
It is still possible to mitigate the worst effects of anthropogenic climate change.
I would love mailing lists to be a thing again, but the experience of using email is just so bad for me. The sheer amount of unsubscribing I have to do to make it usable - not even taking spam into account - makes email a place I don't want to spend any time.
Sydney, Australia.