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

That’s no better than Windows (without a lot of effort and a constant game of cat and mouse only achievable by technical users). At least Google’s cloud services tend to actually be good, if you made peace with the tracking and privacy concerns.


> what is the first video you show them

Whatever is latest posted across their followings/subscriptions?


If they just signed up they have no followings or subscriptions. So now what, you need to show accounts to follow first? Thats the same problem as deciding what the first video to show is. How do you decide who they should follow? Or the vision is that you can only have friends as if it's 2005 and you can't discover anything serendipitously?

I don't consume any content from my friends on something like tiktok where I'm interested in discovering people that have good content under topics I'm interested in. I don't know who those people are and I want to discover new ones that come up not just follow some already popular accounts.


>So now what, you need to show accounts to follow first

Youtube won't show you anything at all if you have a new account with watch history turned off. It says something like "turn on watch history and watch videos so we can recommend some for you".


Undoubtably the change needed here will introduce friction, will reduce viewing time, and society will be better off for it.

The whole idea here is to make content consumption more deliberate and mindful rather than just opening the app and veging out to an endless feed of slop.


You have a lot of certainties. Say will people in hospital bed for 2 weeks agree with you?


That’s also an algorithm. An unsophisticated one, but an algorithm nonetheless.

You can (and should) argue that such a simple algorithm doesn’t “count”, but fundamentally the exact wording of the grandparent post never works, legislatively.

Lawyers will lawyer.


> That’s also an algorithm. An unsophisticated one, but an algorithm nonetheless.

The problem always has been "(personalized) opaque algorithms". Time sorted by followers isn't really opaque, nor is "sorted by likes" or whatever. The problem is always pulling in parameters that a users either has no active control over or are so variable they effectively could be random.


Can everyone just please stop saying "well ackshually sorting is done with an algorithm" and just assume at least not-idiotic-intent here? No no one will ban "algorithms" or suggests anything of that kind. Yes it's a terrible name. Yes it will be hard to formulate what's allowed and what isn't. But a very simple litmus test is: what are the inputs to the algorithm?

users coarse geographic location? Fine

AI detected language of the content? Fine

global popularity of the video clip? fine

user's past behavior: number of videos with similar content they watched? Average number of seconds this particular user usually waits until scrolling further?

The pattern is obvious. Personalized algorithms is what's targeted. Let's keep the discussion intelligent.


Your litmus test isn't correct and your assumption of personalisation isn't correct either. All of the criteria that you see as fine are controlled under the relevant legislation and are considered personalisation, requiring transparency etc.

Furthermore, bills have been brought to EU parliaments that have erroneously attempted to ban all forms of ranking, which would include even the most basic information retrieval algorithms. So it isn't obvious at all what is meant by 'algorithm'.


It’s not about whether there is an algorithm, but whether it’s controlled by the user.


If you can get that 5k/month down to let's say 1k, that's a saving of 48k over the course of a year. You can get a consultant/freelancer for half that sum that'll happily do it for you.


Then you'd have people run extension cords across the border and selling their cheap electricity at inflated prices to their freezing neighbor.


Yeah this is just typical techbro gaslighting. There is no rate-limit and hasn't been for years (it's just default deny), but they refuse to change the wording to reflect.


Would you care to cite your source that GitHub does not apply rate limits to unauthenticated requests?


The parent's experience which mirrors my own - on a clean residential IP that hasn't sent any traffic I hit that "rate-limit" on my first request to the commits list view.

So there is no rate-limit, it's a default deny for unauthenticated requests... which could be fine but at least update the error message to reflect that.


It's a rate limit of 0 RPS to that endpoint


But unless you're on a PaaS, you have "infrastructure engineers" already. So why not at least let them make back their salary by making them built a cost-efficient infrastructure?


> they said they must show they are on Hyperscaling cloud.

This is the main reason; and it applies to developers (they need cloud buzzwords on their resume), it applies to managers (who in turn hire only those with said buzzwords) and it applies to company execs/CTOs who can brag about the complex (self-inflicted) problems their company is solving at the next cloud provider conference, so they can justify yet another VC round.

Run this for over a decade, and you'll end up in a situation where an entire generation of "engineers" is no longer capable of configuring a Linux box to serve some basic webapp and will make up whatever reasons to avoid even attempting to do so.


Unless we're talking actual PaaS (Heroku, Render, Railway, etc), the cloud also needs a dedicated skillset, so "cloud" doesn't remove the need from a sysadmin.

If you can get (and trust they do it right) developers to do AWS or Kubernetes, you should be able to trust them to do conventional Linux sysadmin on a bunch of dedicated boxes.


I suspect you're either severely underestimating what the cloud offers or thinking of a very narrow set of software businesses.

A full stack/backed dev is more than capable of learning both, but one of those has way more foot guns than the other.


Agree. There's lots of programmer-centric SDKs and tools that abstract away a lot of the infrastructure details and make it feel like writing/running code.

A few years ago I worked at a place that was on AWS ECS and I think I can count on 1 hand the number of times I needed to SSH into a machine each year. Half of those times were SSHing into the singular VM we had that ran a Strong Swan IPsec tunnel to a vendor.

The current place I work we have bastions and EKS. Occasionally, I SSH into a bastion but usually just use Cloudflare Tunnels (they run as k8s pods and the control plane is private so the bastions are helpful for bootstrapping things). Out of that stuff, it's all been converted to immutable infrastructure and gets recreated once a month with the latest AMI. Probably could kill the bastions and run Cloudflare Tunnel agents on Fargate on ECS to eliminate all the o.g. sysadmin work but some people are nostalgic so I gotta wean em off VMs


You can also put these lambdas on a shared hosting provider as CGIs and get the exact same experience.


There's a multibillion dollar industry that lives only because they managed to successfully convince an entire generation of "engineers" to become helpless and not be able to serve an HTTP response using their own hardware even if their life depended on it.


It’s easy to convince developers of a thing if it starts with: “you don’t need to learn X anymore”


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

Search: