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

Sorry, the zoom meeting link has changed so now the meeting will take 4 hours and you must get the agenda by FAX.

(this is what happened to OP)


> Hello everyone. Apparently we were not registered at Troisdorf station, so we are on the wrong tracks. We cannot stop.

Of course the train could not stop. It was not registered!


It makes sense when you look at how the numberic for loop looks in Lua.

In Lua you specify the “beginning” and “end” of the iteration, both included. It doesn’t work like in C, where you have an initialization and an invariant. What makes it short in C would make it longer in Lua, and viceversa.

You could argue “why not make loops like C”, then. But that can be extended to the limit: “why have a different language at all?”.


“local” is the same as the “let” that you are describing, isn’t it? Just 2 chars longer.

Isn't this what html-over-the-wire/turbo/stimulus is? [1]

[1] https://hotwired.dev/


> each week we slim down to group by half

What the hell.

Consider making them fight each other in an arena, you could monetize that.


Hunger games style I like it

Anything besides next quarter does not exist.

> AI browsers are proliferating

Are they, though? I get bombarded by AI ads very frequently and I have yet to see anything from those "AI browsers" mentioned on the article.



Do they have any users, though?

Would you like to research this and tell us?

I don't, but that was also my point: I don't care if new AI browsers pop up, if no one uses them they might not even exist.

I didn't even know that AI browsers were even a thing until I read this article. And I work on AI.


I downloaded the chatgpt one, tried it for a minute, thought meh, and went back to my usual browser.

Does that count as a user?


If you don't want invoice 22 to be shown by someone putting 22 on the url, you definetly need to enforce permissions on your app. The Global ID issue is tangential to that.


Sure but the real concern of the article that if passed "gid://moneymaker/Invoice/22ecb3fd-5e25-462c-ad2b-cafed9435d16" the global id locator will effectively locate "gid://moneymaker/Invoice/22". Which is to say, that what is supposed to be a system-generated id which has no need for de-slugification, uses the same lookup method as is normally used for URLs which attempts to de-slugify.

Obviously, this means that first gid was bogus anyway, as it was trying to look up via the wrong key, but the fact that it doesn't fail, and will instead return the record with primary key "22" can certainly be surprising.


The original comment is valid though, this has nothing to do with GIDs, standard /:id/ routes, and Model.find() can suffer the same issue. Probably because "22ecb3fd-5e25-462c-ad2b-cafed9435d16".to_i is still 22?


Yes, you need both

Of all the people that you can scam, why go for children with cancer. I guess you think they are an easy target because they are desperate? Pure sociopath mentality. Crab mindset.


In case any sociopath is reading this: just go for old rich people. They are also desperate because they are alone, seeing their relevancy wane, and their deaths are closer every day. A single successful scam will represent a bigger return of your invested time and effort than, compared 10 successfully scammed children with cancer. And they might not even make a fuss if you steal some money from them, it will make them look weak and it will only represent a small percentage of their wealth.

And you are less likely to be killed by a mob, as a bonus.


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

Search: