As an admin of my own instance... We have a while...
jgrim
joined 2 years ago
MODERATOR OF
And you get to do it again!
Yes, it reminds me of the old internet. I love it. I haven't been this excited since I found newgrounds.com
It's a bug in the current front end. They are about to release version 0.18, which fixes this. I have a beta site setup on my instance if you want to check it out. beta.discuss.online.
There have been several folks creating new front-ends from scratch. I think there will be a lot of improvement very soon.
It was a reference to how they felt bee-trade by Beehaw. So basically have two accounts. First, at Beehaw and second somewhere else that doesn't block federation.
Or two, so you have one for fun and one for... science.
The platform just needs to mature a bit. It’s new and discovered in desperation. It’s free and not monetized. Everyone is working in their free time to build something wonderful.
The Mlem team went from 2 people to 20. They’re about to drop a huge update to their beta app.
The lemmy team worked on front end improvements in the upcoming 0.18 front end.
I have a beta instance setup if anyone wants to see it.
Don’t feel betrayed. Have two accountants. Move to a new instance. Or just wait for them to federate again when the dust settles.
There’s a bunch of other instances. Like mine at discuss.online. Nothing new is needed.
Seems like you’re just suggesting everyone use beehaw with federated accounts.
I'm the admin over at discuss.online. I'm currently scoping out a plan to build a moderator tool. I'd love to chat to help drive my scope. I'm planning to open-source it. Please, reach out to me if you're open to talking.
I also plan to ping admins of other instances to get input. However, your input seems more immediate as you're dealing with these issues.
Did you restart the container after you updated the lemmy.hjson file? The container needs to reload to pickup any changes to that file. You can do docker-compose restart lemmy to restart just that single container.
Also, you posted your database password with your config file. You should change your Database password now that it's "leaked".
Can you show your Lemmy service? Or include the entire docker-compose.yml file? Did you restart Lemmy after you updated the config?
Yeah, there is a massive movement right now. It'll get there. I have tech friends that don't quite get it. It's so simple for me. I'm struggling to find an easy way to explain in.