Ah yes, the “local taxi lobby.” Uber helped show a lot of us what a fucking joke that is, not just in Ottawa.

Innovation, choice, quality and freedom are the choice spices for capitalism soup. These shit-cook-legislators kept sprinkling in taint like protectionism, cronyism, extortion and corruption thinking nobody would notice. Well guess what? Now it’s just taint soup.

Why does it matter who’s serving you taint soup? The problem is there’s no other soup and they keep telling you it’s fine.

Vendor lock-in is 100 times worse today than it was 20 years ago. It’s vile, insidious and borderline cruel. Microsoft doesn’t want to work with anyone, they never have and they never will.

Any feelings of openness and cooperation you get from them is engineered, from the ground up, to ensure that they are in a position of control over you.

Their crack security team is not the result of some spontaneous and sudden desire to protect their customers. It’s a consequence of having to constantly triage the financial impacts of a never-ending stream of critical vulnerabilities.

Labelling this proprietary shit “ecosystems” is insulting to ecosystems. They mere notion that you should be using Microsoft software to monitor, secure and protect your Microsoft software is downright ridiculous.

Microsoft is not the only, and maybe not even the worst, in a long list of hand-wringing, life-sucking, progress-hindering companies who people will willingly defend because these companies have forced their way into becoming a part of our identities.

That makes more sense.

So any comment or post?

It can be on instances with lots of users and open signups.

Donate to the Lemmy project, but also look at donating to your instance / instance admin. It ain’t free to host and operate this stuff.

Commendable that you want to help, but the software needs to handle dead installations as there is no possible way to enforce people to decommission. :) Might be worth dropping just to help the use case of how this gets handled. I feel like you did everything you could.

They want to start an instance for star wars fans because they like captain picard. :)

I’ve been saying this for a few days now, but alas! Downvoted, scoffed. I just don’t get it. I am not advocating for anything other than true decentralization, which is broken in more than one way with the lemmyverse. Defederation is not even the issue. No, I don’t want nazi communities. No, I don’t have anything against admins. I just want to see the system work as it’s touted to work. People are so protective of their communities, and rightfully so, but we need to think hard about the differences between moderation and exclusion. One can foster a safe community, the other will just isolate.

100%. Work together on stability, resilience and privacy while ignoring trolls? Hell no! Let’s focus on creating silos and sniffing our own farts first!

Not sure about the abort banners. The remote communities behaviour sounds perfectly normal. The resolve object error could be related to your instance trying to pull content from another.

I think there has been some issues with the docs and maybe the config files in the repo for nginx / reverse proxy. It’s definitely a key part that some paths go to the UI and some to the backend. It sounds like your sending a request meant for the ui to the backend.

Identities should be federated and not local to instances.

Join an instance that does not allow local communities. Then you can subscribe remotely to whatever you want and block whatever you don’t.

It has to be done by manually by changing a row in the database AFAIK. Are you on matrix? If you ask in there someone might work with you.

Came to make this comment.

The popular instances can take a long time to respond. There’s no feedback in the UI either, you click search and then eventually the result will appear. Depending on what you search for, your instance collects more data than what you’re actually searching for.

Great work!

That is essentially what happens and it’s a technical issue, not a philosophical one. If one instance is denied posting to another, the user should be notified at some point about that. There are a lot of silent errors right now with the setup. If you disable signups for example, users can still try but never see that it will never work.