pouët.net

I talked to scamp about that a few days ago, in theory all ftp://ftp.untergrund.net urls have a https://ftp.untergrund.net equivalent as well, so I might look into a conversion

There is always some middle aged edgelord who has to necropost on prods with toxic titles in the name of free speech. I propose problematic prods be hidden from last comments in order to reduce the drama on Pouët.

I propose getting rid of edgelord behaviour in the scene - much better gains.

Toxic, problematic people should be deplatformed, quickly and rigorously. This could be decided by a committee.

Gargaj: That is so true. I just wish I could download some zen mindset somewhere.

bifat: *drumroll*

I'm willing to get elected into this committee. Just ask. ;-)

Hi,

Can you rename the category: "TRS-80/Coco" to "TRS-80/Coco/Dragon" ?

Thanks,
f.

Would it be possible to add some UTF-8 support to the results.txt and NFO readers? It works just fine in the HTML view, but the DOS font interprets everything as cp437, and the Amiga font interprets everything as Amiga-1251 or even ISO-8859-1, resulting in the usual UTF-8 mojibake. This really hurts NFOs which are encoded as UTF-8, but are intended to be viewed with a Topaz-like font, like this year's Deadline results.

My proposal would be: If the file isn't valid UTF-8, assume it's already in the native DOS or Amiga charset and convert it to UTF-8 for viewing, as it's done now. If the file is valid UTF-8, though, keep it as-is, or ideally replace the characters which are not available in the font by something reasonable (as we can't count on the browser's replacement glyph having the correct width).

Sure, that kind of UTF-8 check is not bullet-proof, but the chances that any real-world ASCII art accidentally decodes into proper UTF-8 seem to be extremely slim. (A single repetition of a block drawing character in cp437 would already make it invalid UTF-8.)

Am I making sense? And if so, is this feasible?

That's what we're doing already - except "If the file isn't valid UTF-8" is an impossible task.

Why is that? You only need to check if there are no invalid UTF-8 sequences anywhere. There's even a function for that in PHP; should be a three-line fix.

Making an NFO file that is meant to be viewed with Topaz and encoding it as UTF-8 is just a terrible idea. Nobody is going to view that file with Topaz, because systems that can read UTF-8 generally doesn't have Topaz installed.

This sounds like faux old school masturbation of the worst kind to me. Let's not try to enable more of it, especially not when it might break legitimate NFO files.

I agree, it sounds like a horrible idea.

I also browsed through the PHP code that Gargaj linked and was delighted to discover that I'm there :D

I love finding old results.txt files that have a cp437 block art header and the actual results in some other encoding entirely, because they perfectly preserve a moment in time when someone went "oh, our graphician has sent us an ANSI? cool cool. Looks like a bunch of ååååååååÚÚÚÚÚÚÚÚ to me, but whatever, let me just paste that into this notepad doc now"

While doing "edit" and "change prod info", and putting, in this case, a CSDB prod-number, I got this error:

Warning: Undefined array key "releaseDate" in /srv/hosted/pouet/sites/www.pouet.net/include_pouet/request-classes-prod.inc.php on line 851

When i select a group or an user (in the credits section) i'd like a link to be displayed beside the "(click to change)" text so i can verify if this is the right choice (when there are several ones).

Also adding a link beside "party year" to the current year (like "(this month)" for the release date would be handy.

Thanks in advance.