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

I was thinking of building something like this just a couple of days ago. Looks awesome! Will definitely try it out


Thanks, if you think about something that might be improved, please open an issue!!!


do you have any source for that?


Other than using 40x agents concurrently for 2h on a Pro plan? No.

Btw, now it's back and limits are being enforced. Despite the super heavy usage, I'm still at just 50% of my total usage. They did lose some usage tracking for sure.


I can confirm. It was roughly until 00:30 GMT no rate limits applied. (Pro Plan with Opus) And it took some time extra for them after usage limit applied again, that you were able to see the usage.


Actually, no. "small booger" would be _moquito_ in spanish.


Look, as an English only speaker I don't care - I'm still stuck at "Haw haw, small booger library!"


Fair. The spelling is off, but the pronunciation is the same.


I'm Spanish and subconsciously pronounced the library as MOCKito, as opposed to moQUIto.


I’m bilingual(ish) and while I’ve always pronounced it MOCKito, I think I may start pronouncing it moQUIto instead now.


How is this faster than EasyOCR if its just a CLI wrapper around it?


Those are social media too


I do use Reddit and YouTube to follow topics related to work. And to some degree Hacker News as well. Come to think of it, these are the apps that make up for most of the screen time usage for me.



Oh, so you're an Android developer and an iOS user, huh? That's quite the rare combination. I'm sure you're very knowledgeable about both platforms, but that doesn't mean you have to be so condescending.

If iOS is so unreliable and unpleasant to use, why do you keep using it? Maybe you're just a masochist. Or maybe you're just afraid to admit that you're wrong.


Okay, a bubble for you to be burst:

> Android developer and an iOS user, huh? That's quite the rare combination.

It’s not. I am in the field and it’s totally not so, especially if you are talking about USA. Besides de-facto dev machine (in android dev world as well) is a Mac, so probably that’s a contributing cause, but anyway I have no large scale data on this.

> I'm sure you're very knowledgeable about both platforms

Really? Why would you have that doubt? I use both the phones extensively for multiple hours a day - at least every working day. I read about the feature set, releases, read dev docs etc of both the platforms regularly - and also do extensive discussion among team (the mobile team) as well how our competitors are using the mobile ecosystem.

So yeah I actually know what I am talking about. And you? That I am not sure :)

> you have to be so condescending

Ah, I don’t think I was. Apologies if it came across that way. It was just a knee-jerk of a shitty response to a very similar comment and I am totally fine with that. If I have to reply to a similar comment in future it’d be in the same tone or mo response at all; I should have gone for the latter.

> Maybe you're just a masochist.

See, now you are being an idiot. God, HN is full of us ;-)

> Or maybe you're just afraid to admit that you're wrong.

Awww. What an insightful twist of a comment. Genius


With all these limitations, why did you prefer IPv6 over IPv4?


Because we don't want to use 20 IPv4 addresses for the cluster of 20 nodes, when we only have so much addresses assigned to our institute. We could have gone the NAT route, but then we'd need to have some router. And if we designate the head node as router, all traffic would not go through the switch directly, but first through the head node and then out. This would mean that the nodes are less independent, as they have this one additional choke-point. Our university gave us a /64 for this network, so we just used that and it worked flawlessly, also for university-internal distro-package fetching and host-cluster connections.

Also, research software is usually working nicely with IPv6. If we encounter something that would really need IPv4, we could update the thing and give it some local subnet - but currently we were lucky.


But you still need NAT right? To support outbound connections from the worker nodes?


So long as you're using a /64 routed to you from your upstream, nope, you won't need NAT.


I think he is talking about this article https://andersource.dev/2022/04/19/dk-autocorrelation.html


Thanks! Title updated


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

Search: