もしかしてこれcert-managerで証明書発行いけるかな
このアカウントは、notestockで公開設定になっていません。
@nick The error is "Access to XMLHttpRequest at 'https://www.mastodonien.de/api/v1/instance' from origin 'http://localhost:9080' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."
@nick Megalodon is a client library for Mastodon, Pleroma and Misskey. I have been developing, but the name was stolen: https://github.com/h3poteto/megalodon/issues/1466
Perhaps, version field is needed.
https://github.com/h3poteto/megalodon/blob/2db1e37c84c179363935e6d1e41b0ea14a3de713/megalodon/src/megalodon.ts#L1343
@nick That message is generated here: https://github.com/h3poteto/whalebird-desktop/blob/28578e381da54696ee03a4fc91489030e6a52c4b/src/renderer/components/Login/LoginForm.vue#L130
Probably, megalodon can't detect the SNS.
https://github.com/h3poteto/whalebird-desktop/blob/28578e381da54696ee03a4fc91489030e6a52c4b/src/renderer/components/Login/LoginForm.vue#L119
What happens when you call the detector method in megalodon?
https://github.com/h3poteto/megalodon#detect-each-sns
@nick Which server are you using?
And does Whalebird say any errors?
@nick Yes, I'm the developer.
Yes, it is expected behavior. This endpoint does not exist in Mastodon, but it exists in Misskey. Whalebird have to check which SNS are you using, so it cheks Misskey's endpoint. When you are using Mastodon, it fails, but no problem.
SecurityGroupとか手動で作ってたの，ある意味すごいよな．昔はruleにdescriptionもかけなかったので，何が許可されてるかまったくわからなかったぞ
