42
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Oct 2024
42 points (100.0% liked)
Asklemmy
43657 readers
2467 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
You talking about pathfinder.social? Yeah as best I can tell, the server is still technically up, but it's not really functioning correctly, so you just get what looks like an empty Lemmy instance if you go there directly. If you go to !pf2general@pathfinder.social (or one of that instance's other communities) from your own instance you can browse the old content, but don't bother with any replies or posts; they'll seem to work and display to you, but not get sent out to anyone on any other instances.
nope pathfinder@ttrpg.network shows wierd for me. This asklemmy I am on though shows fine which is asklemmy@lemmy.ml
Hmm, interesting. I don't know about Mbin, but on Lemmy this sort of thing could be caused if you were on an instance where nobody has subscribed to that community yet. But your instance also has problems with !rpggreentext@ttrpg.network, !vamp_tm@ttrpg.network, and !rpg@ttrpg.network. And even !rpgmemes@ttrpg.network is failing to federate comments. It could be a problem with how Mbin works, or simply caused by nobody on your instance subscribing to those communities. Not sure.