Migrated from @0x1C3B00DA
chat apps and systems like Twitter and Mastodon aren’t a good place for journalism
Super agree with that. Framing this feature as specific to journalism was a poor choice. The feature is useful for any writer/blogger/joe schmoe on the web
BEAM is the VM that Erlang runs on. It also supports Elixir and some other lesser known languages
My ponytail palm
on-demand pods that travel on existing abandoned railways.
They’re reusing existing tracks.
that looks like a console
Not just looks, but provides the UX of a console. So you buy it, plug it up, log in, and immediately start playing. Even consoles don’t provide that streamlined UX anymore, but ppl want all the benefits console used to provide with all the benefits PC gaming provides now. But the key part is the PC benefits don’t get in the way of the ease of it. You don’t have to install or administer a linux distro, you don’t have to twiddle settings for every game (unless you want to), etc
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.
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.
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.
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.
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
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
I would argue that overriding methods on a prototype is not a hack. It’s equivalent to overriding super methods in Java classes, but using javascript’s prototype-based inheritance instead of class-based inheritance.
But I agree with your main point about choosing a language that lets the developer implement their solutions freely.
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.
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 Group
s. 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.
It wouldn’t change that, unless the moderators of those communities agreed to merge them by using the same cryptographic identity.
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.
“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.
deleted by creator
I feel you but i dont think podcasters point to youtube for video feeds because of a supposed limitation of RSS. They do it because of the storage and bandwidth costs of hosting video.