JAR, SWF and CGI-bin scanning by path only is fine, since there are relatively few of those. But .js scanning by path only is too broad.
One option would be to filter out by size, an information that is contained on the CDX. Let's check typical ones:Ignoring some obvious unrelated non-comms files visually we get a range of about 2732 to 3632:This ignores the obviously atypical JavaScript with SHAs from iranfootballsource, and the particularly small old menu.js from cutabovenews.com, which we embed into ../cia-2010-covert-communication-websites/cdx-post-js.sh.
grep -f <(jq -r '.[]|select(select(.comms)|.comms|test("\\.js"))|.host' ../media/cia-2010-covert-communication-websites/hits.json) out | out.jshits.cdx
sort -n -k7 out.jshits.cdxnet,hollywoodscreen)/current.js 20110106082232 http://hollywoodscreen.net/current.js text/javascript 200 XY5NHVW7UMFS3WSKPXLOQ5DJA34POXMV 2732
com,amishkanews)/amishkanewss.js 20110208032713 http://amishkanews.com/amishkanewss.js text/javascript 200 S5ZWJ53JFSLUSJVXBBA3NBJXNYLNCI4E 3632Gérard Bricogne is a prominent French scientist known for his contributions to the field of X-ray crystallography. He is particularly recognized for his work in the development of software and methodologies for the analysis of crystal structures. Bricogne has been involved in creating tools that aid researchers in obtaining and interpreting crystallographic data, which is essential for understanding the molecular structures of a wide range of substances, including biological macromolecules such as proteins and nucleic acids.
Insider trading can discourage investment, and cause CEOs to hide information from employees. While there have been arguments that insider trading makes share prices more quickly go to their proper value, the true solution is that if investors dislike insider trading, companies can legally declare that they will only work with those that legally agree not to trade its shares or facilitate insider trading. If someone unaffiliated with the company simply overhears or comes across insider information, this won't stop them, but even if it were illegal, it would be nearly impossible to prove such a case.
Why is this FAQ licensed under the Creative Commons Attribution 4.0 (CC BY 4.0)? by
Libertarianism FAQ 0
Libertarianism FAQ 0 At first glance, it would seem pretty ironic for an FAQ that lambasts intellectual property rights to place restrictions on its own distribution, even if just attribution. But asking for attribution is consistent with libertarianism.
It is to prevent people passing this FAQ off as their own work, as they could get social/monetary benefits from doing so, and that should be considered fraud. Even if they don't explicitly claim to be the author when using its contents, that is likely to be assumed by most readers, so not explicitly disclaiming it should be treated as fraud.
This does not mean that anyone who doesn't provide attribution must be sued into oblivion; the punishment must be proportional to the crime, after all, and in most cases, any personal clout gained from omitting attribution will be negligible. But for the very few cases where it's not, the license facilitates the prosecution of such fraud in the current legal system.
Pinned article: Introduction to the OurBigBook Project
Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
Intro to OurBigBook
. Source. We have two killer features:
- topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculusArticles of different users are sorted by upvote within each article page. This feature is a bit like:
- a Wikipedia where each user can have their own version of each article
- a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.Figure 1. Screenshot of the "Derivative" topic page. View it live at: ourbigbook.com/go/topic/derivativeVideo 2. OurBigBook Web topics demo. Source. - local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
- to OurBigBook.com to get awesome multi-user features like topics and likes
- as HTML files to a static website, which you can host yourself for free on many external providers like GitHub Pages, and remain in full control
Figure 3. Visual Studio Code extension installation.Figure 4. Visual Studio Code extension tree navigation.Figure 5. Web editor. You can also edit articles on the Web editor without installing anything locally.Video 3. Edit locally and publish demo. Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.Video 4. OurBigBook Visual Studio Code extension editing and navigation demo. Source. - Infinitely deep tables of contents:
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact





