It was more about wanting to give code away in a form that was free for other people to use commercially and have that freedom guaranteed for future users.

Appreciate the feedback though, and yes is slightly less permissive compared to MIT/Apache but about the same as MPL as they both place restrictions. I tried to make it so it doesn't capture unrelated code in a project under its licence so think it works out slightly more permissive then GPL.

Comments URL: https://news.ycombinator.com/item?id=49405284

Points: 3

# Comments: 5

The OCR still tells us more about the target than the actor, but I guess they are suggesting the choice of target itself is the indicator.

> Use of Korean language, OCR targeting of Korean documents, and focus on GPKI systems strongly suggest North Korean origin.

I'm don't follow how needing OCR to read Korean documents points to them being North Korean?

Could also point in the opposite direction of them needing to copy the text for translation.

Yes environmental factors are there too, otherwise it would be 100%, but there's enough evidence pointing to genetics that it is really disappointing when people try to find spurious links to false causes instead.

https://www.open.edu/openlearn/mod/oucontent/view.php?id=669...

Adjusting their product names sounds like a small change they could have made to avoid antagonising a close partner.

Running their own plug-in mirror infrastructure is something companies often do to reduce the risk from relying on a third party.

Similarly having some stake in the development of WordPress reduces risk of them being shut out if there is a license change that necessitates a fork.

Less about caving in on wishes as more that it's risky to choose both to rely on a third party and wind them up at the same time.

I was skeptical when they mentioned that other doctors had been promoting these drugs at gatherings, but what irritated me most was that they didn't have access to the research discussing the known side effects because the journals were behind a paywall. A willingness to pirate / use Google scholar to bypass paywalls shouldn't have been necessary to know about safety issues for a drug.

The process model was the novel selling point at the time from my memory [1].

[1] https://www.scottmccloud.com/googlechrome/

I wouldn't expect lightweight office use to be primarily limited by the amount of memory available so perhaps that isn't a fair comparison still.

On desktop the impact of power consumption is lower, so it is better to offer a slightly higher spec base model.

> Cookie Pal includes the following features:

> Automatically and transparently accepts or rejects cookies from all or specified servers without user interaction.

> Cookies received from unspecified servers can be automatically accepted or rejected without user interaction, or the user can be asked for confirmation.

> "On the fly" adding of servers to the accept from and reject from lists, allows you to manually accept or reject a cookie the first time it is received and then have it automatically accepted or rejected every time it is received thereafter.

[0] https://web.archive.org/web/19971012223847/http://www.kburra...

[1] https://web.archive.org/web/20010331050614/http://www.kburra...

We out executed, but I'd advise caution with mentors. Some were great help, this one was malicious.

The implementation details around cookie recreation don't matter if users are still being tracked. Especially bad if this lets them track you on third party sites that contain Google Plus buttons or advertising iframes.

By ensuring users always remain logged in to the browser they gain a strong advantage over other companies that track users. Users attempting to remove tracking cookies shouldn't find Google ones permanently bundled with the browser.

The intent was likely to aid convenience and avoid users being unexpectedly logged out, but combined with Google automatically logging users into the browser this is a sign that the Chrome team is paying less attention to user privacy than they used to.

Perhaps users who regularly clear all cookies will start using guest accounts instead. Myself I'm more concerned about the general trend of unexpected behavior.

Even if I hadn't already had a terrible experience with their login feature, it is a privacy violation. I haven't agreed to have my browser history and other private data uploaded to an advertising company. The argument that most users want this is flawed: many would object to giving Google access to this without permission. Maybe the EU will step in?

You can add a webhook on GitHub and have it point to our Pull Mirroring API [1], followed by manually setting up the integration to send status updates back [2].

We're looking to make this process easier, and have explored ways we might implement this in https://gitlab.com/gitlab-org/gitlab-ee/issues/5220.

[1] https://docs.gitlab.com/ee/api/projects.html#start-the-pull-...

[2] https://docs.gitlab.com/ee/user/project/integrations/github....