@Dennis Out of curiosity, why did you publish TIO v2 using a specific GitHub account, instead of your account (like you did for TIO v1)?

It's an organization not an individual account

Yes. Currently two people are part of it. github.com/orgs/TryItOnline/people

Oh, I see. I'm not very much familiar with GitHub organizations

Even if I'm part of one or two, I think :-)

we got a snippetify library for JS

and now I question ourselves:

'Do we need TIO:Stack Snippets ed.?"

@SIGSEGV At this point, I wouldn't bother. The API might change any day, rendering your Stack Snippets unusable.

Huh. Okay then.

@Downgoat Are you ignoring me on purpose? :P

Not that I know of >_>

I mean, it's up to you when/if you fix that, but I wanted to make sure you know.

@Dennis Would output streaming be realistic to implement?

Wait what oh no

Hm, I get a "409" error

@Downgoat @DownWat Yes, as I told you earlier, you have to append /api/ or the current version token to the URL of the CGI script.

← 7 messages moved from The Nineteenth Byte

so https://tio.run/cgi-bin/run/api/

Yes.

Appending /api/ also means that the browser will take care of the decompression.

oh D:

I still have to do compression?

hm :/ https://tio.run/cgi-bin/run/api also results in the 409

https://tio.run/cgi-bin/run/api/ != https://tio.run/cgi-bin/run/api

I did trailing / but safari must be killing it >_>

@Downgoat For the request? Yes. I tried looking at your code, but I can't find it.

nvm found workaround