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

It's not the only drug that suppresses appetite, but GLP-1 agonists (Ozempic, Zepbound, etc) appear to work for a larger percentage of the population, and significantly outperform previous appetite suppressants.

There's also findings that suggest that it goes beyond simply suppressing appetite, but also manipulates the "reward" center in the brain. Individuals who take it to lose weight find that they have reduced desire to drink or smoke, suggesting it's less that they struggle with appetite and more the medicine helps overcome addictive behavior.


Nicotine suppresses appetite as well and that has been used by humans for thousands of years.


That’s so silly, these drugs aren’t even anywhere near the same league of effectiveness. There’s plenty of fat people who take nicotine all day.


Hmmm...if as many people consumed semeglutide you would have examples of fat people in that population as well.


You certainly would, because not every case of obesity results from the same mechanisms. But just as with all the other what-about comments, this comment misses the point: this class of drug is wildly successful, and it's the most specific drug for this problem that's been developed so far

https://www.healthline.com/health-news/ozempic-glp-1-drugs-m...

Here's a good piece running through the failure modes in lay terms.


This is genuinely one of the stupidest conversations I’ve been involved in. If nicotine was as effective as Ozempic at appetite suppression then everyone would know about it, it would be commonly used in medicine to treat obesity and Ozempic would never have been created. I hope for your sake this is pedantry instead of ignorance.


Sure, it's just not as good as Ozempic at doing that particular job.


Tom7 implemented some of this with his Learnfun and Playfun (https://www.youtube.com/watch?v=xOCurBYI_gY) - It looks for lexicographical changes to bytes in memory (i.e., one byte seems to almost always increase, and then when it suddenly decrements, a neighboring byte is incremented) as a way of calculating memory location for increasing values (score, x-position), and similarly detects bytes that generally seem to decrease (lives).

It then tries to play the game, choosing inputs that increase the values that should be increasing (move right, gain lives), or tries not to decrease the values that are decreasing (don't die).


It looks like Autocanonizer depends on (the now defunct) Echo Nest (http://the.echonest.com). Spotify bought it back in '16, and the site stopped serving content sometime mid-May of 2020.


Echo Nest was one hell of an analysis company. We lost some amazing work when Spotify purchased it. The silverlining is that their Audio Analysis API endpoint is basically Echo Nest's work made wholesale available for each song they have but we lost the potential for improvements. This many years out, who knows what they'd have been able to do.


Weird, it worked on the local docker version


Under File, select "Prototypes", then double-click "Wigger", then select "Script..." from the Prototype menu.


She was LOVELY in person as well. I got her to sign my copy of How DNS Works.


A couple of quick optimizations:

- If weights are repeated, you only need to specify the last unique one

- You can chain filters using a comma

- You can drop that last point in the curve

  ffmpeg -i input.mp4 -vf tmix=frames=36:weights="1",curves=all='0/0 0.05/1' output.mp4


> You can chain filters using a comma

Haha, I knew there was some way of doing this, but I couldn't remember how (tried semicolons which didn't work), thanks :)


I am kind of amused that the combination of Moon and Robot is so weak that the robot is shrugging its shoulders as if to say, "It is what it is.":

https://emoji.supply/kitchen/?+=rt


Did a fascination with paper airplanes inspire Glider, or was it just a happy coincidence?


Oh, definitely related. My single mom was a "secretary" and occasionally brought home typing paper for me to amuse myself with. I drew a lot of pictures, made a lot of paper airplanes. :-)


> People get so enamored with trying to make REST APIs into this rigorous thing.

It is a rigorous thing, though. It's a standard, and one that has existed for a very long time.

> I would prefer HTTP status codes just go away altogether. Those are for the web browser software to do things like navigation, not for APIs. Same with HTTP verbs.

Verbs and status codes are fundamental for APIs that consume REST endpoints.

I totally understand thinking that vanilla REST is not the perfect model for every case. Maybe you should be using SOAP, or GraphQL, or HATEOAS. What a seasoned engineer shouldn't be doing is abandoning a shared specification and expecting everyone else to comply.

If I am using a third party's API and they serve nonsensical status codes (4xx when their DB is down, 2xx to let me know something failed), I will reach out and ask for them to fix their bug. If they tell me that the error code is deliberate, I will probably look for a more sensible vendor to work with instead.


There was some discussion on reddit about this last year, and the consensus is that the zip codes were not published and likely wouldn't be.

One person worked the paper's methodology backwards and came up with a list of potential candidate cities: https://old.reddit.com/r/todayilearned/comments/i3hb3c/til_t...

Kind of shocked me that I'm nowhere near any of those, as I feel like one of those harbingers (and I feel no desire to move to any of those places).


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

Search: