@derek I don’t think I can. I can set up custom CSS and custom Java script but I don’t have any back end access.
@danielmrose - if you're interested in trying it out, I'd love to work with you on it. No charge till we get it working and that will help our future clients in similar situation! I've been looking for a volunteer to break the need for the .well-known thing for a while. Holler if you like!
@danielmrose By chance do you have the ability to set a DNS redirect (not a CNAME) at your domain provider?
@derek Maybe? My domain provider is Wordpress. Let me do a google-fu
@danielmrose OOOOooooo - so, funny story - Wordpress has built in mastodon compatibility now. Are you familiar with that solution and would it meet your needs?
@derek So my domains are hosted by Wordpress.com.
But my blog is hosted on Write.as. So I don’t actually use Wordpress.
I moved my domains there after Google sold out to Squarespace because Wordpress was offering an extra year for free.
Does that make sense?
@danielmrose Ahhh - yes, that makes good sense. Fingers crossed they have some sort of redirect option!
@derek This is what I can set.
There is an option to forward the domain but I would have to reset my A records which, I think would break my website. 🤔
But this is slightly above my pay grade 😂
@danielmrose Yeah, those are pretty standard items, but unfortunately not quite what we’re looking for. Perhaps write.as has a feature to override the .well-known endpoints? I suspect not since write.as is ALSO a fediverse endpoint.
@danielmrose - want to continue tinkering with it, or should I go ahead and disable? I wish there were a better mechansim for searches. Granted, the only "blocker" here is when people search you by name - (user)(at)(domain.com). The rest of the ecosystem works fine, ie, people can follow you, they just will see your service domain in your username instead of your domain. :(
@derek let’s go ahead and disable. Thanks for giving it a go! I really appreciate it.