Reddit is dead to me and blocked in my router, so I’m good sharing knowledge and cool stuff here.

Matrix also is close to checking all the boxes, but it wasnt clear how it works on mobile (Element seemed like the mobile app that was recommended).

I run Matrix, and it’s pretty great. Though I would recommend Schildichat over Element for the mobile app. I had all kinds of issues with Element Mobile somehow screwing up the E2EE keys for my other sessions. Nothing seemed to fix it except removing my account from it completely. Switched to Schildichat and haven’t had that issue since.

I read the PR. It seems more like a hacky bandaid rather than addressing the actual issue. But I digress.

It’s also possible I misunderstood where/how the limit was being applied. My understanding was that it was limiting the response to 50 per depth (50 seems to be the arbitrary limit for most of the API’s list endpoints). What I really don’t want to do is have to paginate the request for the top level comments.

e.g. if a post has 100 comments, and say, 60 of them are top-level, I much prefer to be able to get all 60 in one go. Depending on the total number of comments provided in the getPost call, I dynamically set max_depth higher (3-5) or lower (as low as 1) and fill in the deeper comments manually with a “show more” button. The exception is if linking directly to a comment where it uses the path to calculate the exact depth to fetch.

finding one with a chain of over 50 in a row is even more rare. Such a thread would be clunky to display in the main comment tree anyways

I’m working around that without pagination, but it’s a low priority fix since Patrick’s Law come into play. It’s like Godwin’s Law except it says that once a comment thread gets deeper than 9, it’s a slapfight that’s best avoided.

I’ve got a laundry list of reasons, but suffice it to say that pretty much every third party client I’ve ever used has been miles ahead in UX and polish.

One example is that if the API throws any error response and lands you on an “Error” page (post removed, user deleted, etc), the whole UI is stuck there until you refresh the whole page (e.g clicking “back” updates the URL to your previous page, but you’re still seeing the error).

Reduce maximum comment depth to 50 by @nutomic #5009

Goddamnit. I removeding hate paginating comments and would rather just fetch all the top level ones and control the depth based on the number of total comments. I also hate that they see the API through the lens of Lemmy-UI (IMO the worst way to interact with Lemmy).

Haven’t messed with it personally (yet), but I’ve seen some examples where Caddy can do some cool stuff (I think the example I saw recently was defining routes that can call an arbitrary program with the HTTP request details).

I use Nginx almost exclusively (I’ve got HAProxy in the mix, too, but it’s strictly for load balancing). Everyone always keeps recommending Traefik to me, but from what I’ve seen, it doesn’t do anything Nginx can’t already do, and the config is all bizarre and way less intuitive. Not saying it’s bad, just not for me. (This is not an invitation to proselytize Traefix at me lol).

Use whatever works for you.

Going to check that out because…yeah. Just gotta figure out what and where to archive.

Yeah, definitely.

I hope @willya@lemmyf.uk sticks around on another instance.

Congrats. This is my last remaining form of social media, but once I got my feed and block lists curated, it’s been pretty great here.

Cool, thanks!

Is there a Github link?

That’s a question for the admins there, but HC is the spiritual successor of, and ran by the same team as, ExplodingHeads. EH was frequently defederated for homophobia, transphobia, bigotry, racism, conspiracy, brigading, hate speech, and general toxicity.

I’m not sure if they’ve cleaned up their act since rebranding, but maybe they figured they’d start out with just the big instances since they were frequently de-federated before?

Context:

• https://hilariouschaos.com/comment/9345
• https://gui.fediseer.com/instances/detail/exploding-heads.com
• https://gui.fediseer.com/instances/detail/hilariouschaos.com

I think you just answered your own question. If ponder.cat isn’t on their white list, content won’t federate.

I naturally read that in Alan Davies’s voice lol

Agree. If you’re not interested in something, just block the community/curate your feed and don’t spam downvotes. It’s like intentionally showing up somewhere you don’t want to be just to “boooo” everything.

Steps in Tesseract:

1. Click the community name in the post to bring up the community profile modal.

2. Click “Block Community”

3. You and the people minding their own business with their own interests can now both be happy.

Bonus: This works from the feed and from the post. If you’re in the feed when you block a community, any other posts to that community will magically disappear.

Edit: Updated the images so OP didn’t think I was throwing shade (I wasn’t)

They simply filter communities from those instances, and not much else. It doesn’t even hide user interactions from those instances.

Yep. “Block instance” is basically “block all communities on this instance”. Its API-level behavior leaves a lot to be desired.

Some UIs will filter users from blocked instances (posts and comments). I know Tesseract does, and I think maybe Boost does?

“One of the biggest functions of blocking is giving women the ability to stop weird men from constantly making them uncomfortable and scared,” one user wrote. “So of course Elon had to change that.”

They buried the lede a bit there, but that’s pretty much it.

SWF shouldn’t engage with Meta at all

Lol I didn’t either.