Scene.org server maintenance
category: general [glöplog]
Today we are starting some major server maintenance which will result in the main scene.org file archive being unavailable for a good part of the day, please use one of our mirrors in the meantime, like for example ftp.no.scene.org.
The website is back already, the archive will be back in the next hour or so.
FWIW www.scene.org seems to work fine here, scene.org doesn't. Even after flushing DNS cache, they seem to point at different IPs. Intentional?
We're doing on the shuffle on the name servers; this also means that "ftp://scene.org" will no longer work, the correct URL will be (and always has been) ftp://ftp.scene.org.
Update: services are back up, but the archive is still syncing back to our fileserver. This will take a few more hours, until then the archive is available for downloads but it is incomplete.
Redhound: thanks for your awesome work in keeping scene.org alive and kicking.
This weekend we're hoping to transition the file browser section of the current Scene.org website over to http://files.scene.org - it looks pretty much the same, just with cleaner code and some upgrades like semantic URLs which will hopefully make a lot of things easier.
This may cause some fuckups on the Pouet/scene.org side, so please be patient.
This may cause some fuckups on the Pouet/scene.org side, so please be patient.
No doubt, Gargaj're sort it out!
Will the download counters work proper again?
Okay, all scene.org file links have been replaced with the new files.scene.org link scheme, should be nice and comfy; if there's something wrong, you know where to find us.
Quote:
Okay, all scene.org file links have been replaced with the new files.scene.org link scheme, should be nice and comfy; if there's something wrong, you know where to find us.
https://files.scene.org/browse/music/artists/netpoet/
broken umlauts in filename display + link
For that matter, opening such files manually, using a proper utf-8-encoded URL (what browsers automatically do nowadays if you type an umlaut into the address bar) does not work (404 - page not found) either. Even worse, encoding the URL in latin1 manually leads to what looks like a server error (connection reset).
Those files will get renamed into something non-wonked.
Ah, following the latest official internet standard, are we? ;)
Oh ,forgot to mention that I meant "utf-8 percent-encoded" resp. "latin1 percent-encoded", as follows:
https://files.scene.org/view/music/artists/netpoet/netpoet_-_herzk%c3%b6niglich_du.mp3
https://files.scene.org/view/music/artists/netpoet/netpoet_-_herzk%f6niglich_du.mp3
https://files.scene.org/view/music/artists/netpoet/netpoet_-_herzk%c3%b6niglich_du.mp3
https://files.scene.org/view/music/artists/netpoet/netpoet_-_herzk%f6niglich_du.mp3
(without the spaces pouet sneaked into those URLs of course)