:(

I felt bad making a long thread once I opened Element X and saw it didn't have support for threads.

Someone let me know later that threads are hidden behind a Labs setting, but it only allows the client to reply to threads, but still exposes the entire thread inline for the channel which sucks up all the air in the chat.

this is wrong - the threads support in labs lets you create threads and navigate into them as you expect.

what you are describing is the old threads workaround which predates the proper solution in labs which should exit labs asap.

I am describing what I see on Element X on iOS today. If someone replies to threads, it is not hidden and navigable on this client. Even after switching the labs feature on, the app was showing the thread interspersed with the rest of the conversation.

Uninstalling the app, reinstalling, and making sure the labs option is turned on before navigating to a room with threads, is behaving how I expect.

So maybe, its a bug that the room does not re-render after toggling that setting.

ah right - that sounds very plausible; sorry for the confusion. have filed it as a likely bug at https://github.com/element-hq/element-x-ios/issues/4810 - thanks for the report :)

Pre-launch I seem to recall using an entirely different product with the same name, that supported CUE or HCL and had a better gui editor. I think post acquisition they scrapped it for the current (and IMO) worse reskin.

My experience disagrees with the 'Respects robots.txt' column for most of the bots listed. Would love to see more details of how they determine that metric.

Are you verifying the IP, or just blindly trusting the user agent?

Good question - I am just putting up robots.txt, and seeing little to no decrease in traffic. I have not tried verifying that server logs user agent corresponds to specific IP addresses. Do you have resources where all the AI bots post their list of IP addresses? Would be easier to just ban by IP completely. From what I've read these bots rotate and use residential blocks so I am not sure I can even see all of them.

I am having trouble imagining the failure mode you are trying to avoid.

It sounds like threads implementation of federation is broken. What effects does toggling that federation setting on or off do?

Like if someone is following “duplicate” accounts of yours and therefore would see double posts, that person can unfollow one. Still double work for you that kind of sucks.

Scuttlebutt had some work done on publicly declaring two identities as the same, I wonder what that would look like for posts. Like a post-id or simple equality comparison or hash could work server side or client side.

I wish the coating lasted longer, I had to throw some tape on mine to keep using it - the rubber keeps wearing down.

I find it hilarious/sad that the 0.5x cheaper Ergo M575 has much better design in that regard (just plastic that doesn’t degrade)

Helps the maintainer focus their efforts during review. If you wrote that exact sentence, a maintainer would keep "understanding of the codebase" as a place for potential sources of incorrect assumptions higher in mind than otherwise.

In my experience, if there's one thing the AI assistants do really well, it's understanding existing code and summarizing it or pinpointing specific things I'm looking for.

Run a community space that uses its own SSO, and needs to share passwords for socials and the like.

Been using this since it was merged. No issues so far, appreciate the work.

Love the relaxation of git-specific guardrails to make jj workflows better.