Choose a domain name #1

Closed
opened 2023-06-24 10:10:15 +00:00 by scott · 10 comments
Owner

What should the domain name of the primary web site which we present to potential clients be?

What should the domain name of the primary web site which we present to potential clients be?
scott added this to the Incorporation project 2023-06-24 10:10:15 +00:00
Author
Owner

My only two ideas are less than ideal due to being expensive domains

  • syndicate.tech: $162.50 (annually!) on namecheap
  • techworkers.coop: $75 (.coop domains start at this price)

Some obvious alternatives are unavailable:

  • techworkers.com, .io, .co: all reserved already
  • techworkers.org: $1379 (and then $14.98/year)
My only two ideas are less than ideal due to being expensive domains - syndicate.tech: $162.50 (annually!) on namecheap - techworkers.coop: $75 (.coop domains start at this price) Some obvious alternatives are unavailable: - techworkers.com, .io, .co: all reserved already - techworkers.org: $1379 (and then $14.98/year)
Author
Owner

I suppose techworkerssyndicate.{com,org,net} are cheap and we could just start with that. But it's long and clumsy and hard to read. I guess that would be good because it's obvious, and we could add another domain like tws.gay (cheap, funny) or tws.sc (short for shortcut; $90/year 😬) as a link shortener

I suppose techworkerssyndicate.{com,org,net} are cheap and we could just start with that. But it's long and clumsy and hard to read. I guess that would be good because it's obvious, and we could add another domain like tws.gay (cheap, funny) or tws.sc (short for shortcut; $90/year 😬) as a link shortener
Member

Just a couple of Q's for clarification sake because this is new and all.
What are your thoughts on a domain regarding internal and client use?

  1. Are you thinking of two different domains? One for the client and one for the use of the workers? This is how my business is set up. .com for public facing and .net for everything for my eyes only, all behind tailscale.
  2. Is tams.tech just a place holder?
  3. One domain to rule them all?
Just a couple of Q's for clarification sake because this is new and all. What are your thoughts on a domain regarding internal and client use? 1. Are you thinking of two different domains? One for the client and one for the use of the workers? This is how my business is set up. `.com` for public facing and `.net` for everything for my eyes only, all behind tailscale. 2. Is tams.tech just a place holder? 3. One domain to rule them all?
Member

I found, workerssyndicate.tech $9.97/yr with Retail $45.98/yr.

I personally am liking the syndicate but don't like the double ss in the url.

I found, `workerssyndicate.tech` $9.97/yr with Retail $45.98/yr. I personally am liking the syndicate but don't like the double ss in the url.
Author
Owner
  1. I hadn't considered that. I just was thinking that "techworkerssyndicate.com" is rather long and it would be nice to have a short url for social shares with a URL that long. just as a mirror
  2. yes. it's just what I use for personal stuff, and I'm hoping to migrate away from it eventually
  3. eh?

yes the double-s is unfortunate, would be nice to avoid it.

1. I hadn't considered that. I just was thinking that "techworkerssyndicate.com" is rather long and it would be nice to have a short url for social shares with a URL that long. just as a mirror 2. yes. it's just what I use for personal stuff, and I'm hoping to migrate away from it eventually 3. eh? yes the double-s is unfortunate, would be nice to avoid it.
Member

I think techworkers gets the point across. You don't have to have LLC, INC or what not In the domain. Plus that shortens it fairly nicely.

Regarding 3, take Vaultwarden for example. Do you want internal passwords and customer passwords under the same instance?
For my business I have been thinking of offering Vaultwarden as a service but don't want them to be on the same instance as my internal Vaultwarden (vault.domain.net). I'd rather have my personal data and client data separate from each other. Plus I feel more comfortable with my stuff behind tailscale.

My 2 cents. Just trying to get a bigger picture of what you are thinking.

I think techworkers gets the point across. You don't have to have LLC, INC or what not In the domain. Plus that shortens it fairly nicely. Regarding 3, take Vaultwarden for example. Do you want internal passwords and customer passwords under the same instance? For my business I have been thinking of offering Vaultwarden as a service but don't want them to be on the same instance as my internal Vaultwarden (vault.domain.net). I'd rather have my personal data and client data separate from each other. Plus I feel more comfortable with my stuff behind tailscale. My 2 cents. Just trying to get a bigger picture of what you are thinking.
Author
Owner

I think techworkers gets the point across.

techworkers.com is registered (for 25 years!) and techworkers.org is $$

image

take Vaultwarden for example...don't want them to be on the same instance

We can use subdomains to differentiate different services, i don't see why that requires 2 domains. Not that I'm against 2 domains, just pointing it out on a technical level.

Vaultwarden is also a whole other discussion, partially because of how we'll manage access to secrets in general and partially because their client apps don't make it easy to have vaults on multiple instances, since they're largely just focused on their own service and vaultwarden just kinda hijacks that. Really the security model with bitwarden as far as I understand is that your vault is e2ee with your password + KDF.

Tailscale/wireguard/nebula is also another discussion worth having separately.

> I think techworkers gets the point across. techworkers.com is registered (for 25 years!) and techworkers.org is $$$$ ![image](/attachments/2314efdc-8066-4dd5-8f4d-1c8c9b10efbe) > take Vaultwarden for example...don't want them to be on the same instance We can use subdomains to differentiate different services, i don't see why that requires 2 domains. Not that I'm against 2 domains, just pointing it out on a technical level. Vaultwarden is also a whole other discussion, partially because of how we'll manage access to secrets in general and partially because their client apps don't make it easy to have vaults on multiple instances, since they're largely just focused on their own service and vaultwarden just kinda hijacks that. Really the security model with bitwarden as far as I understand is that your vault is e2ee with your password + KDF. Tailscale/wireguard/nebula is also another discussion worth having separately.
Member

techworkers.com is registered (for 25 years!) and techworkers.org is $$

image

Yeah I saw that. A beefy initial price but $15/yr after might be worth the investment if everything pays off at the end.

> techworkers.com is registered (for 25 years!) and techworkers.org is $$$$ > > ![image](/attachments/2314efdc-8066-4dd5-8f4d-1c8c9b10efbe) Yeah I saw that. A beefy initial price but $15/yr after might be worth the investment if everything pays off at the end.
Author
Owner

I mean, at that rate, I'd personally rather the prestige of the .coop domain, since that TLD is only available to cooperatives. It would be over 20 years before paying $75/year would cost more than the up-front of the .org. That would also mean, however, that we couldn't get the domain until we have the legal entity.

I mean, at that rate, I'd personally rather the prestige of the .coop domain, since that TLD is only available to cooperatives. It would be over 20 years before paying $75/year would cost more than the up-front of the .org. That would also mean, however, that we couldn't get the domain until we have the legal entity.
Author
Owner

techwork.zone purchased today

techwork.zone purchased today
scott closed this issue 2023-09-26 20:49:32 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TWS/meta#1
No description provided.