The domain name was originally registered with Sav.com, a particularly scummy registrar known for sniping and auctioning off dropped domains. As it turns out, they aren't any kinder to their own customers than anyone else, and without sufficient warning (seemingly in violation of ICANN policies), they sent our domain to be auctioned off when a scheduled payment didn't go through, kicking off a frenzy of anti-communists trying to buy it.

Specifically, a registrar operating in good faith will generally disable resolution of the domain after it has expired, to alert the owner/users that it is expired and in the grace period to renew, but Sav does not, preferring to take domain owners by surprise and let the domain fully expire, forcing them to compete on the open auction to get their domain back.

Somehow, we managed to transfer it out of Sav to a less scummy registrar during the auction, recovering the domain for free. However, the 2 weeks or so where we were operating off of chapo.chat as a backup domain ended up causing a lot of technical headaches and roadblocks to re-enabling federation, hence the delay.

It's fixed

(thank you for letting us know)

Hi, thank you for reporting this issue! sorry it's taken a bit to work its way to the relevant people. It should be working now, assuming you are not currently rate limited and you don't require multiple retries to get the 2fa code right.

New pronouns require a small amount of dev time to add, but it's pretty easy normally. My bigger concern would be the ongoing rebase of our customizations onto lemmy 0.19.6. I've asked in the dev chat!

surprise! we browse the trans mega!

sie/hir has been added, give them a shot!

Yep. It is actually automated, it renewed on its own ages ago, but reloading the web server to pick up the new cert just silently failed. Should be resolved now.

(Note: this is not in any way an official statement by the admin team, I'm just a tech dweeb)

Proposal: Do Nothing, but improve searchability by making the shortcode autocomplete also search by tags, not just the canonical name.

We have the ability to add basically unlimited alt-names or descriptors to the tags for each emote, which has made searching in the emoji picker much more viable even for obscure emotes (provided they are well-tagged). Problem is, nobody uses the emoji picker, most people don't even know it exists.

Make sure the library is reasonably well tagged and make that tweak to the searching and this whole conundrum goes away.

Examples below of some existing tags from a previous effort to tag all the emotes:

We might also want to make the alt-text more descriptive for people with screen readers but that's a separate conversation

Edit: Oh it looks like a dev (comrade makotech222) has already chimed in on this below:

also, its maybe possible we can enhance the inline emoji window to use keywords as well. would have to do some experimentation with it.

 

secondary option if this isn't feasible: remove the unicode emojis from the emoji picker so it goes straight to our custom emotes when opened, and make it more prominent in the UI somehow (highlight it in a different color, make it bigger, make it sparkle, idc). And still finish the job tagging them all

As others have mentioned, that was implemented in a hurry due to tightening up security and safety around embedded images. I've brought it up to the devs to hopefully rectify, as if an instance is trustworthy enough to federate with (aka, not actively malicious) then it is probably safe to show their embeds (behind a blur).

At the latest, this restriction will go away when lemmy upgrades to pictrs 0.5 which will support proxying image requests, but unless there are objections from the rest of the team we will likely add all federated instances to the image allowlist before then.

Working on this very site. So nothing cool, no