copygirl

joined 1 year ago
[–] copygirl@lemmy.blahaj.zone 2 points 3 weeks ago

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?

[–] copygirl@lemmy.blahaj.zone 17 points 3 weeks ago (2 children)

Isn't "queer friendly" and "federates with Threads" an oxymoron?

[–] copygirl@lemmy.blahaj.zone 2 points 1 month ago (2 children)

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.

[–] copygirl@lemmy.blahaj.zone 3 points 1 month ago* (last edited 1 month ago)

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).

[–] copygirl@lemmy.blahaj.zone 133 points 1 month ago (4 children)

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.

[–] copygirl@lemmy.blahaj.zone 13 points 1 month ago

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.

[–] copygirl@lemmy.blahaj.zone 0 points 3 months 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 0 points 3 months ago (2 children)

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 0 points 3 months ago (4 children)

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.

[–] copygirl@lemmy.blahaj.zone 14 points 6 months ago

I use uBlock Origin + vaft from TwitchAdSolutions, which is currently working pretty well for me. I've had some issues before, and every now and then the stream can freeze up when an ad is played. But it's so much better than having to endure even a second of those mind-rotting ads.

[–] copygirl@lemmy.blahaj.zone 5 points 9 months ago (2 children)

At the moment, upvotes and downvotes, while not used that way by many people, is more about what others will see, rather than what content you like. It's more like a community moderating and rating effort. Upvotes make posts more visible, by pushing them further up in what's currently popular. Downvotes do the opposite, and in my personal opinion, should be reserved for posts that don't fit the community they were posted in, spam, or things that break rules – typically the same reason why you would (and should) report a post. They are not "agree" and "disagree" buttons. Topics you disagree with can still spark interesting conversations.

Using the same mechanic, voting, to tell an algorithm whether similar posts should have higher visibility on your own feed, would be incompatible with this existing system. Posts that get a quick reaction or emotion out of you are even further encouraged, while things you simply don't want to see (but aren't necessarily "bad") get punished heavily.

This system works through subscribing to communities you are interested in and actively participating in improving the health of those communities, rather than passively consuming content. That takes some effort, yes.

All in all I think this proposed system is not compatible with Lemmy, and maybe not even a good idea.

[–] copygirl@lemmy.blahaj.zone 8 points 10 months ago* (last edited 10 months 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.

view more: next ›