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

Well it led to the creation of BOINC, a distributed computing system that probably has led to scientific advances in other fields

So I wouldn’t say it was all for nothing, but it’s main benefit was the idea, and not the results it generated


> system that probably has led to scientific advances in other fields

Did it though?


Wikipedia has a table for how many papers each project produced:

https://en.wikipedia.org/wiki/Berkeley_Open_Infrastructure_f...

According to this, Rosetta@home (which is like Folding@home that runs on BOINC) produced 234 papers.


Except as a kid back then, the screensaver was trivial to install and neat to look at, and BOINC was a pain. I dropped it when they switched. I imagine some less-technical adults who were interested did as well.


Agreed, although the reimbursement should be based on whether a reasonable person could consider that to be a vulnerability. Often it’s tricky for outsiders to tell whether a behaviour is expected or a vulnerability


Yeah, the reimbursement would need to be for a good-faith submission worth considering, even if it wasn't actionable.


Companies wouldn’t send it because they know that most websites would block them


Rubbish. That analogy is like comparing a gun manufacturer to a hitman service.

Elon Musk is willingly allowing Grok to be used to harass women (and children). He could easily put in safeguards to prevent that, but instead he chooses to promote it as if its a good thing.

Practically no one defends websites that host AIs to remove clothing from photos of women, or put them in bikinis. The few people who do defend them are usually creeps who need their hard drive searched. Same goes for anyone defending this


Not sure about you, but I personally prefer my websites not to be able to be plagiarised by AI


Thanks, will definitely check this out

Has anyone else been avoiding typing FFmpeg commands by using file:// URLs with yt-dlp


Sadly not, those devices don’t have an exploit afaik


I wonder if liquid glass will push people to jailbreak 18 and 26.


I just hope Apple will fast track a UX update... but they probably won't, due to sunk cost fallacy, and the market and design trends will follow them.

This happens every time, a redesign comes out and people hate it. Same when iOS flat design came out. I dug into the archives, because HN has been around for a while now so we can do that, yay!

https://news.ycombinator.com/item?id=5869121

(hand picking / editing comments freely because I can)

> I read article after article from historically pro-Apple bloggers/authors explaining that no, flat design was fundamentally a bad move: the strongest metaphor is that of the phone as a tool -- that we needed skeumorphism, we need hints for interactivity, we needed polish.

> I think iOS 7, on the whole, looks worse than iOS 6. The stock icons look outright ugly; interfaces like the call-answer screen and the calculator look poorly designed, and everything has the sense that it just needs another run or two through the review process.

> Look at his iMessage screen comparison [1]: yes, the old screen looks a bit geocities, but you can actually read text very well; the new screen is almost unreadable. The prime aim of iMessage is to make people read text, not to look cool.

> [1] https://www.flickr.com/photos/mattgemmell/9023510971/

> Hopefully I'm not the only one that thinks this is going to kill usability. The reason old people can figure their way around <=iOS6 is that everything that can be tapped looks like a button. A more "mature" audience isn't what apple's good at appealing to.

> I'm volunteering at a center that teaches senior citizens various computer skills. One of the courses we teach is on how to use their iPhones. I'm dreading the moment that iOS7 is released: all of these people are going to have to start right back at the beginning in their understanding.

https://news.ycombinator.com/item?id=5856398

---

I'm fairly sure I read the thread I'm quoting from at the time because all of these arguments are still fairly fresh in my head.


> It would be great if we could download the solver manually with a separate command

Download a random video and then copy ejs from yt-dlp’s cache directory (I think it’s in /home/username/.cache)

> being able to package it up together with the solver

`make yt-dlp-extra`


"Attack vectors" is a very interesting choice of words. Yt-dlp is literally using a public API for its intended purpose (accessing videos). The only difference is how yt-dlp is delivering the videos to the user. Probably as much of an "attack" as user-agent spoofing or using browser extensions.

But to answer your question, no, there aren't any suitable APIs (I've looked into it). They all either require JavaScript (youtube.com and the smart tv app) or require app integrity tokens (Android and iOS). Please let me know if you know something I don't?


What about the smart TVs? There have to be a lot of them, do all of them run JS?

Also what kind of environments are executing the JS? If Google begins to employ browser fingerprinting that may become relevant.


Youtube’s tv app is actually just a website (youtube.com/tv, although you need a tv user agent). So yeah, I think most tvs are using JavaScript and the rest are using the tvlite api which has less formats than web_safari (which will continue to work in yt-dlp without Deno if you’re willing to accept 1080p downloads with inferior codecs)


They have been using the older APIs kept around for the benefit of those smart TVs for a very long time, but things move on and newer TVs get fancier hardware and more full-featured software, which includes YouTube, and so Google has started proactively dropping support.


yt-dlp dev here

The Android app uses an API which does not require a JS runtime, but it does require a Play Integrity token. The iOS app uses an API which is assumed to require an App Attest token.

Also, neither API supports browser cookies, which is a necessity for many users.


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

Search: