Live data from Hacker News

The 88x31 GIF Collection

cyber.dabamos.de

21–30 of 49 posts

Re: The 88x31 GIF Collection

#22
post #4

The 'Best viewed with Internet Explorer'[0] GIF triggers severe nostalgia. IE was the dominant browser at the time, and these propaganda buttons just reinforced the idea that IE was the only browser you should be using. Still see the odd site saying 'Works best in Chrome' as if Chrome was the new IE. Personally though, if your site is one of those annoying SPA (Single Page Apps) and doesn't work in Lynx[1], you're do…

The Netscape banners do it for me, as the time when Netscape was dominant was a great time for me. The internet was a huge vault for me, and every time I dialed in I felt that rush. Every minute counted because we paid by the minute.

Netscape is also Mozilla's spiritual father.

Lynx didn't have JS support. Which was a blessing and a curse.

Re: The 88x31 GIF Collection

#23
post #13

Earlier quoted context omitted.

But why did Geocities use the 88×31 format? https://neonaut.neocities.org/cyber/88x31 (link warning: lots of 88×31 GIFs!) says it's likely because the "Netscape Now!" button was of that size.

But why was the Netscape Now button that size? We must go deeper

At the bottom of the stack, the answer is probably either "it fit perfectly in an 88x31 space between some other things on the first page it was used on" or "I drew a rectangle that looked right and didn't bother rounding the numbers".

Re: The 88x31 GIF Collection

#24
post #15

Earlier quoted context omitted.

Big blast of nostalgia from that Japanese pagoda image at the top. It originated as a Commodore 64 320x200 image. Note how there are no color changes between 8x8 pixel blocks. I forget the artist's first name, but I believe his last name was Sachs. He was a huge deal in 64 art in the 80's, and later transitioned to Amiga. I think he did a fish tank screen saver, and I seem to recall a video game on the 64 where you f…

Did you mean ZX Spectrum? Because C64 didn't have any trouble showing multiple colors in 8x8 blocks.

C64 didn't have any trouble showing multiple colors in 8x8 blocks.

In high resolution mode it did, which is the 320x200. You could only have a single foreground color and a background color.

In the low resolution 160x200 mode you could have one background color and three foreground colors in a 4x8 square.

I was a computer artist back then, published in several Commodore magazines, and the first thing I had to decide when painting a scene was if I could get away with the 320x200 mode, or settle for 160x200 because I needed more colors closer together.

Re: The 88x31 GIF Collection

#27

Ugh stop it HN, I can only handle so much nostalgia! FYI, in Japan there's a sunset of websites that are meant for a Japanese only audience and the pages are still designed in 'ol faithful web 1.0 designs.

That's interesting, I recently had a discussion about how Japan has a bit of a tendency to hang on to fashion for much longer, but applied to music. Like certain styles of metal being popular after decline in the west, 90s Animes with soundtracks that sounded like 80s AOR/R&B, or even 80s-pointy-guitars being used by Japanese indie bands.

And not in a bad way, but more in a "fashion isn't as fleeting in Japan". Also it seems that the new and the old are able to coexist in the mainstream there, more than in the West. But that's of course just an impression, I might be wrong.

Re: The 88x31 GIF Collection

#29
post #13

Earlier quoted context omitted.

But why did Geocities use the 88×31 format? https://neonaut.neocities.org/cyber/88x31 (link warning: lots of 88×31 GIFs!) says it's likely because the "Netscape Now!" button was of that size.

But why was the Netscape Now button that size? We must go deeper

As it turns out, if you put two horses side by side...

Re: The 88x31 GIF Collection

#30

> 1011 requests | 9.3 MB transferred | 9.1 MB resources I was going to warn about this, but then I realized that's probably not even half of the average modern web page size =)

Clearly this was the killer app QUIC needed to solve.

If they would just update the server to support HTTP2, it would be 99% there. Living far away from the server I could instantly tell that it was using HTTP/1.1, which was confirmed by looking at the dev tools.
Post reply on HN