
Even your own posts will be hidden from your own profile, if you have “show read posts” unchecked, I think. Like I say it has some pretty weird behavior sometimes.
Even your own posts will be hidden from your own profile, if you have “show read posts” unchecked, I think. Like I say it has some pretty weird behavior sometimes.
Yeah, probably. The other side of “this is so badly needed why haven’t you done it for us” is “if this is so badly needed why haven’t any of the server admins or mods implemented it yet.”
I feel like this is an example of how the core dev team running on an instance that basically just has 3 of the admins do more or less all the moderation for the entire site is not ideal. This type of feature is probably one of the most-requested pain points for most people who run most servers, but my guess is that it’s basically completely invisible to the .ml team why it would even be needed, because their model works fine for them, so why would they.
Of course they’ve got a right to work or not work on whatever they want, but if their goal is success and good moderation for most servers this type of scalability and teamwork enabling thing is super important.
Are you comfortable running a little python script to do it? I’ve done something like this for myself for exactly the same reason, I could polish it up and show you and you could use it locally for yourself.
Your “friend”, huh
Stop acting in ways that violate the social contract and stuff like this will stop happening to you. I have no idea, but I strongly suspect that it’s exactly what it looks like: You’re blocked wholesale from the instances in question in some way which doesn’t show in the modlog.
I don’t even really know how to trace back through all the hall-of-mirrors of what original behavior led to what drama led to what sanctions led to what further drama. Regardless, step 1 is to just openly ask, hey what behavior should I be doing, what should I not be doing. And then just go from there and cooperate with the other people on the network to do the first and not the second. Lemmy is pretty frickin lenient with anyone who is willing on some level to engage with that whole process openly.
https://en.m.wikivoyage.org/wiki/Main_Page looks like what you want.
There are lots of wikis for specific domains, what are you looking to write a guide for?
deleted by creator
I think probably it is not 😕
Yep. You are 100% correct. ActivityPub has some significant flaws.
Hm, I would try just changing it back first. Use geekroom.tech. Any community or anything that federated or went into the database, with one of the other hostnames, is probably cursed now, and best just deleted and never looked back on. But, if you try to reinstall, you won’t be able to keep geekroom.tech as the domain at all, you’ll have to pick a new one (or just use a subdomain like lemmy.geekroom.tech).
Once stuff is federated out from one install under some given domain name, it’s pretty much immutable from that point forward. It probably shouldn’t be that way, but that is the current state of things with ActivityPub being the way that it is unfortunately.
It says: The server returned this error: couldnt_find_community
. This may be useful for admins and developers to diagnose and fix the error.
rDataHoarder also doesn’t show in the list of local communities.
Did you change the domain of your host, after it had already done some federation and created databases, or something like that? I do see the rDataHoarder community in the list of non-local communities, which is a real bad type of error to be seeing. You didn’t do any hacking around in the database to fix things or anything did you? That should never be that way as far as I know.
Hm, I saw no posts on your instance for !rDataHoarder@geekroom.tech, so I tried to make one on my instance to see if it would show up, and now your server’s giving me an internal error viewing that community. Do you know what’s up with that?
I think the time period during which whatever-it-was was making things not work, may have left your federation of communities in a borked state. One thing you can try: Unsubscribe from some particular remote community from all users on your instance (so your instance will request to stop getting updates). Then, resubscribe, and see if you start getting updates again. The initial request to get updates might have gotten swallowed by the brokenness.
This might be a good question for the devs, also. Both because they can help more and because they should know about it as an issue (whether or not it was caused by some Cloudflare thing and whether or not it was your “fault” in setting it up, both of those questions I have no idea.)
Oh… yeah, you’re right. No idea then.