

It seems the dev just wanted to run it as a personal fork and never understood the reason for the pr standards in a collaborative environment
No Port-knocking? Amateurs! /s
Just an interesting point that “Free trade” isn’t. There’s always externalities, like a frienly nation-state military making sure your markets remain open.
Yep, it hit many lemmy servers as well, including mine. I had to block multiple alibaba subnet to get things back to normal. But I’m expecting the next spam wave.
The point of it being a core feature, is that people are not going to Discord for its DM capabilities.
That’s true about DM, however DMs are not a core use-case for discord-like services. It’s the group/voice chats etc. I could see a workaround like lemmy does, where if you want to DM a user in another server, you might be able to do it through your fediverse instance (i.e. a DM simply has your fediverse instance DM their fediverse instance), but I’m sure there can be more elegant things like. However DMs by themselves are a weird thing by themselves, so much so, that even bluesky had to bolt DMs on-top and outside of their protocol.
Sorry but what exactly do you communicate and access between discord servers? Are you talking about PMs which are by default independent of servers?
Unified search could easily be achieved through third party tools at the least, like for IRC. I don’t think even discord has unified search between servers.
The bloat that it had tacked onto it since then is egregious.
VCs gotta make back that ROI…
Sounds like this is part of their business plan. Make hosting it so onerous, you’re better-off using their servers, or paying them to do it for you.
Just use croc to share files. Then size doesn’t matter.
I guess the easy solution here to to make it use oauth2 authentication. Then you can just authenticate using one account elsewhere. If fediverse services also at some point become oauth2 providers, then even better.
deleted by creator
Revolt != Matrix
I’m not using the js-client. I’m updating pythorhead so I need to make sure the API is at the final version before I can match it. And to match it I need the patches to be in so I can read the doc, and/or import the swagger.
I will do what I can in advance, but to do the pre-development you asked for, we do need the final version up somewhere.
Ah, good to know before I start developing. Can you let me know when we can start the development as I don’t want to use the API and then discover it’s missing more PRs?
Does this mean you renamed just the DB columns, but not the API keys?
Oof, lots of work to do for everyone.
If anyone can figure out all the non-mentioned API changes and write them here it would be useful for people like me to avoid having to reverse engineer things
I’m ok with people promoting services which accept cryptocurrencies (hell, Lemmy itself accepts crypto donations). However promoting cryptocurrencies itself is a no-no in our instance.
Also: Crypto is a not private. The blockchain is public.
As much as I like this approach, I want to hear if the author has at any time successfully sued anyone with it because I seriously doubt it.