Pressure is the same on both ends, and the bottom of the can is already thicker than the sides of it. The top of the can is thicker than the sides, but thinner than the bottom, because you need to be able to open the can easily. So in order to make it thinner than the bottom but at least as strong, you use a different alloy.
I had this sort of issue. Back in 2010 I had mined a hundred coins (CPU mined, back in those days, lol). A month ago I decided to find the wallet file, took me 2 hours to search 5 HDDs with multiple partitions each from my old computers...
I fixed this problem now by printing the keys out, storing them securely in a safe and deleting the wallet files.
Sharing music, video and/or porn on the network will be mostly inevitable. But on the other hand, the web of trust should limit the impact of this alot. If you consider that people interested in curating/helping with the leaks and documents would distrust peers putting porn/music/video up, there will likely be 2 or more networks with little trust between one another.
You didn't mention anything about anonymization of the nodes/peers. I am guessing you're thinking of putting this behind Tor?
> You didn't mention anything about anonymization of the nodes/peers. I am guessing you're thinking of putting this behind Tor?
You'll be able to do so, but I imagine that most people will run this outside of Tor. 1) It makes it easier for people to access, and 2) In theory, there will be so many nodes that the risk to any one operator will be low.
HN isn't meant to solve the same problems as Discourse. Both attack on a common problem, which is making discussion meaningful, but the context is widely different. HN isn't meant to be used as a forum, it is a news discussion board, topics loose relevancy after just a couple days. Try adding lots of value to a topic by posting a reply after 48 hours, chances are, almost no one will see it, and even less people will reply to it. Forums don't work that way, you get discussions in forums which can last sometimes even years.
And considering other forum options, Discourse has probably a killer feature, which is "Best of" a thread. Forums are horrible for documentation, after a meaningful discussion topics usually go dead, and if you want to read an old topic (but relevantt to you) with 500 pages (or even just 20), it is painful, you don't need to read every single comment, and Discourse's "Best of" will (should) fix that. That is powerful.
There isn't an add-on, else it would be in that list. But we do got TOR Browser, which is optimized to be untrackable, out-of-the-box, with the standard configuration. Even when using it outside the TOR network, you are better off than with all of these add-ons (mostly because of browser fingerprinting that the OP's suggested configuration is succeptible to).
Beware though that not all sites will work with TOR browser out of the box (because of noscript blocking js), but it is fairly easy to whitelist the js code you need to make them functional.
There is actually an arduino shield that let you integrate arduino with the Lego microcontroller, so you can expand the number of inputs and outputs, though this is mostly a transition from lego to arduino, because at that point, you better off doing everything through an arduino (except that you get to use your lego motors and sensors with it this way). Here is a book that teaches about how to do it and talks more about the arduino shield:
C Interfaces and Implementations (David R. Hanson)
Expert C Programming (Peter van der Linden)
I'm also a fan of C Programming: A Modern Approach (K. N. King) as an introductory book, but it's very different in intended audience from K&R. King is writing for students, and he assumes nearly nothing. K&R are really writing for experienced fellow programmers, I think. So it's an apples to oranges comparison. But King is certainly more modern. He includes a fair amount of C99 material. The writing can't compare with K&R. It's nowhere near as dense or elegant. But if you find parts of K&R a bit too dense and elegant, it's a good trade-off. (I used them both in tandem while trying to learn C this summer. It worked well for me. When King got too verbose, switch to K&R. When K&R lost me, switch to King.)
King's book was my introduction to serious programming when I was younger. In an era of my life where I usually prefer ebooks, I still have King's book, in dead-tree format, and love it.
IMO, this is a better book at explaining C clearly: "advanced programming in the unix environment" by W. Richard Stevens. Don't be fooled by the title.. it's a beginner book.
> Don't be fooled by the title.. it's a beginner book.
I never know what to do with comments like this. It's obviously not a beginner's book. At the very least, it assumes that you know C. If your response is "C is a small language. You can learn it by reading <some-other-thing>.", you're admitting that APUE is not a beginner's book. If your response is, "C is a small language. You can learn it by reading APUE itself.", then I call bullshit. Is it theoretically possible, sure. But is it a natural way for a true beginner to learn C? Certainly not.
What do you mean by this? You obviously have NOT read it. I have. I'm telling you it is a beginner book. It does not assume you know C or anything else. It has nothing to do with the size of C. Grabbed it off my bookshelf -- he starts off telling you how to login to a unix system. How advanced can it be?
This is literally the book that taught me the basics of C within a week -- the first language I learned (15 years ago). So it is definitely a beginner book IMO.
Edit: I will say, he does get into some more advanced things toward the end. Which is why I like the book.. he starts off very basic, and by the end, he's covered the basics of interprocess communication, shared memory, etc.
I have read the book. It does not teach you C. It assumes that you know the language. It does not teach you anything about the syntax of the language.
He does not tell you how to log into a UNIX system. He tells you what happens when you log into a UNIX system. (That is a big difference. Compare the first chapter of Kerrigan and Pike's The Unix Programming Environment, which actually does teach about terminals and explicitly talks about how to log in and what a login is -- for a complete beginner.)
Here's the first bit of code, from page 5:
#include "apue.h"
#include <dirent.h>
int
main(int argc, char *argv[])
{
DIR *dp;
struct dirent *dirp;
if (argc != 2)
err_quit("usage: ls directory_name");
if ((dp = opendir(argv[1])) == NULL)
err_sys("can't open %s", argv[1]);
while ((dirp = readdir(dp)) != NULL)
printf("%s\n", dirp->d_name);
closedir(dp);
exit(0);
}
My point is very simple: If you do not know C and especially if you also do not know any programming language, it would require either magic or another book or tutorial to figure out the syntax or semantics of those lines. Why is the first include thingy in quotes and the second in brackets? What is an include thingy anyhow? What is DIR? Why do some things have a * in front of them? When are semicolons used? Not every line ends in one, but most do - why? What is the -> used for? When do I use parentheses and when do I use braces? What is argc or argv? Are those names important? What is NULL? Why are some things all capitals and some not. Does that matter? He doesn't answer any of these questions (nor should he), because the book is not meant to teach you C. It assumes that you already know C.
#include "ourhdr.h"
int
main(void)
{
printf("hello world from process ID %d\n", getpid());
exit(0);
}
Ch 7 is the environment of a unix process.
7.2:
"argc is the number of command line arguments and argv is an array of pointers to the arguments. We describe these in Section 7.4." exit codes are discussed in section 7.3, where he also talks about 0 in exit.
Granted, he does not discuss the syntax or NULL...
Looking through it.. I'll agree it isn't a beginner book. Intermediate at worst though.
Hmm... Having not seen the first edition of the book (which is the edition you must have given that you used it 15 years ago and it was updated 8 years ago), it's possible that your assessment of its elementary content is specific to that edition.
However, the second edition of the text is by no means elementary; unless you are conflating beginner literature with comprehensive literature, and the text is certainly comprehensive.
I'll grant you that Chapter 1 is a summary and introduction to the entire book with little challenging or novel material for someone experienced with UNIX and C, but many advanced texts have introductory sections. A large portion of the "The Art of Computer Programming: Fundamental Algorithms" is essentially a review of the elementary mathematics necessary for the analysis of algorithms, but I would never call TAOP a "beginners book"!
This thread has been interesting for me. The first time I've opened the book in 13-14 years probably. Not exactly what I remembered. So just ignore my posts :)
As I mentioned in another reply, if you upload in high res, and your uploaded image is big enough for a decent print, you will be able to print photos at 10x15cm without an issue. Any bigger of a photo, low resolution issues will appear.
Do you charge for shipping? 50 cents per photo seems pretty high, unless you have free shipping. Or maybe that is just the right price and I shouldn't compare it with our prices here in Brazil (we print millions of photos at where I work, in an HP Indigo printer, for less than a quarter than that, though we charge for shipping separatedly).
Yes, the charge for shipping is a flat rate of $3 to anywhere in the world. I also agree 50 cents is a bit high, I would like to get it down at some point. I am using a fulfillment provider and currently at the mercy of their costs (this is very convenient though). It sounds like since you print your own and have a large volume you can get the cost much lower. I think printing my own in the future may be an option and would lower my cost a lot.
