News for hackers. Stuff that matters.

SixtyHurtz

Re:TikTok goes dark in the US on Sunday January 19, 2025 @08:34AM (#42756804)
Carry on with that:

> The President must further determine that the divestiture “precludes the establishment or maintenance of any operational relationship between the United States operations of the [application] and any formerly affiliated entities that are controlled by a foreign adversary, including any cooperation with respect to the operation of a content recommendation algorithm or an agreement with respect to data sharing.”

The content recommendation algorithm is TikTok. It is developed in China by Chinese engineers. There is no lawful way for TikTok to operate under this law, and the SC has completely failed by not considering this. It's a really lazy judgement.

Probably the outcome Congress was hoping for is that it gets sold to a US buyer who would operate TikTok with the technology under license, and everyone would just pretend that now it's operated by a US interest despite that being impossible. Like sure, they would be running the servers, but the code would largely still be written in China!

Edit: Actually it would be kind of worse, because thinking about it TikTok has a lot of engineers outside China now, so how would it even work? Would they fork the code and then that would be it? It's such a crazy proposition.

Re:Making AMD GPUs competitive for LLM inference on Wednesday December 25, 2024 @08:33AM (#42508703)
That's just BOM. When you factor in R&D they are clearly still losing money on B580. There's no way they can recoup R&D this generation with a 10% gross margin.

Still, that's to be expected considering this is still only the second generation of Arc. If they can break even on the next gen, that would be an accomplishment.

Yep, that's basically it.
Re:Winamp Legacy player source code on Tuesday September 24, 2024 @06:26PM (#41641622)
Because if I didn't have a license then that would mean I would be liable for infringement every time someone downloaded it from GH. That's exactly why GH has the TOS that it has - so that nobody can be sued for just using GH when a rights holder uploads their own work to a public GH repo.
Re:Winamp Legacy player source code on Tuesday September 24, 2024 @04:33PM (#41640625)
Cloning is part of GitHub's functionality, so therefore we can clone it but can only commit those changes back to GH. We are permitted to do anything that is part of GH's functionality.
Re:Winamp Legacy player source code on Tuesday September 24, 2024 @04:21PM (#41640498)
The GitHub ToS states:

> If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub's functionality (for example, through forking). You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.

It would be weird to have a license that lets me create a fork in my own repo, but doesn't permit me to distribute it. If I create a fork of a public repo on GH, I require a license to distribute it because a public repo can be forked or downloaded by anyone. I can't them doing doing it. Therefore permission to further distribute is required for participation on GH.