Also yes 😆

Not that, specifically, but I get annoyed when people post screenshots of videos that have the “play” icon on them. My dumbass clicks on those 9 times out of 10.

South Park: What Scientologists Actually Believe

Beyond that, it’s a cult / pyramid scheme.

Also, check out Leah Remini: Scientology and the Aftermath documentary for a good insider’s perspective.

It’s not the documentary, but here’s Leah explaining the scam: https://www.youtube.com/watch?v=oM-FrI5Hqto

I think they’re stating the opposite: that there are multiple posts about it in many, many communities.

Yeah, mostly. It’s a third party UI that you’d use in place of (or alongside) any other. Works on mobile (optionally as a PWA) and desktop.

Not sure if lemmy.ca runs it directly, but the hosted instance is unlocked so that it can connect to any Lemmy instance.

Sadly, Lemmy doesn’t provide crosspost information in the feed; the frontend has to detect those duplicates and roll them up itself.

Not sure if any other UIs do, but Tesseract will match crossposts on title as well as URL (the default UI only uses URL). I wrote that behavior in specifically for what you described; I was annoyed by seeing 3-4 duplicate posts to different communities all in a row.

It’s not perfect since the crosspost rollups only happen if the duplicates are fetched in the same batch, but it does help a lot.

That’s why I’m trying to block out all this and enjoy this last month and a half as best I can.

I’ve said before (and will say again) that US elections are like our national-scale county fairs: idiots that your normally never see come out of the woodwork.

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

Taco Bell

Both chili and vegetable soup.

Never cared for either growing up, but now they’re both comfort food, especially on cold days.

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 fucking 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.

I think the real dick move is offering up their services as digital scabs.