News for hackers. Stuff that matters.
Re:Winamp source code leak by cyber_kinetist on Monday November 29, 2021 @09:35AM (#29380299)
For context, here's the new revamped(!) Winamp coming up soon: https://www.winamp.com/

It's just... the complete opposite of what Winamp was all about, and it's horrible and leaves a bad taste in your mouth (-100 points for the atrocious "modern" website which loads MBs of Javascript, screams BIG TEXT at you, hijacks your scroll wheel, and still tells you nothing about the actual software other than it will probably suck. Oh and another -100 points for that cookie popup.)

Re:Winamp source code leak by firekvz on Monday November 29, 2021 @09:44AM (#29380410)
The browser on my pixel 6 crashed, haven't seen a site lag a phone for like 2 years
Re:Winamp source code leak by cyber_kinetist on Monday November 29, 2021 @09:46AM (#29380439)
Yeah, the site also freezes my Firefox for 5 seconds, and this is from a gaming PC. Absolutely horrendous...

How hard you would actually have to try to make a website as horrible as this, this thing is just a meme.

Re:Winamp source code leak by sli on Monday November 29, 2021 @10:18AM (#29380801)
For all that lag, I was expecting a lot more than some simple animations. And that scrolljacking is by far the worst I've ever experienced. I have to scroll three times to switch to the next section. Can't even manually drag the little scrollspy thing. Atrocious.
Re:Winamp source code leak by cjnicholls on Monday November 29, 2021 @10:49AM (#29381172)
Here’s the developer https://www.laniche.com . Their other websites don’t seem to be as laggy but there is a theme of animating *every* element and embedding videos.
Re:Winamp source code leak by andai on Monday November 29, 2021 @11:41AM (#29381903)
Holy shit, you weren't kidding! What the heck is this thing doing, mining bitcoins? How did this ever get approved?
Re:Winamp source code leak by mderazon on Monday November 29, 2021 @11:12AM (#29381503)
Came to write this as well
Re:Winamp source code leak by kingsloi on Monday November 29, 2021 @09:43AM (#29380390)
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!
Re:Winamp source code leak by hdjjhhvvhga on Monday November 29, 2021 @09:53AM (#29380513)
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") is inadequate because it is reactive, not proactive. I'd like to be able to blacklist everything and whitelist only chosen websites I trust. Loading for too long because of tracking code? Too bad, choose another loading strategy or I just close the tab. Making my fans spin faster? Begone.
Re:Winamp source code leak by eitland on Monday November 29, 2021 @10:19AM (#29380816)
There is another thread going on about bringing back web 1, but here is something I have been advocating for a while, make 2 different new web profiles, along the lines of:

1.) A subset of modern HTML / CSS, custom Javascript. Remove anything that isn't needed and especially anything that affects rendering negatively for no good reason.

1.1.) Possibly: Provide versioned, vendor neutral versions of js to allow for autocomplete.

2.) Same as 1, but with custom JS. All js must complete in a specified number of cycles. User interaction gives extra cycles.

The point of 1 is to:

- for companies: massively lower the barriers for new browsers (remove lots of backwards compatibility and the huge problem of JS)

- for security conscious users: provide a safer way to browse the web

- for users generally: provide a way to browse the web faster and more comfortably

- the point of 2.) is to provide an approximation of what we have today but in a way that automatically limits developers from abusing JS.

Re:Winamp source code leak by lproven on Monday November 29, 2021 @10:59AM (#29381331)
Sounds good, but I'd move for the total removal and banning of all JS and other scripting.

Otherwise, what's the point?

Re:Winamp source code leak by Zandikar on Tuesday November 30, 2021 @01:25AM (#29389525)
I've actually taken to using a Javascript toggle extension that defaults to off. Makes the web a far better experience when it comes to venturing into unfamiliar territory (going to a site you haven't been to in a while, if it all, or following some shortened url that leads who knows where, or just clicking through something on a news aggregator for example). And if it breaks the website? 9 times out of 10 that's your "It's not worth it" signal to just close the tab and move on. If they can't even deprecate gracefully, they almost never use javascript competently and unobtrusively.
Re:Winamp source code leak by Kiro on Monday November 29, 2021 @11:09AM (#29381444)
What about actual apps or games where you want to push the limits?
Re:Winamp source code leak by eitland on Monday November 29, 2021 @11:15AM (#29381537)
For that we already have html5 and Firefox :-) (and Chrome and what not)
Re:Winamp source code leak by kevin_thibedeau on Monday November 29, 2021 @02:05PM (#29383785)
NoScript does this.
Re:Winamp source code leak by hdjjhhvvhga on Tuesday November 30, 2021 @05:57PM (#29398512)
My point is, I'd like to give some basic cycles to unknown websites. The NoScript solution is good but radical. If you visit new websites often, you spend some time clicking "temp trusted." In my scenario, websites do have some power, but not much. They should never be allowed to make my fan turn faster - unless I allow it. I don't believe this can be done at the plugin/extension level.
Re:Winamp source code leak by stavros on Monday November 29, 2021 @10:12AM (#29380742)
Winamp (winamp)

It really whips your browser's ass.

Re:Winamp source code leak by theandrewbailey on Monday November 29, 2021 @10:39AM (#29381041)
My brain automatically read that in that guy's voice from DEMO.MP3, complete with the bleating.
Re:Winamp source code leak by andrew_ on Monday November 29, 2021 @10:49AM (#29381176)
LOL same. It's absolutely wild how that's an automatic response.
Re:Winamp source code leak by stavros on Monday November 29, 2021 @10:49AM (#29381174)
As it should!
Re:Winamp source code leak by Nition on Monday November 29, 2021 @02:30PM (#29384097)
Funnily enough, despite that brand new absolute mess of a website, the ancient original Winamp Forums are still running: http://forums.winamp.com/
Re:Winamp source code leak by robertlagrant on Monday November 29, 2021 @10:44AM (#29381105)
> We’re building Winamp for the next-generation.

The incorrect hyphen is just irritating as well.

Re:Winamp source code leak by jmknoll on Monday November 29, 2021 @11:59AM (#29382134)
At the bottom of their site, they have about 30 open full time positions, including Sales, Legal, and Finance. Seems strange for a 25 year old media player. Did they just close a big funding round or something?
Re:Winamp source code leak by WorldMaker on Monday November 29, 2021 @03:44PM (#29385030)
I don't recall the full tumultuous journey, but highlights I recall were Nullsoft (original Winamp creators) towards the end were bought by AOL who did them dirty and then AOL forgot about Winamp as a property entirely for something like two decades through the Time Warner merger then divorce then the Yahoo! merger into "Oath" under Verizon. At some point in spinning Oath back out of Verizon and putting Oath's IP on the chopping block someone found Winamp in an old closet somewhere and sold the "brand" to whoever this new company is that so far as any can tell has zero relationship to the original Nullsoft in any capacity.
Re:Winamp source code leak by thedoctor_o on Monday November 29, 2021 @04:41PM (#29385642)
The pure Nullsoft Winamp was from 1997 to mid-1999 with AOL having Winamp under it's ownership until 2013 (technically until mid-January 2014) when it was sold to Radionomy (who then were bought by Vivendi but then bought themselves back under the guise of Audiovalley).

So that time with AOL covers v2.5 when it became free after starting out as shareware through to v5.666 along with the maligned WinAmp3 period. So that's whole a lot of not doing much but still producing releases for almost 15yrs. Winamp (& SHOUTcast) were sold before Verizon did it's thing with AOL.

-dro

Re:Winamp source code leak by pongo1231 on Monday November 29, 2021 @10:02AM (#29380623)
Interestingly in contrast to the others it loads up fine on both my laptop and my S9 with Firefox, even after disabling my adblocker and unblocking all scripts in NoScript.
Re:Winamp source code leak by caslon on Monday November 29, 2021 @07:31PM (#29387265)
Another one who it worked completely fine for. Zero issue here. Firefox on X11.
Re:Winamp source code leak by isk517 on Monday November 29, 2021 @12:47PM (#29382773)
Add me the the list of people who thought you were exaggerating about how bad the website was and then immediately noticed how it made my browser stutter.
Re:Winamp source code leak by ttyyzz on Monday November 29, 2021 @09:44AM (#29380403)
The page is a performance nightmare on my mobile phone (pixel 4a), unusable.
Re:Winamp source code leak by sen on Monday November 29, 2021 @06:21PM (#29386685)
Not only froze my entire browser (ALL firefox tabs, including youtube playing in another window), but it locked up my entire system for a few seconds, I couldn't alt-tab or anything.

That's... almost impressive in how bad that is. I didn't know a website COULD lock up an entire system in this day and age.

Re:Winamp source code leak by denton-scratch on Monday November 29, 2021 @01:03PM (#29382963)
That site's unusable; I see [Decline][Accept] buttons, with no explnation of what I'm being invited to decline or accept. No choice but to close the tab.
Re:Winamp source code leak by Flockster on Monday November 29, 2021 @09:47AM (#29380448)
Wow, it made my Firefox stuck for a few seconds, opening it in a new tab. (So it wasn't viewable while loading).
Re:Winamp source code leak by lostgame on Monday November 29, 2021 @02:20PM (#29383981)
In the Spotify/Apple Music, etc; era - wtf is the selling point on this?
Re:Winamp source code leak by alx__ on Monday November 29, 2021 @05:34PM (#29386176)
Looks like they copped the design styles from Sonos. Which is already meh