Live data from Hacker News

Winamp source code leak

web.archive.org

211–220 of 338 posts

Re: Winamp source code leak

#212
post #55

Honest question, as someone who actually used Winamp back in ~2004: why would you want to use it now? I have some nostalgia for it, sure, but what exactly does it actually offer you that something like VLC doesn't? It seems like it plays my music and videos competently enough, and I don't know anyone who actually uses Shoutcast anymore. This isn't a passive aggressive dig or anything, I would actually like to know.

VLC doesn't have gapless audio playback.

Re: Winamp source code leak

#213
post #120

I just can’t understand the point of the DMCA takedown here. This software is very dead and abandoned at this point, and the only thing bearing its name is vaporware that appears to be so distant from the original as to effectively not even compete with it. Of course, the copyright holders have every legal right to do so. But doesn’t it seem pointless? This codebase probably has more historical interest than commerci…

How do we know the DMCA takedown even came from the rightsholder? It's trivial to pretend to own something, and companies aren't really obligated to verify the authenticity of takedown requests.

Well, it’s impossible to be 100% certain, but the claim itself was posted publicly.

https://github.com/github/dmca/blob/master/2021/07/2021-07-0...

Re: Winamp source code leak

#214
post #118

Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…

XMMS was a really nice Winamp clone for Linux way back when. Might be a good starting point. http://www.xmms.org/

Audacious.

Re: Winamp source code leak

#215

Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…

My memory is fuzzy on this but didn’t most consider Winamp 2.x the best. Winamp 3.x was considered bloated. So to help rectify the problems of 3.x, Winamp release version 5.x (the best of 2 + 3). Though I recall many still used version 2.x even after the 5.x release. Question: so when you say folks are trying to keep the "last version" alive, which version are you referring too since later versions weren’t loved.

Winamp is highly modular. Most functionality is in plugins, and you could only install the plugins you want. For example you could exclude the media library, modern skins, and video playback. So, 5.x doesn't have to be bloated.

Re: Winamp source code leak

#216
post #55

Honest question, as someone who actually used Winamp back in ~2004: why would you want to use it now? I have some nostalgia for it, sure, but what exactly does it actually offer you that something like VLC doesn't? It seems like it plays my music and videos competently enough, and I don't know anyone who actually uses Shoutcast anymore. This isn't a passive aggressive dig or anything, I would actually like to know.

It's small, does the job I need, it can be made to look good, and extended via plugins. What else do I need? VLC seems like overkill for music.

Re: Winamp source code leak

#217
post #198

Earlier quoted context omitted.

>> see no reason to update You will when you get a 4k monitor.

Winamp has a built-in function to double the pixels, so it's actually quite usable on 4K as-is.

It only works for the main window. The library window doesn't work with it.

Re: Winamp source code leak

#218

Interestingly enough, there has been a community project dedicated to keeping the last Winamp version alive (last version from the original creators), and it really great to use. https://getwacup.com/ It includes a skin that allows it to work on modern display resolutions. It's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor. Edi…

> I's really interesting to see just how low-res screens were when it was in it's hey-day, given that they are nearly unusable on a 4k monitor.

This reminds me of the realization that modern MacOS apps can have icon sizes larger than the original Mac's screen- 512x512 icons vs. 512x384 monochrome screen.

Re: Winamp source code leak

#219

I'm afraid that, at one point in time, a DMCA takedown might backfire at the archive. I mean, it has been taken down on Github, but it's of course available at archive.org - it would hurt the internet as a whole if the archive needs to close it's doors. Hopefully that will never happen.

I'm not 100% sure of all the details, but archive.org has some exceptions[1] to the DMCA & thanks to California, it's officially considered a library - which again, I believe gives it some more leeway on the DMCA. [1]: https://archive.org/about/dmca.php

In the event a DMCA notice must be actioned, the content is no longer made available ("darked") but it remains archived for the future.

Re: Winamp source code leak

#220

Earlier quoted context omitted.

Wow, that's a first. Clicking the URL hung Brave, completely unresponsive for 2-3 mins, now it's loaded but shows nothing but a dark blue background. Same for every refresh, too!

This is my pet peeve. Browsers should not allow any websites to hijack all computing cycles. This was already clear a few years ago during the Monero hype. The fact that most adblockers will detect such attempts today doesn't change the fact that any website can almost prevent you from doing other work just because you opened it. The current strategy of dealing with this problem ("this tab has become unresponsive") i…

NoScript does this.
Post reply on HN