[0x0] 0x0.st down 404, patches unavailable

[1480c1]

Process 29842 stopped
* thread #1: tid = 29842, 0x00007fbec95714e0, name = 'fhost'
    frame #0:
Process 29842 stopped
* thread #8: tid = 29842, 0x00007fbeab7d1840 fhost`get(path='/sgwa.txt') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30)
    frame #0: 0x00007fbeab7d1840 fhost`get(path='/sgwa.txt') + 27 at fhost.c:139
   136   get(SrvContext *ctx, const char *path)
   137   {
   138       StoredObj *obj = ctx->store->query(shurl_debase(path));
-> 139       switch (obj->type) {
   140           case ObjTypeFile:
   141               ctx->serve_file_id(obj->id);
   142               break;
(lldb) q

It seems that 0x0.st is down for downloading patches, base index.html works fine

Don't open another issue dealing with patches until 0x0.st is working

[wiiaboo]

I think it's working now?

[1480c1]

Hmmm, it seems that based on 0x0 repo, that message is send whenever a 404 is raised, so most of the patches are available, but

• https://0x0.st/sgwa.txt [Opusfile]
• https://0x0.st/sgEY.txt [ffms2]
  are unavailable

[wiiaboo]

Maybe they're too old then.

[wiiaboo]

We should probably stop using 0x0 for long-lasting patches.

[wiiaboo]

I think the opusfile patch was xiph/opusfile#13 (comment)

[wiiaboo]

And ffms2 patch is a rebased version of https://github.com/m-ab-s/media-autobuild_suite/blob/gh-pages/patches/0001-ffmsindex-fix-linking-issues.patch

[Kogarou-san]

Why not just use github Gist for long-lasting patches?

[maolang]

Anyway to bypass the ffms2 hit through a config setting, Opus one seems possible to be easy by just adding --disablle-opus

https://0x0.st/sgwa.txt [Opusfile]
https://0x0.st/sgEY.txt [ffms2]

[1480c1]

transferred over the two patches mentioned here, might also move some of the other non-temporary patches too