The Glowfic Constellation
Re: The Glowfic Constellation
I couldn't log in but Throne helped me and now I can. :D
Re: The Glowfic Constellation
Yeeeeeah it's possible I'm gonna have to make everyone reconfirm their passwords, otherwise you'll have to change your password whenever you change your username because I was a dumb.
It was my mom's birthday weeks ago, actually, but I've been out of town and so has she, this was the first day that worked. However, when you halve a recipe, you need to ACTUALLY REMEMBER TO HALVE THINGS, so my extremely-eggy cake may need to be redone :/ this is why I start early I guess...
Redirecting between root and www, or redirecting vast-journey, or both? 100% will eventually redirect vast-journey; less clear on base/www. I'm aware the two CNAMEs shouldn't be working even if somehow they are, and I suspect long term I'll have to use www. instead of root because of exactly that issue, but I'm not sure how the email issues will work since I'm not currently using @glowfic.com for emails. (Which like, longterm I probably should? But these seem like problems for Future Marri.)
Namecheap was cheaper and included free privacy? It's possibly not clear just how very much I don't know how this works, and exhausted stubbornness is pretty much the only reason it's even kind of working. The SSL certificate does 100% support both www.glowfic.com and glowfic.com, though, that was the entire reason I went with DNSimple/Comodo. (Plus it has a Heroku integration and is actually pretty cheap and so forth, but most places make you pick www. or @. and I didn't want to).
Probably other things, but gotta go deal with the egg emergency.
It was my mom's birthday weeks ago, actually, but I've been out of town and so has she, this was the first day that worked. However, when you halve a recipe, you need to ACTUALLY REMEMBER TO HALVE THINGS, so my extremely-eggy cake may need to be redone :/ this is why I start early I guess...
Redirecting between root and www, or redirecting vast-journey, or both? 100% will eventually redirect vast-journey; less clear on base/www. I'm aware the two CNAMEs shouldn't be working even if somehow they are, and I suspect long term I'll have to use www. instead of root because of exactly that issue, but I'm not sure how the email issues will work since I'm not currently using @glowfic.com for emails. (Which like, longterm I probably should? But these seem like problems for Future Marri.)
Namecheap was cheaper and included free privacy? It's possibly not clear just how very much I don't know how this works, and exhausted stubbornness is pretty much the only reason it's even kind of working. The SSL certificate does 100% support both www.glowfic.com and glowfic.com, though, that was the entire reason I went with DNSimple/Comodo. (Plus it has a Heroku integration and is actually pretty cheap and so forth, but most places make you pick www. or @. and I didn't want to).
Probably other things, but gotta go deal with the egg emergency.
Re: The Glowfic Constellation
Kappa: So, www is a thing for Historical Reasons, dating from a time when the Web and the Internet weren’t near-synonyms. Some technical things are still easier if you use subdomains, but usually there are workarounds; PointDNS provides a workaround for the various CNAME issues, for example.
Marri: I suspect things might break a bit with *sending* email too, where some email places are more likely to consider glowfic.com emails spam. I don’t know, though. If you do have a problem with that, I suspect that the CNAME thing might break some potential fixes.
A lot of people say that it’s a bad thing that NameCheap just resells enom, but AFAICT the chances of that actually causing problems are pretty small. The privacy can also in theory become an issue but in practice probably won’t; if there’s a legal dispute the official owner of the domain is WHOISGUARD, INC., not you, but I can’t imagine them actually doing Bad Things with that fact. When I researched registrars a few months ago my favorite was NameSilo, which is also cheaper, but I don’t have enough experience with any of them to know they’re actually better.
A Let’s Encrypt certificate can support subdomains, but it does not have Heroku integration.
Good luck with the eggs.
Marri: I suspect things might break a bit with *sending* email too, where some email places are more likely to consider glowfic.com emails spam. I don’t know, though. If you do have a problem with that, I suspect that the CNAME thing might break some potential fixes.
A lot of people say that it’s a bad thing that NameCheap just resells enom, but AFAICT the chances of that actually causing problems are pretty small. The privacy can also in theory become an issue but in practice probably won’t; if there’s a legal dispute the official owner of the domain is WHOISGUARD, INC., not you, but I can’t imagine them actually doing Bad Things with that fact. When I researched registrars a few months ago my favorite was NameSilo, which is also cheaper, but I don’t have enough experience with any of them to know they’re actually better.
A Let’s Encrypt certificate can support subdomains, but it does not have Heroku integration.
Good luck with the eggs.
-
- Posts: 3554
- Joined: Fri Mar 21, 2014 5:47 pm
- Pronouns: 'He' or 'she', interchangeably
- Location: under a pile of Jokers
- Contact:
Re: The Glowfic Constellation
Hmm. I retract my vague preference and am back to having no preference at all.
Re: The Glowfic Constellation
The bolding on the Unread page is strange and confusing but fortunately I almost always only need the Opened page which does not have it.
Re: The Glowfic Constellation
Made a new cake, correct number of eggs but questionably edible brown sugar; here's hoping.DanielH wrote:Marri: I suspect things might break a bit with *sending* email too, where some email places are more likely to consider glowfic.com emails spam. I don’t know, though. If you do have a problem with that, I suspect that the CNAME thing might break some potential fixes.
A lot of people say that it’s a bad thing that NameCheap just resells enom, but AFAICT the chances of that actually causing problems are pretty small. The privacy can also in theory become an issue but in practice probably won’t; if there’s a legal dispute the official owner of the domain is WHOISGUARD, INC., not you, but I can’t imagine them actually doing Bad Things with that fact. When I researched registrars a few months ago my favorite was NameSilo, which is also cheaper, but I don’t have enough experience with any of them to know they’re actually better.
A Let’s Encrypt certificate can support subdomains, but it does not have Heroku integration.
Good luck with the eggs.
Do you mean that sending email might break *now* because of the CNAME or long term when I start using @glowfic.com addresses? Sounds like the second thing.
I could also have just issued my own certificate for free; a lot of this was getting an Actually Valid certificate.
It looks like Namecheap lets you pick a custom DNS nameserver; are you suggesting I use the free PointDNS nameserver instead of Namecheap's? PointDNS only gives me one domain for free, not sure that covers both root and www. and it's otherwise $15/mo.
Re: The Glowfic Constellation
Fingers crossed about the brown sugar.
Currently your glowfic.com DNS entry has a TXT record saying
Let’s Encrypt is an Actually Valid CA according to a lot of places, and they are signed by IdenTrust which is an Actually Valid CA according to everybody, so they work everywhere. They don’t do extended verification, only domain verification, but that’s all you have now.
I know nothing about PointDNS except what’s been mentioned here; I would guess they could handle those under the same domain and 10 records is probably enough, but I don’t know.
Currently your glowfic.com DNS entry has a TXT record saying
"v=spf1 include:spf.efwd.registrar-servers.com ~all"
. This means basically “Hey, if anybody tries to send an email from an @glowfic.com address and it didn’t originate at our servers, they’re Suspicious.”. If you don’t have a record like that some places might just assume all emails are Suspicious. Currently they might not see that because the CNAME isn’t supposed to exist alongside other records. You should probably also get that record changed anyway because the servers it lists are Namecheap’s, and I doubt you’re sending email from them.Let’s Encrypt is an Actually Valid CA according to a lot of places, and they are signed by IdenTrust which is an Actually Valid CA according to everybody, so they work everywhere. They don’t do extended verification, only domain verification, but that’s all you have now.
I know nothing about PointDNS except what’s been mentioned here; I would guess they could handle those under the same domain and 10 records is probably enough, but I don’t know.
Re: The Glowfic Constellation
hey guys what's going on in this thread
(Totally unrelated question here: what's the character limit on character names? I've been uploading all my characters, but one of the Leos does not so much have a "name" as a 60-word [391-character] title which he is eternally plagued by. I'll probably end up just going with his 3-letter pseudonym, but I'm kind of morbidly curious about how close I could have gotten.)
(Totally unrelated question here: what's the character limit on character names? I've been uploading all my characters, but one of the Leos does not so much have a "name" as a 60-word [391-character] title which he is eternally plagued by. I'll probably end up just going with his 3-letter pseudonym, but I'm kind of morbidly curious about how close I could have gotten.)
Re: The Glowfic Constellation
hiiiiiiiii
Re: The Glowfic Constellation
I don't know of any actual hard-capped limit on character name lengths! It'll display weirdly in threads and mobile users may hate you for it (since it wraps badly on mobile), but I can at least do a 15-word-long name just fine and I can't see any limit in the code. The database could well limit it but if so I don't know what it limits it to.