this post was submitted on 30 Oct 2024
418 points (97.9% liked)

sh.itjust.works Main Community

7716 readers
1 users here now

Home of the sh.itjust.works instance.

Matrix

founded 1 year ago
MODERATORS
TheDude@sh.itjust.works
manifex@sh.itjust.works
biela@sh.itjust.works
imaqtpie@sh.itjust.works
418
Feedback about our name: someone's concerns on sharing (sh.itjust.works)
submitted 2 weeks ago* (last edited 2 weeks ago) by brbposting@sh.itjust.works to c/main@sh.itjust.works
136 comments fedilink hide all child comments
 

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 comment's thread
view the rest of the comments
[–] brbposting@sh.itjust.works 4 points 2 weeks ago (1 children)

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

[–] InEnduringGrowStrong@sh.itjust.works 4 points 2 weeks ago

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.