Closed mrvdb closed 5 years ago
Thanks. Issue fixed.
Should I change the name of this repository to writefreely.el? I'm not associated to either writefreely nor write-as, so I don't know whether it's OK to use these names in the first place.
Wow, quick response. :-)
For the name, best ask @matt@writing.exchange (mastodon account). Personally I'd prefer something with writefreely as that is the version we have code for.
For complete support of other endpoints, I think the function write-as-publication-link
will need to change a bit as well. That seems to be the last hardcoded bit.
Thanks for pointing it out.
After asking Matt, I've renamed the project to writefreely.el.
I cannot test it in other instances, but there are no more hardcoded instances of write.as. Here are the two variables to be configured:
(defcustom writefreely-instance-url "https://write.as"
"URL of the writefreely instance. You may
change the endpoint in case your blog runs in a different
writefreely instance.")
(defcustom writefreely-instance-api-endpoint "https://write.as/api"
"URL of the writefreely API endpoint. You may
change the endpoint in case your blog runs in a different
writefreely instance.")
Cool,thanks.
If you need a test instance, you're welcome to register on qua.name if you want.
Awesome, just did :)
Write.as recently released their source under the name writefreely (see https://writefreely.org for details) so their software will run on more endpoints than https://write.as For example, mine is at https://qua.name
If you make the endpoints into defcustom variables all the writefreely instances can use this package as well.