Lemmy

12542 readers

38 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago

MODERATORS

nutomic@lemmy.ml

why didn't lemmy community actors get put on a subdomain? (toast.ooo)

submitted 5 months ago by grant@toast.ooo to c/lemmy@lemmy.ml

2 comments fedilink hide all child comments

always wondered this, but kept forgetting to post it

eg users would be on @grant@toast.ooo and a community would be on @canvas@group.toast.ooo or something like that

then it would still follow the AP spec but still allow for identical identifiers (like a user account being @sc07@toast.ooo and a community also being [!sc07@toast.ooo](/c/sc07@toast.ooo))

top 2 comments

sorted by: hot top controversial new old

[–] scrubbles@poptalk.scrubbles.tech 0 points 5 months ago (1 children)

As an instance owner, the amount of overhead to support that would be nuts for me. Each subdomain would have to have DNS routed to it, or a wildcard which isn't the best supported. On top of that I'd need to somehow manage certs in a way where when the software detects a new community it'd have to ask for a new cert and broadcast the new domain to everyone. Then what do you do about communities from other instances on your instance?

What is being done is the right way. We use DNS to tell us different services/hosts. We use the path to tell us a subsection of the same service

[–] jmcs@discuss.tchncs.de 1 points 5 months ago

TLS certs can have one level of wildcard (even let's encrypt supports this), and creating subdomains programmatically is not exactly black magic - the main blocker from the technical side is that the code to update the DNS is usually not portable between providers, so it's not adequate for a federated open source project.