stefs
Joined 16 years ago
Joined 16 years ago
i.e. MyTemplate.tpl.html
{if $foo}hello world, {$myname}!{else}goodbye, world.{/if}
which creates a kotlin class that can be used like this: MyTemplate(
foo = true,
myname = "bar"
).toString()
the biggest upside for me is that this way there's full, free IDE support, i don't need to write extra view models if the mapping isn't 1:1 and performance is pretty good because in the end there's no runtime parsing/compiling/interpreting except for the baseline JDK stuff (though there are even faster engines).https://codeberg.org/h34tnet/tempolin
warning: so far i'm the only user though, so don't use it in production. also, i'm working on some improvements right now which haven't been pushed yet.
1. either their actions are ignored by the victim states, which makes this very cheap and effective sabotage to weaken EU members.
2. or alternatively, if there's military retaliation, putin can finally do the mobilization he promised not to do for his war on ukraine, because he can now assert that the country is under attack by foreign nations.
the EU / the member states are now in a pickle: they know it's russia but can't say it out loud because then they'd have to take action. they also can't do nothing because then russian sabotage could wreak havoc with the population and economy. so what can they do?
1. military support of ukraine 2. further sanctions of the russian economy, which includes getting rid of dependencies on russian goods 3. re-arming and modernizing their own military (i.e. introducing modern drone warfare capability, launching their own satelite intelligence, ...) 4. start opposing/controlling russian influence by local malicious actors, i.e. russia friendly right wing political parties (which is somewhat complicated but not impossible in a democratic setting)
boldly improved: https://share.gemini.google/cR72HXmY4UdH
initially https://share.gemini.google/eJ54qDXM1gzC
boldly and maximally improved tone, clarity and flow: https://share.gemini.google/RiqX4x6mLB82
But i think one of the prediction markets more important uses is to enable insider trading for the current administration.
google became the most popular search engine exactly because those SEO keyword spam lists didn't work anymore and, after a while, they vanished. blogs, on the other hand, worked exceptionally well, because they used to link to other blogs' entries a lot, and blogs also used to be (comparably) high quality content.
so the main SEO guideline for getting a good page rank used to be: have a blog/news and publish lots of high quality content that bloggers link to.
in my opinion there's no _fundamental_ reason between an AI agent and a human adversary attacking your code, just a practical difference. in the long run the only way is to fix the bugs.
but i agree with you that in practice, it's also a question of cost effectiveness. booby-trapping your code is probably making attacks cost prohibitive for almost everyone (which is the same situation as before, when attackers had to employ security researchers/hackers or buy zero-days from 3rd party providers).
running SOTA models is expensive, so the attackers aren't going to do drive-by attacks. next generation cheap models might do the same, but they can also be used by the defenders.