followed tags: 28
followed domains: 3
badges given: 6 of 6
member for: 1579 days
Here's a better link. This isn't really about Trump, they're just using it to drive donations. IA does a donation drive every year, and they've been talking about doing a full, out of country backup for a long time.
Common Sense is one of the few audio shows that I always bump to the front of my queue. In the last few months Dan talked quite a bit about what 2020 might be like if an insider won the election, and I was hoping he might talk here about what he thought 2020 looked like now, but I don't think he did (unless I missed it).
I'm proud of humanity for banning international trade in African grey parrots.
That is really cool!
Here's one of my favorite versions:
One of the most notable things about 1201 is that it makes it illegal to tinker with or research ways to get around DRM for gadgets or media that you already own (even if you don't share it). Even if the DRM is poorly implemented and easy to get around, if it was meant to be a digital lock, it's illegal to try to break the lock. Cory Doctorow gave a keynote at the Decentralized Web Summit last month at the Internet Archive and talked a lot about DMCA 1201:
In the speech he talks a lot about one reason DMCA is becoming especially troubling lately: with EME DRM is being baked into the web.
It's a pretty complicated issue, because it definitely is solving a real problem: Netflix, spotify, etc. have needed to Flash/silverlight/whatever to prevent users from downloading files in their browser. With EME, users won't have to resort to using these closed source extensions that have often exposed them to security vulnerabilities.
On the other hand, EME means DRM is getting a first class seat in browsers. Whereas we've always been able to download and keep any media sent to us over the (open) web, EME will prevent that. And to add insult to injury, it severely raises the bar for any new browsers to enter the fray. From another EFF post:
- This system, "Encrypted Media Extensions" (EME) uses standards-defined code to funnel video into a proprietary container called a "Content Decryption Module." For a new browser to support this new video streaming standard -- which major studios and cable operators are pushing for -- it would have to convince those entertainment companies or one of their partners to let them have a CDM, or this part of the "open" Web would not display in their new browser.
edit: hey mk, could we get direct links to video and audio files to be embedded in posts like images are?
- How does it handle censorship?
Each person that adds or pins ("seeds") any content would presumably be legally liable in their jurisdiction for hosting that content the same as they would be hosting that content on a regular web server. So, probably no more or less censorship resistant than the web of today. However, IPFS would make it much easier for me to, for example, add content that my own government might want to censor, and then tell people outside of my country to pin it, and then I could stop pinning it and perhaps no longer be liable for it (if no one knows that it was added by me).
The devs maintain a list of content added to IPFS that have resulted in DMCA takedown notices, so that people can avoid pinning it.
The real win for IPFS is making publishing any kind of file over the open web more accessible to everybody and sharing the hosting load with others, rather than avoiding censorship (although perhaps we could say that IPFS could help to avoid censorship to the same extent that bittorrent does).
- Could IPFS have some kind of P2P DNS system? Could it set up something like .onion sites that are resistant to takedowns and DDoS attacks?
By default, every file and directory added to IPFS is given a hash, which makes that content accessible at /ipfs/`hash`. Like this. Everything added to this is immutable, meaning that link will always point to that exact file. If the file is changed and re-added, it will have a different hash. The mutable layer added on top of ipfs is called IPNS (inter planetary naming system), which you can use to always point to the latest version of your files (like a website, or the latest version of a software repository) with a different hash. Like this. Human-readable names can then be mapped on top of the IPNS name (with DNS or any other naming scheme). Like this.
The DNS gateways to IPFS (like ipfs.io and ipfs.pics) are stopgaps between HTTP and IPFS. Ideally for IPFS, everybody should be running IPFS so that they can add and pin content, and access content on IPFS without going through a http gateway, which is centralized behind a web server and DNS, so you have to trust the gateway controller to faithfully serve the unmodified content (same as a typical website). Any website could use IPFS on the backend (either like a gateway, so that it's visibly using IPFS, or just as a storage mechanism for files, like you suggest with .onion).
If you're accessing IPFS natively, then it's absolutely mega resistant to DDoS attacks, but a gateway or site with IPFS behind a server is susceptible like any other website.
- I'll have to look more into it, but I wonder if a RPi could be used as a small ipfs server, I feel it should...
I've got it running on my Pi 2 (and my laptop) and it runs fine. I usually have to restart it every few days because of high cpu usage. Honestly right now there's not much to do with it (except say "cool!") that a normal server doesn't do much better. It's fun to play around with but for it to be really useful you'd have to either join a "web ring"-like thing with some friends where you'd all pin each others content, or have a bunch of VPSs pin your content, or be part of a bigger project which is currently using torrents.
I live a couple miles south of where this happened, and my roommate happened to drive by the scene a few hours afterward. The mood in the neighborhood this morning is very strange and surreal. Such a terrible and pointless situation, to say the least.
People have been gathered at the governor's mansion down the road last night and this morning but we haven't heard anything from him yet.
Thank god for ubiquitous cell phones and internet connectivity. Though change will inevitably arrive much too late, it will have to come at some point.
Excellent. Not sure how I missed that one.
Correct me if I'm wrong (Wintermute), but I'm assuming she/he meant that prices are raised proportionally for everybody by places that accept credit to make up for the fees they have to pay, so you're paying a shop's credit card fees whether you're paying by credit or not.
I can't imagine that it's illegal in this situation, but I have no idea about the law you're referencing.