Standardnotes API broke again

[Mikescher]

It looks like the StandardNotes API no longer works and now returns 504 Method not allowed on the sync request.

According to the StandardNotes team the public API will not be maintained anymore and everyone is forced to use their webapp or mobile apps (or build clients by using their javascript code directly....)

I don't think I can fix it this time, if someone wants he can try to fix the StandadNotes plugin but I'm not really in the mood to play whack-a-mole with their frequent API changes...

I'm almost at the point where I'll just write my own notes-server -.-

---

Edit:

A "temporary" "workaround" is to host StandardNotes on your own server, I'm currently using the following docker tags and it seems to be working:

standardnotes/syncing-server-js:ae56126585a0519f2c5a5c8844aee881cdd56f4d
standardnotes/syncing-server-js:ae56126585a0519f2c5a5c8844aee881cdd56f4d
standardnotes/api-gateway:7980af3d82507ca6990ec9d7fdcdc19003f4f8b8
standardnotes/auth:9ca373e208fb68d1388da677f9246c0a7c1cc122
standardnotes/files:7980af3d82507ca6990ec9d7fdcdc19003f4f8b8
standardnotes/revisions:9ca373e208fb68d1388da677f9246c0a7c1cc122
localstack/localstack:1.3.1
redis:6.0-alpine
mysql:8
mysql:5.6

I don't think I can fix it this time, if someone wants he can try to fix the StandadNotes plugin but I'm not really in the mood to play whack-a-mole with their frequent API changes...

This can be resolved with the tool in C#: puppeteer-sharp, an Headless Chrome .NET API.

var options = new ConnectOptions()
{
    BrowserWSEndpoint = $"wss://www.externalbrowser.io?token={apikey}"
};

var url = "https://app.standardnotes.com/";

using (var browser = await PuppeteerSharp.Puppeteer.ConnectAsync(options))
{
    using (var page = await browser.NewPageAsync())
    {
        await page.GoToAsync(url);
    }
}

[sn3akyb3ar]

Btw, seems like they fixed it for now, at least it syncs for me without any problems.

This can be resolved with the tool in C#: puppeteer-sharp, an Headless Chrome .NET API.

this is a good idea in case the API doesn't work correctly

[Mikescher]

Hello, Is this issue resolved or not?

Afaik its not - as written above I'm currently hosting my own StandardNotes server, pinned on version ae56126585a0519f2c5a5c8844aee881cdd56f4d.

if someone wants he can look at the current API flow and update the StandardNotes plugin, but I'm kinda burned out constantly updating it...

his can be resolved with the tool in C#: puppeteer-sharp, an Headless Chrome .NET API.

I don't think thats a good idea, that would be prone to breaking (even more than the API), and i really don't want to start interacting with the website directly.
if someone wants to implement this, please use the current StandardNotes plugin as a starting point, but copy it into a new plugin (aka standardnotes-pupeteer), and preserve the existing API-based plugin.