copygirl

Presumably this is because a block is different from the content being removed. It simply means the servers stop communicating with each other regarding new communities, posts and comments. This could allow the instance to be unblocked and the old content to continue existing – say for example when an instance has been acting badly, but it gets fixed some time later.

Blocked instances should probably not show up in search, but if you have a direct link to an old post, perhaps this should still be available? Not being able to block a community when its instance is already blocked makes sense, and probably doesn’t matter if you mostly check for new content, but I can see it being a bother when its shows up in other situations. One could call this a bug, or an oversight, but I suppose it depends on what the intended result is.

Politicians decide things, but to actually make stuff happen, the government needs to collect taxes to pay for services that are then provided to the public. I think the idea here is to take out the middleman. You won’t solve the problem country wide, but you’ll help some people, and that’s still worth it. Work together without like-minded people locally, be an inspiration, and show that it works. I’ve only been very briefly part of an activist group (specialized in food saving), so probably best to look elsewhere for good advice on how to do this well.

Yeah, it should not be part of the text just like line numbers shouldn’t be part of the code on a code hosting site, yet it can be visible, no? Later it does recommend using $ to distinguish command and output. Is it now okay for a beginner to be confused about what it means?

Is providing a number of commands to use that require user input really that bad? When people start tinkering with the command line, first of all they shouldn’t trust just anything on the website blindly, which at the very least requires a basic understanding of how to enter commands, and respond to the terminal asking for input. The following “bad” example…

sudo apt update
sudo apt install software-properties-common
sudo add-apt-repository ppa:deadsnakes/ppa
sudo apt install python3.9

…is instead turned into this single command with even more confusing syntax for beginners:

sudo apt update && \
  sudo apt install --yes software-properties-common && \
  sudo add-apt-repository --yes ppa:deadsnakes/ppa && \
  sudo apt install --yes python3.9

Sure, it’s convenient, but if you just throw blocks of code at people to run, are they really learning anything?

A better approach would be to have a quick tutorial on how to use the terminal and what the $ and # symbols mean (though they could be CSS decorators that can’t be copied), what sudo is and warning people about running untrusted commands on their system. Then you just link to that at the top saying something along the lines of “if you’re unfamiliar with running commands, and the following seems confusing, check this quick summary”, behind a question mark icon connected to each block of commands, or similar.

Then you should also override Equals(object), GetHashCode, and implement IEquatable<T>.

Thankfully a lot of the usual boilerplate code can be avoided using a record class or struct:

public record Person(string Name, uint Age);

Is this not what the “active” sorting does?

The lenses don’t have to both be at the same distance to be fair.

The real question is not what the algorithm pushes to you, but whether their moderation actually bans bigots and removes their posts. Any other instance would lose their “right” to federate with a queer-friendly instance if they didn’t do that, so why would Threads get an exception?

Isn’t “queer friendly” and “federates with Threads” an oxymoron?

Both banned by your instance: https://lemmy.world/instances

I don’t think that’s how it works and it would likely not be legal. By explicitly blocking Threads, you make a big statement about not wanting your instance’s posts to show up there. Also from a technical standpoint, I don’t think a “middle-man” instance will push posts from another instance to a third one. You’d have to explicitly scrape data that’s not available via the API. Please correct me if I’m wrong.

Actually this is pretty easy. First of all you got to get a stack of exactly 1 TNT and place it down where you want it to explode. Be careful not to put anything else in the slot the TNT was in because that’s now shadow-linked with the TNT you placed. You need to somehow get a redstone signal to activate in the same tick as you punch the TNT block. It’ll take a bunch of tries. Be careful not to pick up the dropped TNT item, or it’ll go into the shadowed slot. That part is pretty random. Next open up the chat and type “BOOOM!” or similar. It helps if you copied the text beforehand so you only have to paste it in. Log out of the server and never come back because you’re a bad person.

Could you please provide some sources for that? I’d like to know more.

First of all though, there is no such thing as a “hostile fork”. Being able to fork a project, for any reason, is the entire point of open source. And to be fair, not wanting to continue working for a for-profit company for free is a very good reason.

And yeah, when you suddenly turn a FOSS project that’s been developed with the help of a bunch of contributors, into a for-profit company, without making a big fuss about it beforehand and allow the contributors and community to weigh in, then yeah, that’s a hostile takeover of sorts, at least in my opinion. Developers gotta make money, but they could’ve done that by creating a new brand instead of taking over that of a previously completely FOSS project. Forgejo is preventing that exact thing from happening by joining Codeberg (a non-profit).

There’s been a hostile takeover at Gitea and it’s now run / owned by a for-profit company. The developers forked the project under the name Forgejo and are continuing the work under a non-profit. See also: Their introduction post and a page comparing the two projects. Feel free to look up more, since I haven’t familiarized myself with the incident all that much myself. Either way though, maybe consider using Forgejo instead of Gitea.

I did decide to delete all my comments and posts on Reddit. Sure, maybe I’ve posted some helpful comments, but why support Reddit with their continued existence? Remove content, and people might move to other sites to get their information.

I also decided to keep my account. Turns out some content stayed around, because I could not see and therefore delete it in locked subreddits. So when they came back, the comments came back too, and I was able to delete them, still.

Something else to consider in place of or in addition to a build number could also be using the git commit hash of what you’re building. Though I would only use that for non-stable releases.

For example, stable versions of Zig look like 0.12.1 and then there’s in-development releases like 0.13.0-dev.351+64ef45eb0. It uses semantic versioning where the “pre-release” is dev.351, which includes an incrementing build number, and the “build metadata” is 64ef45eb0, the commit hash it was built from. The latter allows a user to quickly look up the exact commit easily and thus know exactly what they’re using.

What I’m saying is that Microsoft is, in fact, being hostile by limiting OSS builds such as Codium in the ways I’ve mentioned above. I guess that’s how they try to get people to keep using their proprietary build instead.

Version 5 of a software, device, vehicle or such isn’t necessarily better than version 4, and no official definition of the word “version” require this, either. If I may make another anology: You may pick one of 5 different versions of an outfit to wear, and even though they were labeled in the order they were made, from 1 to 5, none are inherently, objectively better than any other. In the case of UUIDs there are versions that are meant to supercede others, but also simply alternatives for different use-cases. Anyone with access to some up-to-date information can learn what each version’s purpose is.

except for visual studio code

But also:

• Telemetry everywhere
• Not permitted to use the official marketplace with OSS builds
• Not able to use certain extensions (like C# debugger) with OSS builds

Though I’ve been very happy about the direction .NET and C# have been going, especially the licensing.

Not to be pedantic but I think the headline is fine.

If you simulated a fire in a building for training purposes and upon activating the fire alarm, it got broadcast to emergency services when it shouldn’t, you did accidentally broadcast the fire alarm, simulated or not.

The “accidentally” already implies it was done in error, suggesting it was not an emergency. On the other hand, if it was a real emergency, and just wasn’t meant to be publicly broadcasted, I feel like the headline would’ve looked different.