Hacker News new | past | comments | ask | show | jobs | submit | tkw01536's comments login

I'd second this - linking directly to `https://arxiv.org/abs/{{id}}` maybe even include the formats in the `Access Paper` box on the RHS of that interface would be a neat feature.


i added a 'source' button on the index and paper page that takes you to the link you mentioned, thanks for the feedback


I believe the questionable legality also extends to any kind of video calls taking place on systems with this turned on. If Recall indeed "does not perform content moderation", then having it on would include having screenshots of all video calls.

Especially in many-party consent jurisdictions recording video calls by taking screenshots at a sufficiently high frequency without the explicit consent, or at least option to opt out, of remote parties is probably illegal.

Disclaimer: IANAL and this isn't legal advice.


I usually interpret the “we” in scientific papers as “you (the reader) and me (the author)”.


At one point a project in a research group I'm part of did automatic parsing of the entire OEIS to find relations between different existing sequences. Using a very simple approach, they found ~300 000 000 relations (e.g. meaning one sequence can be expressed as some combination of other sequences); see section 4 of [1].

However they submitted only three (!) of those back to OEIS. Even with 130 reviewers on the OEIS side, submitting all of those relations would have basically been a Denial-of-service attack on the review process.

[1] https://kwarc.info/people/mkohlhase/papers/icms16-oeis.pdf


You can actually also use the latexmlc omni-executable [1] (that is part of the latexml distribution), which can convert to html in one command:

    latexmlc --dest=mydoc.html --format=html5 mydoc.tex

[1] https://math.nist.gov/~BMiller/LaTeXML/manual/commands/latex...


Wouldn't the grant given through section 5 of GitHub TOS [1] apply here?

That says "you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality".

In other words, without an explicit license you can do whatever you like with publically viewable content as long as it runs via GitHub.

[1] https://docs.github.com/en/site-policy/github-terms/github-t...


> as long as it runs via GitHub.

That is extremely limiting...


Yes it does, e.g. compare the pdf [1] and corresponding html [2].

[1] https://arxiv.org/pdf/2312.12451.pdf

[2] https://browse.arxiv.org/html/2312.12451v1


Even if the official tool does shut down, a quick search shows several projects on GitHub to replace the official flashing utility. This seems to include a backup of the original site [1], an extended version [2] and a dump of the firmware [3].

[1] https://github.com/bestadamdagoat/stadiaupdatetool

[2] https://github.com/luigimannoni/stadia-controller-flasher

[3] https://github.com/Scyne/stadiaRawBtFw


However D4 also explicitly says "This license does not grant GitHub the right to sell Your Content". One could argue that because Copilot is a commerical product it is in fact selling (a derivative of) user code, and thus the grant in D4 does not apply.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: