Shoutout to our hard-working maintainers, first of all.

Wanted to open a space for the community to discuss this aspect of marketing/identity.

Original comment link [e: snip]

You are viewing a single thread.
View all comments View context
4 points

This comment would be more relevant a year down the line if perspectives shifted and users begged for sanitization, but:

Is it technically challenging or financially costly or otherwise problematic to mirror content to another subdomain, or domain mask or something? I thought of this after seeing oldsh.itjust.works:


try.itjust.works

leg.itjust.works

share.itjust.works

subm.itjust.works

(2 & 4 don’t work as well as the current split word)

No reply requested unless it seems like it would be fun/interesting to type one

permalink
report
parent
reply

I’m not an expert on the specific of this, but changing the domain for the UI (as in oldsh.itjust.works) seems a lot easier than changing the domain for the backend, which includes federation with all other instances.
I don’t know of any way to change the federated stuff without breaking pretty much everything and starting over.
Maybe there is and I just don’t know about it, or maybe there could be an easier way at some point.

permalink
report
parent
reply

sh.itjust.works Main Community

!main@sh.itjust.works

Create post

Home of the sh.itjust.works instance.

Community stats

  • 81

    Monthly active users

  • 116

    Posts

  • 546

    Comments