205 karma · joined August 11, 2010
They did not. Automod was created by a user as just another script that interacted with reddit's api (albeit, a powerful and useful one). Deimorz eventually joined reddit and became an admin, and Automod was eventually integrated into the site code (primarily for performance reasons), but that was completely user-created, and in fact a great example of how reddit's community governed the site for a long time in absence of much direction from reddit Inc.
Really? It seems to me that the problems come from not banning things, still: see all the complaints about racism and other "undesirable content" on the site.
We're already crowd-sourced! http://www.ifixit.com/Contribute Only about half our guides are staff-created.
> (I'd me more willing to contribute if the TOS wasn't so restrictive, but since I still own my content I don't mind so much"
Good news! Everything on iFixit is CC BY-NC-SA: http://www.ifixit.com/Info/Licensing (but you still own your content).
Not enough, and that's the problem. iFixit's purpose for existing is to get people repairing their things (electronic or otherwise); this is why we make guides and sell tools and parts, why we make all our guides freely available under a Creative Commons license, and why we spend a lot of time and effort convincing people that yes, they can repair things.
So when a corporation makes a visible effort to discourage these same people, we get frustrated. Yes, most Apple consumers don't want to repair their iDevices. But they never will if Apple continues discouraging them.
From: googlebot(at)googlebot.com
User-Agent: Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)#> vim /etc/pacman.conf [archlinuxfr] Server = http://repo.archlinux.fr/$arch #> pacman -Sy yaourt
There are some CSS animations in Mozilla's Demos: https://mozillademos.org/demos/dashboard/demo.html . They work just fine for me in 4b12.
Unless I misunderstand you, it certainly is when using Vagrant.
Indeed. As a moderator on a fairly active IRC channel (on Rizon!), I've seen my fair share of trolling. I remember an instance a few months ago where the room was engaged in trying to persuade a naive person to some viewpoint, gradually growing increasingly frustrated at his lack of acceptance of any points. Then, after a good 20 minutes, he said something to the effect of "Gotcha! I agree with you, but was just trolling.".
In my experience, the most effective method is to mute a troll before they have a chance to stir anyone up. Unmute them a few hours later to give them another chance to participate.
For those who aren't aware of the issues[0] that were revealed several months ago, Diaspora's devs made some rudimentary security mistakes. Yes, it's an alpha, but as pointed out in the HN thread (which I did not save, and am too lazy to search for), this was basic security - the stuff you have to keep in mind from the start, not stick on later.
[0]: http://www.kalzumeus.com/2010/09/22/security-lessons-learned...
http://www.gnu.org/licenses/gpl-faq.html#DistributingSourceI...
This is one of the features of git I most appreciated when I started using it (my first VCS was Mercurial).
I get distracted easily. While I'm rooting through the code base trying to do something, I'll notice something else to fix. And something else. And something else. By the time I've finished whatever I was trying to do in the first place, I've got 5 or 6 different things I've actually done.
In git, it's trivial to split these up - `git add` separate files, or `git add -p` when you only want to stage some of the changes in a file. This leads to cleaner commits.
I've heard people decry this, saying that you should be testing each individual state of your codebase. git being the powerful sonuvabitch it is, you can do that:
* `git stash --keep-index` will store away all of your modifications, other than the ones you're getting ready to commit. Run your tests, commit, `git stash pop`. * Checking out different revisions and running tests isn't a bad option, either, whether you use `git bisect` or do it manually. With the amazing power of `git rebase -i`[0], you can easily fix any little issues without disrupting other commits.
[0]: http://schacon.github.com/history.html
You will change their SHA1 sums, so they'll become different commits. This isn't a problem, though, if you haven't pushed them up to a shared repository.
It also doesn't help that Pandora has terrible tagging. I have a number of "Horner, James - Braveheart, Film Score"-esqe scrobbles that originate from them.