@0x1C3B00DA@fedia.io avatar

0x1C3B00DA

@0x1C3B00DA@fedia.io

This profile is from a federated server and may be incomplete. For a complete list of posts, browse on the original instance.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

Then, there is TikTok algorithm which is a common critic of the app but is how you get a never-ending flow of content which isn't uninteresting enough for you to turn the app off

I think there needs to be some kind of discovery algorithm for new users with an empty feed (or even existing users who just wanna find something new) but a federated alternative doesn't need something as powerful as the tiktok algorithm to be a decent replacement. It doesn't need to surface a "never-ending flow of content" because it doesn't have a financial incentive to keep you in the app endlessly.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

My ponytail palm

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

I could see walking through a debug session document with a junior dev to guide them on how to debug classes of issues better. Or if they're running into a bug and ask for your help, you could write out the first few debugging steps and let them take it from there. That might be easier to understand than "I'd check service X and see if it's processing Y like it should or just passing it on to Z". Having a defined way to explain how to debug an issue could be useful

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

on-demand pods that travel on existing abandoned railways.

They're reusing existing tracks.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

This issue has been noted since mastodon was initially release > 7 years ago. It has also been filed multiple times over the years, indicating that previous small "fixes" for it haven't fully fixed the issue.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

People have submitted various fixes but the lead developer blocks them. Expecting owners of small personal websites to pay to fix bugs of any random software that hits their site is ridiculous. This is mastodon's fault and they should fix it. As long as the web has been around, the expected behavior has been for a software team to prioritize bugs that affect other sites.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

Relying on the competence of unaffiliated developers is not a good way to run a business.

This affects any site that's posted on the fediverse, including small personal sites. Some of these small sites are for people who didn't set the site up themselves and don't know how or can't block a user agent. Mastodon letting a bug like this languish when it affects the small independent parts of the web that mastodon is supposed to be in favor of is directly antithetical to its mission.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

Harvesting the dataset isn't the problem. Using copyrighted work in a paid product is the problem. Individuals could still train their own models for personal use

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

I'm not familiar with the exact amount of resources, but I know it takes a lot. My point was about what specifically is in contention here.

Also, you were the one pointing out that this case could entrench "giant fucking corporations" in the space. But if they're the only ones who can afford the resources to train them, then this case won't have an effect on that entrenchment

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

What legislation like this would do is essentially let the biggest players pull the ladders up behind them

But you're claiming that there's already no ladder. Your previous paragraph was about how nobody but the big players can actually start from scratch.

All this aside from the conceptual flaws of such legislation. You'd be effectively outlawing people from analyzing data that's publicly available

How? This is a copyright suit. Like I said in my last comment, the gathering of the data isn't in contention. That's still perfectly legal and anyone can do it. The suit is about the use of that data in a paid product.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

It's funny how this comes after Chrome's switch to Manifest V3, which makes ad blocking not possible on Chrome and was purely for security reasons and not for disabling ad blockers. Now that Chrome users can't block ads on the first-party site, they're going after third-party clients. Such coincidental timing.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

expanding organic cropland can lead to increased pesticide use in surrounding non-organic fields, offsetting some environmental benefits.

It's ridiculous to call this a harm of organic farming.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

It wouldn't change that, unless the moderators of those communities agreed to merge them by using the same cryptographic identity.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

Super disagree. A community at the protocol level can have just as much character as a community at the network level, but without most of the drawbacks. The "instance as community" idea was always a poor substitute for actual Groups. The community shouldn't be a server that users are bound to; it should be a Group that has access controls and private memberships (if desired). The moderators get all the same benefits of maintaining a limited community with their own rules, but users aren't beholden to petty drama via instance blocks or defederation.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

If you break that up you end up with only a few large and likely advertisement funded instances being able to survive.

I'm not saying I don't think instances should be able to use that model, only that I think that model should not be the dominant way of building a community on the fediverse. But I don't see why a user would be less attached to a community just because its hosted on a different server from them, especially on the threadiverse which is topic based and where users are most likely going to engage in multiple topics.

Holding Hands with the "Fediverse" – ActivityPub at SFO Museum ( millsfield.sfomuseum.org )

SFO Museum has joined the “Fediverse”. We have begun to operate a series of automated “bot” accounts that are published using the ActivityPub protocols and that can be subscribed to from any client, like Mastodon, that supports those standards. These are automated, low-frequency, accounts and they currently only support...

Deadly morel mushroom outbreak highlights big gaps in fungi knowledge ( arstechnica.com )

On Thursday, Montana health officials published an outbreak analysis of poisonings linked to the honeycombed fungi in March and April of last year. The outbreak sickened 51 people who ate at the same restaurant, sending four to the emergency department. Three were hospitalized and two died. Though the health officials didn't...

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

"Morels are more likely to cause intestinal distress if eaten raw, although even raw, they can be tolerated by some people," the agency wrote. Morels should be cooked before eating, as cooking can destroy bacterial contaminants. "For that matter, all mushrooms, wild or cultivated, should be cooked to release their full nutritional value because chitin in their cell walls otherwise inhibits digestion," the USDA writes.

The article mentions multiple times that cooked mushrooms are safer than raw ones.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

The article also points out that there were people who ate the raw sushi with no adverse affects, so mentioning "their established toxicity" seems like it would be just as misleading.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

I think you missed a key part of the article. Content Nation was not harvesting data from the fediverse; it was just federating. It was a new project that had just spun up and didn't have a full feature set yet, but other than those missing features it was a normal fediverse instance.

0x1C3B00DA , (edited )
@0x1C3B00DA@fedia.io avatar

for profit corporation being able to suck up your posts is probably what has many upset

They can already do that without a bridge. And it doesn't "suck up your posts". It works just like any other instance. They have to search for you and follow you. Then they receive posts going forward, but they won't get historical posts.

I personally would block such a service

Good! You can do that and that is a perfectly reasonable solution. That's part of what has ppl upset on the other side of this argument. All of this arguing and vitriol is happening over a service that you can block like any other fediverse actor.

0x1C3B00DA ,
@0x1C3B00DA@fedia.io avatar

But public posts federating across the network isn't an "experience". It's the basic functionality of the network.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • test
  • worldmews
  • mews
  • All magazines