agwa

39 ms·

481.
by agwa 6y ago
DigitalOcean isn't intentionally damaging the open source community - they are just indifferent to the harm they're causing. They are fully aware of the spam problem and refuse to take measures to fix it because it would be too m
482.
by agwa 6y ago
Nah, they're only free for 12 months, not forever: https://aws.amazon.com/free/?all-free-tier.sort-by=item.addi...
483.
by agwa 6y ago
It's the same in many parts of the US, but unless the apartment comes with central AC, we're stuck with noisy and inefficient window AC units[1], or worse, portable AC units[2]. [1] https://www.mytrustedcontractor.com&#
484.
by agwa 6y ago
I've never seen an apartment building in the US with special pipes for running the refrigerant lines. It's just not feasible to install a mini split in the US if you're renting, but it appears Japan is totally set up for it.
485.
by agwa 6y ago
He must have changed his view because he ultimately allowed the feature. Does anyone know what changed his mind?
486.
by agwa 6y ago
To be clear, it will be incompatible with GPLv2- only software. Projects which use the default GPLv2 license notice will be able to link with OpenSSL 3 without problem, since the notice permits the software to be re-licensed under newer v
487.
by agwa 6y ago
> Also, because it relies on session tickets, there's a time window after which the ticket gets cycled and properly initialized. But that is apparently 6 hours by default so it is going to protect only really long-lasting TLS sessio
488.
by agwa 6y ago
It should be possible for the Raspberry Pi to emulate a USB flash drive using the OTG connection, though I'm not sure if it can emulate a keyboard and a mass storage device at the same time. It would be a very valuable feature for sur
489.
by agwa 6y ago
Yes, a good API with good documentation is important. Fortunately, OpenSSL has improved significantly in the last few years. Unfortunately, I've talked with crypto experts about GnuTLS's bizarre session ticket key rotation system
490.
by agwa 6y ago
The bug report downplays the severity of the problem. This comment comes the closest to explaining the severity: > ticket encryption key and decryption key are all-zero [...] in TLS 1.2, it may allow attackers to recover the previous co
491.
by agwa 6y ago
> And just because a key is public, doesn't mean that it is going to be automatically sent to a third-party. In practice, it pretty much does - bad actors continuously scrape the GitHub firehose looking for AWS secrets, and then aut
492.
by agwa 7y ago
This is a good reason to use a technique like cperciva's payment iframe: https://www.paymentiframe.com/ It lets you use stripe.js (thus getting the PCI compliance benefits) without Stripe being able to spy on your visi
493.
by agwa 7y ago
Keep in mind the vulnerability was in a 5 year old version of the protocol and has since been fixed, so the description of the protocol won't match what you're familiar with. > In the attack by Eve, it is claimed that Eve recov
494.
by agwa 7y ago
Maybe. But why would you try that when you can just not use signatures, which were the wrong tool in the first place? My point is that you usually need less crypto , not more. Trying to fix fundamental problems by tacking on more crypto
495.
by agwa 7y ago
This is a pretty pedantic point and the inaccuracy doesn't detract from the rest of the post, though I will mention this to the author as accuracy is important. The accurate thing to say is that the attack was found 6 weeks before Let&
496.
by agwa 7y ago
This is a good example of what can go wrong when you try to use too much cryptography. When designing a protocol/application, you should first try to do it without crypto, then with hashes/symmetric crypto, and only as a last res
497.
by agwa 7y ago
Looks way better with the new text color. Thanks!
498.
by agwa 7y ago
I really want to check this out, but my eyes hurt reading the page because the contrast of gray on black is so low. A vision-impaired person might not be able to read it at all. Please consider using this tool to pick a text color that pr
499.
by agwa 7y ago
They absolutely can. Just one example of how ICAAN regulation helps: ICAAN requires that the .org registry let domain owners lock in their current price for 10 years if a price increase is announced, and prohibits different renewal prices
500.
by agwa 7y ago
Michael published an interesting post about his attempt to talk with owners of sheet metal shops: https://mtlynch.io/retrospectives/2020/01/#sheet-metal-resea...
501.
by agwa 7y ago
Yeah, ccTLDs are often poorly run and domain names can be seized for arbitrary political reasons. In contrast, gTLDs are regulated by ICANN and are required to uphold technical and policy standards.
502.
by agwa 7y ago
Zestful uses machine learning, so there could be a fair amount of storage, CPU, and memory requirements that make using a hosted API preferable to a local library. Also, if you read Michael's posts on https://whatgotdone.co
503.
The latest version of Slack has a setting to disable the WYSIWYG editor(twitter.com)
783 points by agwa 7y ago|221 comments
504.
by agwa 7y ago
In the case of .org, non-uniform renewal pricing is only allowed if "the applicable registrant expressly agreed in its registration agreement with registrar to higher Renewal Pricing at the time of the initial registration of the domai
505.
by agwa 7y ago
> Take a page from the Donuts book: create multiple price tiers for popular domains, up to 100x the base rate. > Raise rates for long-time owners of common words. They weren’t using that premium space anyway. This is forbidden by th
506.
by agwa 7y ago
> I've always wondered why so many people are using .io domains (and now .ai domains). Most people do not know the difference between gTLD and ccTLDs. They think .io and .ai are just like .com. Registrars like Namecheap ought to d
507.
by agwa 7y ago
It's about more than just legal jurisdiction. gTLDs are required by ICANN to adhere to certain standards whereas ccTLDs are not. As a result, the majority of ccTLDs are incompetently and/or capriciously operated.
508.
by agwa 7y ago
If a registrar did that, the .org domain owner would change to a better registrar, and they'd be able to keep their .org domain. There's competition among registrars, unlike registries.
509.
by agwa 7y ago
If their registrar did that, Wikipedia would change registrars to one that didn't - and they'd be able to keep their .org. There's competition among registrars, unlike registries.
510.
by agwa 7y ago
In practice, this says the same thing. There's no reason for registrars not to let their customers lock in the low price for 10 years. There's stiff competition among registrars and their margins on domain name sales are razor t

More ›