796 karma · joined December 13, 2020
[ my public key: https://keybase.io/mvolfik; my proof: https://keybase.io/mvolfik/sigs/VJT0Utkifb_Y2h3hM7OYj50eT4rBTTmCAGhVg_1q7uw ]
Also, it's not in my "preferred videos", they are paid ads, and they appear to many people, maybe it wasn't so clear from my comment
I have to disagree. Czech Youtube is currently full of scam ads with photos (and sometimes even bad deepfakes) of Czech president and other public figures, supposedly endorsing some investment product that yields you like 50% profit. I keep reporting these, and I know some people who do too, but ~80% of those reports get handled as "we determined no violation of our rules".
build.rs absolutely is a glaring security hole in the sense you say, but compared to that, this is much worse. You can verify the build.rs code that you download (at least in theory, and some people in banks or distro packages probably actually do), but binaries are orders of magnitude more difficult to inspect, and with the current Rust build system pretty much irreproducible.
- it historically appeared in autotranslated game chats in Arena of Valor game https://www.reddit.com/r/arenaofvalor/comments/btykru/commen... - mention on GitHub repo of a translation model https://github.com/Helsinki-NLP/Opus-MT/issues/62
I'm curious to see if anyone else has interesting encounters with this
But I'm not really satisfied with the sending side of things - my plan doesn't include the feature, and sending via Gmail is enough most of the time, but setting up each alias manually in Gmail is quite annoying.
To add an example of my own:
fn do_the_meow(meower: Meower)
seems like you want to take (consume, own) an object implementing Meower, which is correctly explained not possible like this. A suggested solution, fn do_the_meow(meower: &dyn Meower)
is very different - it is now correct with regards to a trait access, however, now you're just taking a reference. Correct replacement would be Box<dyn Meower>. And the final solutions, fn do_the_meow<M: Meower>(meower: M)
fn do_the_meow(meower: &impl Meower)
the first one is correct and equivalent to the original intent - it takes (owns) the value. However, the second variant (which is, again, as correctly stated, the best solution), is different again - it takes a reference (`&`) to `impl Meower`.Coming back to my point - it is important to separate the difference between the ampersand and the impl/dyn part. To suggest an improvement, one could first write all variants of this function taking a reference (`&Meower`, `&dyn Meower`, `&M` and `&impl Meower`), and later introduce the difference between where one can use sized/unsized types, and that Box<dyn Meower> is owned equivalent of &dyn Meower, and why one can't have owned `dyn Meower` just lying around.
Now let's pray they have other notifications than via email
My understanding of the term 'stablecoin' means that it is a crypto 'proxy' to some fiat currency, typically US dollar, just to avoid the actual conversion between crypto and fiat (because of taxes etc). So why isn't there just a DumbCoin(tm) that simply is 1-to-1 backed by the dollars? You give me a dollar, I mint you a coin. Somebody sends the coin back, I return them the dollar.
edit: oh, and there's new levels. there goes my afternoon...
What I also like about it is what a .Svelte file looks like. Since it's a compiler from the very beginning, it didn't need to start as .js and only than add .jsx for a little less verbosity. Svelte file is basically a HTML file with <style> and <script> tags. Variables from javascript can be referenced in HTML simply with {var}, and there are constructs for if/else, loops and few other special things. Easier to see than describe, go to https://svelte.dev/tutorial/