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

Yes! I've been leech blocking Reddit the past couple of days and I intend to keep doing so until I've broken the habit of absent mindly typing "Reddit" into a new tab whenever I have brief downtime waiting for something.

But in the mean time I find that search results for things point to Reddit at least as often as stack exchange.


> Will Reddit buckle under pressure and go back on the API changes?

If they do, it won't be for several months and only if there's a drop in traffic that looks to be permanent. The protest itself won't change anything.

A change in the API certainly makes sense (OpenAI showed the value of the reddit's comment data, and I think spez is pissed that OpenAI is not only profitable, in a large part due to the availability of reddit's comment data, but because OpenAI is run by another reddit co-founder). And maybe that's the plan all along...

There's an idea that users will hate any change you preset. If you give users minimal-change, they'll hate it and revolt. If you give users drastic-change, they'll hate it and revolt. So give them drastic-change, weather the revolt, then walk back to moderate-change and by-in-large they'll accept it.


>I imagine everything will go back to the status quo as soon as this protest is over. The mods have no real leverage, and a temporary outage like this isn't going to suddenly make a bunch of people switch to some other site.

I don't think reddit will be dead by the end of the year or anything quite like that. But we know from past studies (using that API, heh) that a very tiny percentage of site visitors post content. I think it was something like 10% of visitors are logged in, 1% of visitors comment regularly, and 0.01% post content. But something like 90% of the content is from only 1% of the users who post content, so the 0.01% isn't even that important, it's the 0.0001% who drive the site. And there's a lot of cross over between these power users who post all the content and the moderators of the largest subreddits.

So what will happen when the power users quit the platform? It's not just that lots of communities will go unmoderated and shutdown (if their mods don't shut them down first), but a lot of the content will dry up.

Now, vacuums fill and naturally any void left by the power users leaving will be filled by others who start posting, but that could very well be the beginning of the end. We saw this with Digg. There were several mass exoduses from digg to reddit and other sites that caused the quality of digg content to get worse and worse for the 3 or 4 years before Digg v4 put the final nail in the coffin. Had Digg kept old.digg running along side digg v4 it might have continued to suck for many more years, but Digg's influence on internet culture was decidedly in decline before Digg v4.

And that I think is what we'll see with reddit. Many communities will collapse, content will reduce in quality, and the slow attrician will begin. It won't disappear in a year or 3, but it won't be nearly as important in a couple of years as it is today. Remember when "slashdotted" was a term?

The big questions is "where will the users go?" When digg was fucking up, there was already reddit. Can fediverse link aggregators (lemmy, kbin.social, etc) really serve as a replacement? I'm not convinced. I've read there's efforts to make a link aggregator using BlueSky's AT protocol, but that's not yet here.


With secureboot on Linux you can secure as much or as little as you want. On my system, grub isn't even safe, only the shim that load grub is secure. But I could set it up so the kernel is secure, have the kernel only load verified initrd, and then have the initrd check the root filesystem.

I don't, but secureboot can detect changes to the root filesystem if you want it to. I think this generally requires setting the rootfs to mount readonly.


Who cares? It's on pypi (https://pypi.python.org/pypi/pyp/2.11) so just `pip install pyp` and then you have it. You're probably not going to want to distribute shell scripts that rely on pyp, but if you're distributing scripts you can just distribute scripts written entirely in Python and use pyp for your own one-liners.


I agree. It's just like how a carpenter's best tools are English, arithmetic, and blueprints.


All those things do help, but a carpenter can do the same job with an axe, a saw, a chisel, a knife, or a froe but in the end what they are doing is cutting wood. If you're a programmer and you don't look at languages as a tool you are doing yourself a disservice. In the end you just need something to turn some data into a different kind of data, everything else is a tool to do that one thing.


Torvald's has said in the past he won't ever change the license of Linux.

The GPL normally has a clause that says the source code has to be licensed under "this license or a newer version of the GPL". Projects that have moved from GPLv2 to GPLv3 did so because of this clause in the license. Torvalds specifically removed this clause.

I doubt Torvalds is concerned about whether or not users can use ZFS. He's defended the existence of closed source kernel modules (ex graphics drivers, network drivers). There's even the quote in the article that Torvald's didn't consider Andrew File System derivative of the kernel. Further, users can use ZFS-FUSE; there's no question that ZFS-FUSE doesn't infringe. Finally, Oracle owns sole copyright to ZFS; they can re-licence it.

Linux will never move from GPLv2 and I'd be really surprised if Torvalds saw the ZFS issue as a problem with the GPLv2 and not an Oracle problem.


Thanks, good answer. Is Torvalds legally correct with his defence of non-GPL kernel modules? I mean his position makes total sense to me technically, I just find it a bit strange that he wouldn't push for an OSS license that unambiguously allows for such kernel modules, s.t. everyone could shut up about this issue. I also understand though if his position is that it's just not a problem that needs to be solved (since he doesn't think that contributors would end up suing distributors about this issue).


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

Search: