viperscape
viperscape on Hacker News
But that means waiting for the third party right?
Magic links are susceptible to man in middle attacks if your DNS is compromised, like on public WiFi, because the reset token is in the URI itself. So you're most vulnerable when you click the link.
I was just about to comment on magic and pokemon cards! Maybe even baseball packs. All could be traded for real cash, and obviously were! It's such a grey line though, the original intent of the cards is to not be traded around for cash, but be used to play games or simply collect (without the intent to sell) and be enjoyed.
To be frank, I'm glad the world is cracking down on the digital forms of this, I think it's a bit corrupt-- explicitly targeting minors with considerably less self-control. In my opinion, it's right up there with apps that use in-game currency gems/coins that you can purchase with real money; because kids targeted by that game audience often don't understand the repercussions on such activities. I think there needs to be a very fine line drawn where a child cannot make a digital purchase, even if inadvertent. Regardless. It shouldn't be a "we suggest you set up parental controls", literally the device should be locked down from entirely preventing such behavior and must then be overrode by an adult.
You didn't take a multivitamin? How did your body handle lack of vitamin c? or d?
Have you tried Botox? Might be a good way to test your theory
I don't understand in general why OLED is taking so long to be mass produced for TVs and monitors. It's like just now becoming mainstream, with what seems like two actually purchasable products.
The article mentions "cannabis abuse" a few times, what metric is there to put use into the abuse column?
"scheme web framework", except there are multiple scheme implementations and variants. I don't understand why the word scheme is even used, each scheme is basically a silo.
How does this differ or compete with platforms such as patreon? Also I signed up and it defaulted to Artist, I feel like major category type should be chosen during onboarding. Also, sign in with Google should be a thing I think.
I second this. Write a basic game with 2d graphics, use SDL, and save and load the state to file. To take it a step further and write a networked version with your own basic byte encoding if each move and game state to keep in sync. This would teach you a ton of various topics.
The last two bother me especially. Only thing I can think of is that bodies are expendable and for police that means good second skins, they get first or second dibs. No need for cyborg parts when blasters kick so much butt.
The stack backup reasoning is lame, "too expensive" is not really defining, and if a stack can be transferred to another stack, having two with one in a strongbox seems logical. You possibly lose memories then, but live on. It seems to come down mostly to money and socioeconomic disparity. At one point someone says, fixing a broken leg is too expensive. That's ridiculous
This is awesome, thanks for sharing !
A bit of a stretch, but you can use Electron (
https://electronjs.org/) which ties to nodejs, and use nodejs to call out to C.
Good point! I think you'd have to implement a lock of some sort, and check for it in application logic-- that way both can be updated simultaneously... not ideal!
> any possibility of ambiguity is effortlessly dealt with
"(+ 1)" is rather ambiguous and evaluates to 1, compared to "1 + ", which is very straight forward-- it's an incomplete expression and no evaluation can be done.
That sounds like expected behavior. Both users are incrementing a value of 100, which would be 101 in both cases. It's not atomic.
If User A incremented 100, and saved it down; then User B loaded this saved state and incremented 101, it'd be 102.
Having learned Rust and used it for nearly 2 years, I am now happy using C. I think most issues in C are easily catchable. Here me out:
1. If using Int for indexing or any sort of len or count, make sure it's positive when needed, and within bounds of what's allocated. As in if you plan on allocating huge data, plan it out and use the right data type.
2. If you alloc, then free when done. If you free, set to Null; and before you free, check for Null.
3. If you realloc, in particular, check that it actually worked and prepare for basic error handling.
Rust requires all of these steps by default.
Finally, just test some of your code. Rust makes this easy, and encourages it.
I still really like C.
Why is double free so commonly an issue? Isn't setting to Null after free and checking for Null before hand a common practice?
Not to do the c vs c++ thing, I too prefer c. For over 20 years actually I have preferred c to c++; all the while learning and enjoying other languages like rust. c still is missing some crucial stuff in my opinion-- there are times where I wish generics existed, and when you tie that to a trait system like in rust it's really a pity to not have something like that in c. Couple that with really great package managers for libraries in other languages, and a coherent way to use the libraries, makes one long for more when working in c; it's really missing great and easy code sharing that so many other languages have at their front and center.
Well depending on the surgery that might be advisable, it's an anti-inflammatory and heading off inflammation is usually beneficial.
Older resistance style touchscreen s would work well here, this is where the capacitance screens fail easily.
No purchase necessary! The title and the slogan on the site seem to infer something else. It's public domain source, it says at the bottom of the page. Glad to see more static generators, not sure how this is better or different than the other many
Also curious, would one ever do this in C? I understand the need in Rust and Zig, but in C is this usual?
What do you use for the mail server? Do you do any sort of backups or failover? Just curious
is it strictly in-mem? for instance if redis is restarted is there an option for unread streams to be saved with redis persistence