Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ronsor
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
25 ms
·
781.
▲
by
ronsor
1y ago
The clear solution is to not copy every aspect of the original and also release your port under a different name.
782.
▲
by
ronsor
1y ago
uBlock filters
783.
▲
by
ronsor
1y ago
Arguably a package manager shouldn't be so complex that it takes many developers years to implement.
784.
▲
by
ronsor
1y ago
> wonder if there has been a significant loss of institutional knowledge on how to make a lot of those old hand made animations No need to wonder: there has been, and basically all Disney 2D animation, even what little they do for the ci
785.
▲
by
ronsor
1y ago
That's exactly why it's problematic in licenses unless explicitly defined.
786.
▲
by
ronsor
1y ago
I pay for games because it's convenient. Most DRM is decidedly inconvenient for me, especially Denuvo-tier DRM. The end result is that if there's DRM, I'm more likely to pirate it or not play it if there's no crack.
787.
▲
by
ronsor
1y ago
If enough "relevant" countries do it, that either won't happen or won't matter. If the U.S. ditches it, no one is going to do much more than throw a brief fit.
788.
▲
by
ronsor
1y ago
The solution here is to get rid of copyright.
789.
▲
by
ronsor
1y ago
I'm not sure how this will work as crawlers don't read or accept ToS.
790.
▲
by
ronsor
1y ago
you can also just ignore the berne convention, and accept whatever consequences there might be
791.
▲
by
ronsor
1y ago
> This would be a great way to ensure Europe can grow its own. The reason this doesn't happen is because of Europe's internal issues, not because of foreign competition.
792.
▲
by
ronsor
1y ago
Contracts don't, but foreign law is going to make this a pain for OpenAI. Other countries may not care what a U.S. court orders; they want their privacy laws followed.
793.
▲
by
ronsor
1y ago
This court order certainly violates privacy laws in multiple jurisdictions and existing contracts OpenAI may have with customers.
794.
▲
by
ronsor
1y ago
We could, of course, repeal DMCA section 1201, but no one in government wants to do that.
795.
▲
by
ronsor
1y ago
That works if you want to launch an application from a website, but it doesn't work if you want to actively communicate with an application from a website.
796.
▲
by
ronsor
1y ago
Do note that since the removal of NPAPI plugins years ago, locally-installed software that intends to be used by one or more public websites has to run an HTTP server on localhost. It would be really annoying if this use case was made into
797.
▲
by
ronsor
1y ago
Yes, yes I'm sure. I like using C sometimes.
798.
▲
by
ronsor
1y ago
You can, but it will require far more memory than any computer has.
799.
▲
by
ronsor
1y ago
This is why you should randomize all behaviors which should not be depended on. Change things quickly and often if you're not making any promises.
800.
▲
by
ronsor
1y ago
50% people shilling LLM products, 50% people complaining about LLMs (or indirectly by complaining about crawlers) However, this place used to be JS framework news not too long ago
801.
▲
by
ronsor
1y ago
Can't we just submit bogus hashes?
802.
▲
by
ronsor
1y ago
Wow, Microsoft open-sourced Windows XP?
803.
▲
by
ronsor
1y ago
In some jurisdictions, there's one (or more) corporate directors who are legally responsible for a subset of activities. In that case, there are "nominee director" services where you pay someone else to take that position. Th
804.
▲
by
ronsor
1y ago
> Also how could you pinpoint the reference to your constant in the machine code? Not OP, but often one uses an easily identifiable dummy pattern like 0xC0DECA57 or 0xDEADBEEF which can be substituted without also messing up the machine
805.
▲
by
ronsor
1y ago
TLS 1.3 prevents tampering with the handshake. The transcripts won't match and the connection will be aborted.
806.
▲
by
ronsor
1y ago
> When the client sends a hello, the firewall says “that looks like a TLS hello”, and then waits for the server’s response. It inspects the certificate and then applies any rules. This kind of stuff is exactly why TLS 1.3 encrypts every
807.
▲
by
ronsor
1y ago
The authors can presumably update the dataset on the site; however, I think past versions remain. Besides that, the GDPR is at odds with the fact that public posts and data almost never goes away. I don't think that reality can be legi
808.
▲
by
ronsor
1y ago
> people do it with the whole TLS stack all the time. It's the only way to add custom TLS extensions.
809.
▲
by
ronsor
1y ago
China doesn't care about silly licenses.
810.
▲
by
ronsor
1y ago
Apple won't do anything right now as they're certainly afraid the courts* will slap them hard. *Both US and EU now
More ›