Migrated from @0x1C3B00DA
It’s a cool feature, but it sucks that (once again) the mastodon team is taking control of fediverse-wide features and ignoring outside criticism.
Doing an AMA on mastodon would be a horrible experience for everyone. Others have pointed out the obvious difference in reach, blocks/defederation means some ppl may not even be able to participate, participants might never receive questions, users from different instances wouldn’t be able to see sibling comments, etc.
PWAs were not liked when they came out.
By some ppl. There were also ppl who did like them. As soon as the desktop support was axed, fans of the feature started complaining immediately.
at the time, people in general did not like PWAs as a concept. Independent of the browser
Again, I think this is a sampling issue, because my experience was the complete opposite.
And one of the key parts of PWA features was the “Progressive” part. The site works without those features and you don’t have to use them so removing the support never made much sense to me.
BEAM is the VM that Erlang runs on. It also supports Elixir and some other lesser known languages
My ponytail palm
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
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
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.
These “Aerocarts” will be pulled down the runway by the lead plane just like a recreational glider. They’ll lift off more or less together with the lead plane, then stay on the rope throughout the cruise phase of flight, autonomously surfing the lead plane’s wake for minimal drag and optimal lift
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.
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.
deleted by creator
But public posts federating across the network isn’t an “experience”. It’s the basic functionality of the network.
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.
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.