phase_change @ phase_change @sh.itjust.works

Posts

8

Comments

62

Joined

2 yr. ago

Yeah, runaway global warming might not happen. Plant monocultures would begin to disappear. New invasive species wouldn’t happen, though existing ones might have a better time for a bit. Major thoroughfares wouldn’t create barriers to migration. Dams might take centuries to collapse, but I think humans going extinct might have one of the biggest impacts.

I believe you are correct. Any paying Red Hat customer consuming GPL code has the right to redistribute that code. What Red Hat seems to be suggesting is that if you exercise that right, they’ll cut you as a customer, and thus you no longer have access to bug fixes going forward.

I suspect it’s legal under the GPL. I’m certain it violates the spirit of the GPL.

I am not a lawyer, but I have been a follower of FLOSS projects for a long time.

Me too. I know what I’m suggesting is functionally impossible. I’m wondering if it could be done in compliance with the GPL.

All of those contributors have done so using language that says GPLv2 or higher. Specifically says you can modify or redistribute under GPLv2 or later versions. So nothing stops the Linux Foundation from asking new contributors to contribute under the GPLv4 and then releasing the combined work of the new kernel under GPLv4.

The old code would still be available under the GPLv2, but I suspect subsequent releases could be released under a later version and still comply with original contributions.

Again, I know it won’t happen, just like I believe Red Hat’s behavior is within the rules of the GPL. I’d love to hear arguments as to how Red Hat is violating the GPL or reasons why the kernel couldn’t be released under GPLv3 or higher.

I suspect what Red Hat is doing is compatible with GPLv2, which is how the Linux kernel is licensed. I’m certain what they are doing is inimical to the Intent of GPLv2.

That raises some questions and possibilities. It looks like the Linux kernel still has the GPLv2 or later clause, despite not moving to GPLv3. See https://www.kernel.org/doc/html/v4.18/process/license-rules.html

How possible is it to create a GPLv4 that addresses this? Building a new license that does shouldn’t be difficult. However, I’d assume the Linux kernel isn’t released under a GPLv3 or later because of some objections with those changes. I’d imagine creating a GPLv4 that addresses the Red Hat issue but leaves out the changes in GPLv3 is likely a non-starter because those that have chosen a GPLv3 or later license will object.

Given the thousands of contributors to the Linux kernel, is an upgrade to a GPL version higher than v2 even possible? I’ve got no idea, but I’m curious of any insights.

Upvotes and downvotes.

Right now, I can browse by New on my subscribed communities and see every post since the last time I did that.

I can view or re-view posts and read every response. If the responses are legion, I can play with hot/top and get the meat of the discussion.

Did you notice that last sentence? On the few posts where there are too many responses to view all, I’ll try to get at those that are relevant.

If the Lemmy community grows large enough, I’ll need to do the same for posts. I will no longer be able to regularly view by new and have time to see everything.

So, I’ll need to rely on some sorting method to make certain I see relevant stuff.

Someone with millions of bots that never post have millions of upvotes and downvotes to influence the score used by the sorting algorithm that I’ll use to decide what to read.

But aren’t thumbnails local?

Part of what prompted my question is that I doubt I have the correct worldview because I believe I’m influenced.

The abstract for that paper is very interesting. Thanks for that link.

I agree that developing critical thinking skills, a willingness to question one’s beliefs, and a comfort with not knowing enough to have an opinion are all ways to help protect from manipulation, and likely ways that don’t lead to conspiratorial thinking.

No. They can be used in influence campaigns. They can upvote the posts and comments the controllers want you to see and downvote those they don’t.

Spam’s obvious and can be dealt with. Bots altering what shows up in your feed is impossible to combat as an end user.

In some ways, this shows Lemmy is winning. It means Lemmy’s important enough to start trying to influence. It also means we’re about to go through some interesting times.

I migrated to Reddit after Digg imploded. Here’s a few things I think were better.

Feeds weren’t filled with meme posts. Comments weren’t filled with quick one-liners to get upvotes. Back then, there was much more substantive commentary.

Now, over the years, I’ve subscribed to subreddits that contained the type of content I wanted, plus the default subreddits I was subscribed to as a new user back then are much different than today. Open Reddit using a different browser or a private browser window, so that you’re not logged in. How does that compare to your experience of 12 years ago?

Honestly, much of the things I don’t like are because of large entities wanting to influence social media. That same thing will happen (likely is already happening) to the fediverse. I just hope the distributed nature makes it more difficult.

I’ll agree and go one further: the idea of wanting to recreate Reddit is bad.

Most of us left Reddit because of the API crap, but I suspect most of us have not been as happy with the Reddit experience as we once were. The more you recreate a system that’s close to Reddit, the more you make it easier for influence campaigns, spam bots, and disruptive trolls to operate.

Federation, with separate but similar communities, makes it tougher for a massive bot operator to run a monolithic influence campaign. My hope is the design of the fediverse helps to defend against these types of attacks. My fear is the inexperience of server operators with these types of coordinated attacks makes it difficult.

Perfect! Thanks.

My concern is less the VM hosting the docker instance getting compromised but that Lemmy has an exploit and the Lemmy instance getting compromised. I’m quite certain that Lemmy is getting a closer look by the bad guys. You’ve had hundreds of instances spun up in a week, most that have done nothing more than follow an online example of how to spin up a Lemmy instance.

And, I was under the impression that the container and thus the logs were cleared when restarting or redeploying docker. If I’m wrong, I’m horribly embarrassed and will point at that “old school” in the title. I’ll also be doing some testing.

Kids these days with their containers and their pipelines and their devops. Back in my day…

Don’t get me started about the internal devs at work. You’ve already got me triggered.

And, I can just imagine the posts they’re making about how the internal IT slows them down and causes issues with the development cycle.

Nice. I’ll definitely check it out.

I’m intrigued by the phrase “crowdsec security engine on the docker”. Yes, I can Google, but I’d appreciate a bit of comment on what that is and how involved the setup is.

Agreed on all counts. Of course none of that exists on the on the Lemmy docker instance.

It doesn’t stop you from being hacked, but if you are hacked, it helps you to understand how so you can defend against it. So, I agree it doesn’t improve security for your instance, but it can improve security for your future instances.

Yep. I’ve hosted my own mail server since the early oughts. One additional hurdle I’d add to you list is rDNS. If you can’t get that set up, you’ll have a hard time reaching many mail servers. Besides port blocking, that’s one of the many reason it’s a non-starter on consumer ISP.

I actually started on a static ISDN line when rDNS wasn’t an issue for running a mail server. Moved to business class dsl, and Ameritech actually delegated rDNS to me for my /29. When I moved to Comcast business, they wouldn’t delegate the rDNS for the IPv4. They did create rDNS entries for me, and they did delegate the rDNS for the IPv6 block. Though the way they deal with the /56 IPv6 block means only the first /64 is useable for rDNS.

But, everything you list has been things I’ve needed to deal with over the years.

In your user settings, there’s a Blocks tab. I’ve not blocked anything, but I assume you can unblock there.