Hacker Newsnew | past | comments | ask | show | jobs | submit | almondsays's commentslogin

I am not a lawyer. I would imagine you could be charged with 'obstruction of justice' or some other such law if you did this in the US or as a US citizen. Something to think about before doing such a thing.

edited to be more verbose


http://www.law.cornell.edu/uscode/text/18/part-I/chapter-73

This is the federal obstruction of justice statute, could you point out the part that applies to jamming the illegal collection of inadmissible evidence by an agency that enforces no laws or regulations and conducts no criminal or administrative investigations or proceedings?


You're absolutely right. The government, NSA, et al, would definitely not take anyone to court over this. That's the wrong tool for this job.


No, I'm not a lawyer and/or qualified to do that. Maybe I'm wrong, but I don't care to find out by attempting it.


This is an unintentionally perfect demonstration of the concept of chilling effects. Someone should take a screenshot of this and put it into a textbook.

Wikipedia link on chilling effects: https://en.wikipedia.org/wiki/Chilling_effect


The fear of getting caught shouldn't be the only reason you don't do something. Either it's important enough to do, or there's multiple reasons doing something isn't a good idea.


Trolling the NSA to prosecute someone for 'obstruction of justice' for essentially being a nuisance, is a dream scenario for the ACLU/EFF/EPIC/et al.


did I ask for my connection to be wiretapped?


"Hey, this web app thing is popular, everbody is making one. And I like the web. I should make one myself."

Just some perspective.


Yeah, except with beer you have 2-3 orders of magnitude more starting expenses.


Well, that's shallow too.


Boiling frog expirement?


This is fun.

  - Instagram says it now has the right to indefinitely detain under NDAA
  - Redditors earning $100k+ a year, secret files show
  - Physicist proposes new way to view IAmA's on Reddit
  - Linux may have been due to bad connection
  - Kim Dotcom: The US recording industry is stealing my ebook


Some more:

- 3px of padding makes all the female developers?

- Postgres on the moon

- Game Over: Zynga Shuts Down 84,000 Websites, ‘By Mistake’

- IBM to Acquire Tumblr

- Firefox Beta 15 supports the possible suspension of U.S.

- Kim Dotcom: The US recording industry is stealing my ebook


> At what other point in history has police distributed a completly illegal tool onto unsuspected and non-targeted civilians?

It might be a stretch but..

"LSD was one of the materials tested in the MKUltra program. The final phase of LSD testing involved surreptitious administration to unwitting non-volunteer subjects in normal life settings by undercover officers of the Bureau of Narcotics acting for the CIA." - http://en.wikipedia.org/wiki/Project_MKUltra


Thank you. It was a covert human research operation experiment rather than police enforcement, but it still bear some meaning on this issue. The government offered one victims family an out-of-court settlement of $750,000.

If the government release a virus and it cause damages, government might be found liable. Still, an out-of-court settlement is not exactly a predicate, so its hard to know what would happen.


I was interested until I saw that it starts at €7,250.00!


Have you seen the Just5?

http://www.just5.com/


They're not that very well built. My retired anti-tech, luddite, menu-fearing dad had plenty of trouble using the older, more squarish model.


Woah, the brick [1] is seriously cool (no irony), I would love to try one of those out.

[1] http://www.just5.eu/brickred.php


Excuse me if this is a naive question but I'm kind of confused on using just a few lines of code. I know you must attribute the original creator when the license calls for it but where? For instance lets say I have 500 lines of code and 10 lines of borrowed code at lines 245-255. Whats best practice in that situation?


There's practically no difference between using 10 lines of GPL code and using a whole package. In either case: you must comply with the terms of the GPL license; your own code is now GPL'd. The exceptions to this rule aren't worth litigating.

If you're not interesting in (say) GPL'ing your code to match the 10 lines you lifted, you would be better of just reimplementing those 10 lines yourself.


I don't think there is a commonly agreed practice. My opinion (and what I tell my students):

Independent of the specific license, I would suggest listing sources (and uses) of all external code in your LICENSE file, and at the header of each file. This makes it much easier to check for license compliance later on. Most open-source licenses require attribution but do not explicitly specify how this should be done.

Example: "check_for_update() from stackoverflow.com/... (CC BY-SA)"

Depending on the license of the code you are using, you might be required to mention its use in your application's documentation (e.g. BSD, CC BY).

If the code is in the Public Domain or is not sophisticated enough to be protected by copyright (thin ice!), there is no need to mention it in the source code.

If it is just a few lines of code, try to put it into its own function and add a short comment. This also allows you to easily remove problematical code later on.

Generally, if it is just a few lines of code, dealing with the license issues is usually not worth it. For example, you can not legally mix CC BY-SA code from Stack Overflow with GPL code. I would suggest just looking at the SO solution and writing your own implementation of the algorithm (not completely safe but probably the most convenient solution).


Treat it like a citation in a paper. Add comments acknowledging and saying where the code came from. If nothing else, it'll help refresh your memory on why you needed it.

Also be aware of the original licensing for the code. If it's any more than attribution you'll need to determine how it affects the rest of your code and if you might need to reimplement.


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

Search: