Logging in, seeing who else logged in, to a small community that controls its own destiny.
Lately I’ve been nostalgic, I guess, about how tech was in the 90s. It was less glamorous, less usable, but also way more human and civil. Everyone was just into technology and sharing cool stuff.
This little corner of the web kind of feels like that sometimes.
I finally understand, thank you! I’ve seen this comment re: searching a few times but I thought it was for just that, “searching.” I figured if I already knew the community and instance it would be as simple as appending to the Partizle URL. Searching via complete URL isn’t bad either, and users in bigger instances shouldn’t see it pop up as often.
Yeah, it’s not as elegant as it could be. And it’s basically unexplained using the site.
Plus, it doesn’t really provide any feedback that it’s trying to go out and find it. It just says no results, until it finds it, and then results just show up.
Lemmy is a little rough around the edges.
Replying again because having a direct line of comm with an Instance Admin is pretty awesome.
Is there a reason we should see any desync issues between the same community on different Instances? For example, https://partizle.com/c/sysadmin@lemmy.ml shows 0 comments on most threads, while the “native” https://lemmy.ml/c/sysadmin has all the comments available.
This issue is not unique to Partizle, seeing similar from https://lemmy.dbzer0.com/c/sysadmin@lemmy.ml, though there are more comments (but not all.)
I haven’t dived into the codebase at all for Lemmy (and I don’t really know Rust anyway) but my best guess is that, because lemmy.ml had a lot of downtime in the past 48 hours, it had trouble fetching comments. I checked it twice yesterday and got 503 or similar errors. I would assume (but haven’t personally verified) that periodically (or based on activity) they’ll resync comments and it’ll show up again.
Again, I’m not a Lemmy developer and couldn’t say directly. I just wouldn’t be surprised of all the lemmy.ml downtime this week affected its synchronizations with other instances.