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

Great, but what is the license? The GitHub has it as none.


Because the Iranians blocked the entrances with soil. There are satellite photos showing dump trucks at the entrances and the entrances being covered over.

It was a clever move on the part of Iran, because an invading force would need to bring heavy equipment with them, which isn't going to happen.


Well.. kinda? Makes me wonder about just dropping munitions on the entrance, or even just using conventional explosives.

And yes, I don't know the skill set to validate the thought. However, I have seen beaver dams cleared with dynamite, and there's a wide level of explosives which can be dropped or deployed on foot...

(People saying it would be violent, well sure, but so is dropping bunker busters...)


Beaver dams are not several dozen tons of dirt. You are not going to C4 through several tons of loose dirt.


Great work, I love this.

I tested it with my recently restrung BG80 at 27lb and it came out with 26.69lb!

One improvement I'd ask for, is in the string thickness selection. I had to go look up the thickness of BG80. It would be cool if you could preload some of the popular strings in there.

Also, the string tension number is good, but I'll get it to a peak and then I'll stop to press the stop recording button and it's dropped back down. It would be nice to have a "Peak tension" or a graph of the tension.

Thanks


It should be noted that there is already a lint rule for this: https://typescript-eslint.io/rules/no-floating-promises/


I created a ticket, using comments is not necessary because there is already the `void` syntax for when you don't want to wait:

https://github.com/stanNthe5/typescript-autoawait/issues/1


I have a lot of .cursor/rules

If it goes off track I put a rule in there. It’s like a junior developer that I have to keep constraining it to project goals, coding styles and other aspects.

I have different files in there to help with being able to reuse rules for different projects.

Overtime it’s getting better at staying on track.


Have you posted your rules anywhere online?


It’s short sighted to say Europe should spend more on defence. Europe is now going to move away from US weapons and develop its own systems.

That’s a net loss for American defence companies and jobs in the USA. For the US military, costs per unit will go up, because they aren’t mass producing these systems at the same scale.

Trump didn’t just step back from an alliance that existed for 80 years, he also burnt the bridge by destroying trust.

For Europe, it’s probably a good thing to kickstart a new economic recovery, e.g. German automakers can switch to tanks and IFVs.


Cursor has the .cursorrules file. Do you use that in combination with your approach?


In England we call them "Indicators" as opposed to turn signals. My driving instructor said, they are call that because they are only indicating they might go that way. Never assume they will. It was some defensive driving advice.

I can understand that it's annoying that inconsistent use of turn signals is an annoyance, it isn't as bad a people that don't use them at all, but my understand is that the American road system doesn't have roundabouts like we do, which kind of require good indicator use for smooth driving.


We have roundabouts. We don’t have them everywhere but then I bet you don’t either.

My home town in Idaho has built at least five I am aware of in as many years, with more planned.

My neighborhood in Seattle plants a tree in the middle of unmarked intersections which effectively creates a mini roundabout.


> I bet you don’t either.

Oh you haven’t been to the UK if you think that. :) They are absolutely everywhere. Traffic planers love them.


I've driven in England and New Zealand, and they really had them everywhere.

Yes, we have them in the US, but we don't have enough of them that you can expect that all drivers know what to do with them. It's entirely too common for approaching drivers to be unaware that they must yield to vehicles already in the circle.


This isn't a criticism but feedback from someone that is looking for a 3rd party auth service.

I am starting up my own business, I have spent some time evaluating AuthKit and I can't justify investing time on it. Specifically, I want to target small to medium sized companies that want SSO built into my services.

The fact that the auth would be at an *.authkit.app domain is disconcerting, users would think they have been click-jacked because they have left the domain they were expecting. Your comment about custom domains costing because of Cloudflare is strange given how much CF charge verses the $99 per month cost you charge, there seems to be a big order of magnitude difference, since under the Pro plan they charge 10c per additional domain. Perhaps you have additional services behind that, but it seems strange: https://www.cloudflare.com/en-gb/plans/ The "Powered By x" would actually be preferable, many people are used to seeing thing like that on payment screens.

Also, the SSO connectors being $125 per month per connection, rules out my target market. That is a lot in my market and it doesn't ease off as I grow, it's a fixed base cost. As I grow to 20-30 customers I'd be better off hiring a developer to implement the same features.

I get it that I am not the target market; that big businesses wouldn't bat an eyelid at that kind of costs. But for my purposes, I can't justify your costs. Good luck to you.


There are several open source options out there (several linked above) that could be a good fit for your business economics. I know lots of folks talk about Supabase and Auth.js on X.

If you have the time and patience, you can also certainly build it yourself. There's no miracles here, just complex engineering and solving a thousand edge cases.

If you decide to use open source, make sure you quickly update dependencies so you're always running latest. Ruby-SAML had a major vulnerability disclosed last month and thousands of apps were affected: https://workos.com/blog/ruby-saml-cve-2024-45409


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

Search: