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.
And if some indie dev lasts a little bit longer because I threw away a few dollars, i’m all for it
BEAM is the VM that Erlang runs on. It also supports Elixir and some other lesser known languages
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.
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
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.
yes exactly what sneezycat said. I was being sarcastic and pointing out that Manifest V3 was always a crackdown on ad blocking and nothing else.
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.
There’s no way Mozilla is replacing Google as the default, so what are they actually announcing here? I didn’t read any actual results thats happening. Are they just adding Qwant as an option in the search engine settings?
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.
deleted by creator
But public posts federating across the network isn’t an “experience”. It’s the basic functionality of the network.
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.