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

I would also recommend Benn Jordan's YT channel, he has a couple of videos covering flock cameras. His latest one is: https://www.youtube.com/watch?v=uB0gr7Fh6lY

edit: grammar


Off topic question.

> I imagine 90%+ is peered or hosted inside ISPs, not via transit

How hosting inside ISPs function? Does ISP have to MITM? I heard similar claims for Netflix and other streaming media, like ISPs host/cache the data themselves. Do they have to have some agreement with Steam/Netflix?


Yea netflix will ship a server to an ISP (Cox, comcast, starlink, rogers, telus etc) so the customers of that ISP can access that server directly. It improves performance for those users and reduces the load on the ISP’s backbone/transit. Im guessing other large companies will do this as well.

A lot of people are using large distributed DNS servers like 8.8.8.8 or 1.1.1.1 and these cansometimes direct users to incorrect CDN servers, so EDNS was created to help with it. I always use 9.9.9.11 instead of 9.9.9.9 to hopefully help improve performance.


The CDN/content provider ships servers to the ISP which puts them into their network. The provider is just providing connectivity and not involved on a content-level, so no MITM etc needed.


Who would run Windows on AWS? I know some companies do, but it's like 0.01% of all Windows machines.

The implication is that it's a lot of bots using a common user-agent string.

> 80% of new developers on GitHub use Copilot in their first week

I am not sure how honest this statement is. I remember typing something in an input which I thought was search, but no, it was AI search or something like that. Free copilot got activated on my account simply by submitting a search query. Statement may be technically true but it's target audience are investors and maybe higher management (someone is getting a raise or a bonus), not actual developers.


Not really, you should learn Typescript by learning JavaScript first. Then consider learning C#. Or if you want to focus on the back end side learn C# and skip TS/JS.

They are created by the same person but they are very different in my opinion.

TypeScript is "a tool" for JS, it is possible to compile without errors but still fail in runtime (e.g. wrong object type returned from API), on the other hand parsing JSON with C# will give you correct object type, it may fail if some properties are missing but it will fail at parsing call, not further down when you try to use missing property. In other words typing is not glued on top of the language it's core of the language.


I sometimes miss Spring magic when working with ASP.NET, and I worked 12+ years with C# and only a year with Spring. Not saying one is better than the other, it's always a choice, less magic = more boilerplate and less boilerplate = more magic.


Short for oxycodone, a drug abused by addicts.


Reminds me of something similar I saw a few days ago.

https://old.reddit.com/r/3Dprinting/comments/1o195z6/i_elimi...


Do you have a link? I want to read more about that. Did they interpret any use as deriving from minio?


They changed their public guidance at this point, but you can still find references to their approach to AGPL quoted here: https://news.ycombinator.com/item?id=35328316

> "When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the larger stack and MinIO."


Yes, the page at https://www.min.io/opensource no longer contains this phrase. It sounds reasonable now. I guess they talked to a lawyer.



Did they ever get permissions from their contributors to switch to AGPL? Last I checked they did not. They didn't require a CLA either.

So no matter what they claim large parts of the codebase are still apache2.


It wouldn't matter anyways, you cannot relicense historic releases.


It does matter, since the current AGPL license status is questionable at best, they did not have permission to relicense code added by contributors. This is why CLAs exist.


If you don't have a CLA you just end up with the new changes being AGPL which creates a mixed license amalgamation which in practical terms regresses down to the stricter of the licenses which would be the AGPL.


Do we need a fork? As an example, ffmpeg is source only for mac and windows, which just means someone else is building and distributing binaries.


They changed their license to AGPL, removed features (Web UI, etc.) and now they don't provide docker images/binaries. It's their project but; what's next?


Obviously they will eventually no longer license AGPL at all. It's wild to me how this can be a surprise to anyone, this entire company has been one gigantic red flag for years and that's just what's publicly known. It's a legal department with a software product as a side business.


> what's next?

Removing existing Docker images? Seems unlikely.


It seems crazy that docker hub images are not immutable. Makes them really unreliable.


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

Search: