Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
caffeinewriter
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
31.
▲
by
caffeinewriter
7y ago
I think you're quite correct. If you're investing in obfuscation, you're probably making the wrong investment. Malicious actors have to obfuscate to avoid detection for as long as possible, and benign actors would probably be
32.
▲
by
caffeinewriter
7y ago
While you might have access to the AST, obfuscated JS is still harder for humans to parse, and reverse engineer what the original function is doing. For example: var _0x11f8=['\x6c\x6f\x67'];(function(_0x417d16,_0x4a5f0f){va
33.
▲
by
caffeinewriter
7y ago
I appreciate all your transparency and engagement on this issue. It probably would have had the same outcome, yes, but potentially resolved much more quickly. Regardless, the fact that you're fixing it is music to my ears.
34.
▲
by
caffeinewriter
7y ago
I mean, yes and no. Every business exists to make profit, but most companies thrive when their customers are happy, not miserable. Many (but not all) microtransactions in gaming, particularly in the more predatory free-to-play models, don&#
35.
▲
by
caffeinewriter
7y ago
Good response from DO, but this line jumps out at me. > Responses to account locks were not prioritized differently from a ticket management standpoint to be above less severe tickets. That's arguably the biggest failure, IMO. The f
36.
▲
by
caffeinewriter
7y ago
This isn't a new problem. Cloaking[1] has been around for a long time. Google[2], and Facebook[3] have been fighting this problem for years. Even Google hasn't had perfect luck with fighting off cloakers[4]. [1]: https:/
37.
▲
by
caffeinewriter
7y ago
I'm https://takeoverthe.world/@caff :) Self-hosting Mastodon has been an adventure, for sure. However, relays have definitely helped with federation. :)
38.
▲
Captchas Suck (2017)
(axesslab.com)
2 points
by
caffeinewriter
8y ago
|
0 comments
39.
▲
by
caffeinewriter
8y ago
Basically, you have to go through the ICANN accreditation process, which is documented here: https://www.icann.org/resources/pages/accreditation-2012-02-... The cheaper, and easier way, if you're looking to s
40.
▲
by
caffeinewriter
8y ago
Here's an alternate mirror as well. [link removed] Edit: I'm removing my own copy, since I just realized I didn't set up a contact for that site, and I'd rather play it safe than sorry. Others have mirrored it, and one&#
41.
▲
by
caffeinewriter
8y ago
I feel like every language should have at least one "wat" style talk or article. Even for languages you adore, it's important to understand the quirks, shortcomings, and issues in a context that might seem absurd to an outsid
42.
▲
by
caffeinewriter
8y ago
I completely understand the decision to not stand their ground. Going up against Slack means going up against a multi-billion dollar company, and potentially all the legal firepower that entails. Even if every monetary cost were covered, th
43.
▲
by
caffeinewriter
8y ago
Arguably he shouldn't have had to, since the arbitration clause appeared in the Terms of Service after he made his pledge. I have my own opinions about arbitration but that's neither here nor there when what you agreed to did not
44.
▲
by
caffeinewriter
9y ago
I was just thinking about this. Instead of versioning with an `Accept` header, or with a URL version, why not version off of an upgradable API key?
45.
▲
by
caffeinewriter
10y ago
What? No. > The statute applies to "confidential communications" -- i.e., conversations in which one of the parties has an objectively reasonable expectation that no one is listening in or overhearing the conversation. See Flan
46.
▲
by
caffeinewriter
10y ago
I follow them as well :) Their work with containers, and their general commentary make for fascinating reading.
47.
▲
by
caffeinewriter
10y ago
There's Codenvy[0], whose beta is built upon Eclipse's new Che[1], which can also be self-hosted. [0]: https://codenvy.com/ [1]: http://www.eclipse.org/che/
48.
▲
by
caffeinewriter
10y ago
I've been meaning to read Kill Decision for quite some time. Daniel Suarez has some really unique perspectives using near-future fiction. Daemon and Freedom™ were fascinating glimpses into the potential of the future of modern day tech
49.
▲
by
caffeinewriter
10y ago
I'd love to see a blog post on some of the nitty-gritty details on this. Even if there's no known root cause, it'd be fascinating to see your analysis on this.
50.
▲
by
caffeinewriter
10y ago
Awesome! It wasn't readily apparent that delivery is handled by a third party before signing up. I've used Instacart before, so it's cool that it's just an integration, but I wasn't sure if it was an addon I was mis
51.
▲
by
caffeinewriter
10y ago
This is the first startup in a while I've been excited to spend money on. It looks great, and it looks like it already has a very mature feature set. The one thing I didn't see was the pricing on the delivery options. Is that live
52.
▲
by
caffeinewriter
10y ago
Submitted it to Hybrid Analysis, and this particular attachment appears to be benign, and is in fact an e-ticket for American Airlines. Doesn't seem to contain any embedded malware readily apparent in the analysis. https://w
53.
▲
by
caffeinewriter
10y ago
Or why not some enterprising job seeker? That'd be one thing to put on the resume. "Contributed fixes to thousands of Github repositories."
54.
▲
by
caffeinewriter
10y ago
Mostly off-topic, but if you haven't heard it before, you'd probably enjoy giving Criminal[0] a listen. [0]: http://thisiscriminal.com/
55.
▲
by
caffeinewriter
10y ago
Or even Min[0] which was on here a few months back. [0]: https://news.ycombinator.com/item?id=11484770
56.
▲
by
caffeinewriter
10y ago
Just because the bubble hasn't burst yet, doesn't mean we're not actually in a bubble. That line of reasoning irks me a bit, but still, it is laughable how the imminent bursting of the bubble has been predicted for nearly a d
57.
▲
Eternal September
(en.wikipedia.org)
2 points
by
caffeinewriter
10y ago
|
0 comments
58.
▲
by
caffeinewriter
10y ago
Perhaps Browserify would be something that would work in this use case. Awesome job! In addition, it might be cool to have in-line substitution of data. For example, in your analytics notebook[0], I noticed you referenced the number in text
59.
▲
by
caffeinewriter
10y ago
Yikes.
60.
▲
by
caffeinewriter
10y ago
I'm really hesitant to even consider this without it being run through the Diehard Tests[0], since from my understanding, "True Randomness" should be cryptographically secure should this be used in a CSPRNG. [0]: https:/
More ›