Hacker Newsnew | past | comments | ask | show | jobs | submit | whyfy's commentslogin

https://github.com/jberg/butterchurn This is the visualizer that they're using.


someone (podiki) submitted butternchurn to hn[1].

this is 50% of the winamp2 experience. glad to see it again.

[1] https://news.ycombinator.com/item?id=26813265


Meanwhile, nano doesn't get that treatment


"Video unavailable This video is no longer available due to a copyright claim by Microsoft Corporation."


Ran the site through GTMetrix https://gtmetrix.com/reports/peteris.rocks/5gIfn1Ef It's like ad central, sadly.


In addition, eating foods that contain zinc makes this point moot. Meat, shellfish, nuts, even dairy


And Spotify can control their service how they please, next.


As a point of fact, they cannot, because their goal with "controlling their service" is to control what is displayed on someone else's personal property as a condition of listening to the free data stream they decided to emit.. and so Spotify (or anyone else) is not capable of making that a reality.

They could change their service to try to block users who protect their personal property from having certain harmful pieces of information (like ads) mixed in with otherwise freely available data sources. But it would just be a silly failure, since lots of people already circumvent that type of thing easily and legally with technology all the time.

The only thing they could actually do is to entirely shut down their emitted free stream of data all together, both content and ads alike. Of course they are free to do that if they want. Nobody suggested they have to emit a free stream of data.. only that if they choose to then people will just keep consuming it without allowing ads to appear, and the ads will keep being legally and successfully blocked regardless of any type of ban that Spotify tries to implement.


I haven't found actual specifics, but a quick search on Google Patents reveal that Qualcomm has a similar one for the image control/resizing. https://patents.google.com/patent/US20140306903A1/en?q=appli...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: