[-] copygirl@lemmy.blahaj.zone 7 points 6 months ago

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.

[-] copygirl@lemmy.blahaj.zone 7 points 8 months ago* (last edited 8 months ago)

I don't think I disagree with you, I just think Valve should be the last company that should be under fire for the 30% cut. As in, it should come after plenty of other companies, because they actually do offer many valuable services in return. I'm all for lowering the cut Valve takes, just make sure every other storefront that does objectively less is required to do the same.

It also feels like complaining about the food from one store being expensive, while you get larger potion sizes than other places for the same price. Yes, food should be affordable. Shouldn't the complaint be made towards the industry as a whole rather than the store that is (for now) objectively better than the alternatives?

[-] copygirl@lemmy.blahaj.zone 7 points 8 months ago

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);
[-] copygirl@lemmy.blahaj.zone 8 points 10 months ago

Taming animals so you can ride them, or let them pull carriages? Building roads for vehicles? Train tracks with functional trains? Cool airships? All made obsolete with this one-kills-all glider feature! Don't let good game design get in the way of convenience! /s

[-] copygirl@lemmy.blahaj.zone 8 points 1 year ago* (last edited 1 year ago)

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.

[-] copygirl@lemmy.blahaj.zone 7 points 1 year ago

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.

[-] copygirl@lemmy.blahaj.zone 7 points 1 year ago

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.

[-] copygirl@lemmy.blahaj.zone 8 points 1 year ago

This is potentially dangerous, as it encourages dealing with text as an array of chars. But graphemes in Unicode, which represent a single symbol in a writing system (such as "H", "心", or "💚"), can take up multiple chars in a string. The linked approaches only work if you can guarantee that your string only contains ASCII. See also: The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No Excuses!)

[-] copygirl@lemmy.blahaj.zone 8 points 2 years ago* (last edited 2 years ago)

A personal instance generally doesn't have a big reach, unless people actively follow the person who's posting the doxxing information.* The fediverse may not be a good way to spread personal information of others, throwing up an instance like that is not much different than throwing up a website or forum.

There's two things I can think of you can do: Contact the company that hosts the website to take it down – I'm unsure about how you go about this, but I'm sure you can find out more about that. And to report the instance to other instance admins to get it blacklisted, perhaps get it on a block list, limiting its reach and thus effectiveness. Get in contact with big instance admins, they likely have chatrooms you could join, and they might be able to help with the other step as well.

*edit: In the case of Lemmy, I suppose it would be people following a community, rather than a user directly. If moderators or admins act on the posted informated and delete it, the deletion will federate as well and any legitimate instance will automatically delete the content on their servers as well. This would also be true for Mastodon and such. If not, the above applies.

[-] copygirl@lemmy.blahaj.zone 7 points 2 years ago

Just yesterday I replied to a post where a similar question was asked, so I hope it's okay if I just copy-paste my answer:

The best Mastodon instance is the one that aligns with your interests and values the most.

  • Are you interested in tech? There's a couple of tech-focused instances.
  • Are you some flavor of LGBTQ+? Some instances do a better job at keeping out bad actors, and you can be around like-minded people.
  • Are you interested in gaming? Movies? Art? Writing? Game development? Home improvement? Gardening? Activism? Memes? News?
  • Maybe you're interested in stuff happening in your country or local area?

Why? When you're looking for new content, and new people to follow, the local and federated timelines of your instance are a good way to do so. Your home timeline includes all the people and hashtags you followed yourself, and their boosts. The local timeline includes all the posts and boosts of everyone on your instance. The federated timeline has all the content that everyone on your instance is following. (Of course you can always follow anyone you like, but I'm making a point about ease of discovering content relevant to you here.)

For this reason, just joining a big, general-purpose is less useful, since you're just going to get a hodge-podge of random things in these timelines. Perhaps you don't mind, but I feel like it's good to point out this feature of the fediverse, as some people might not know, or realize this is a thing.

How? Okay, of course this is silly to recommend without giving you some way to look for these instances. There's a couple of directories that allow you to search for them. Looking for some briefly came up with https://instances.social/, https://mastodon.help/instances and https://mastodonservers.net/. Also note you can migrate your account from one instance to another, taking your followed content and even followers with you.

[-] copygirl@lemmy.blahaj.zone 8 points 2 years ago

It's a lot more legally dubious for them if you defederate. If your instance willingly connects and shares data out of their own volition, it's like that instance giving permission. If an instance blocks communication via the ActivityPub protocol outright, what are the legal grounds for Meta/Facebook to be able to freely access that information? Even if it's posted publicly to view.

As an example. I can have my own website and post some info there, write articles, have contact information. People can view it. Companies can index this information and make it available to search. But I'm guessing it's not legal (or at least less so) to be collecting that information to process and sell. Companies can do that so easily because you agree to it in their terms of service.

(But hey, IANAL.)

view more: ‹ prev next ›

copygirl

joined 2 years ago