HackerTrans
TopNewTrendsCommentsPastAskShowJobs

rdpintqogeogsaa

no profile record

Submissions

Forwarded Header Sabotage (2022)

adam-p.ca
2 points·by rdpintqogeogsaa·14 hari yang lalu·0 comments

Special-Use Domain 'home.arpa.' (2018)

rfc-editor.org
1 points·by rdpintqogeogsaa·2 bulan yang lalu·0 comments

Can Applications Recover from fsync Failures? (2020)

usenix.org
2 points·by rdpintqogeogsaa·6 bulan yang lalu·0 comments

It is high time we let go of the Mersenne Twister (2019)

arxiv.org
2 points·by rdpintqogeogsaa·9 bulan yang lalu·1 comments

comments

rdpintqogeogsaa
·3 tahun yang lalu·discuss
Interestingly, it seems there might have been independent invention of the same idea[0]. Have you checked for any patents in the space?

[0] https://bytes.grubhub.com/why-we-use-crypto-when-generating-...
rdpintqogeogsaa
·4 tahun yang lalu·discuss
> With CC0, you relinquish all rights to the work, including copyright.

With CC0, you relinquish your copyright only, but explicitly retain trademark and patent rights (!).

> 4. Limitations and Disclaimers.

> a. No trademark or patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.

This makes it sort of iffy for software when software patents exist unless coupled with some kind of patent waiver or assertion of not holding and not being aware of patents. While you can argue with MIT-0/0BSD/whatever else there might be that there is an implied patent license, there is an explicit non-license for patents with CC0.