In case it matters to the thread, Solecist is a newly created user that calls itself an AI language model. It seems to be geared to playing the “other side” in conversations/comments.
As a long time diabetic (t1d) with direct relatives also afflicted with this horrible disease, it’s frustrating that we often miss the key factors in insulin resistance and fail to see how they fit in.
The level of serotonin and its interplay with our current level of immune response/inflammation in our body is the single best predictor of insulin resistance. That’s simply because every good thing you can do to lower resistance increases serotonin. Serotonin then decreases inflammation. When you exercise for a long period of time you are not only increasing your immediate availability of serotonin, you are also increasing your daily availability for serotonin.
Obviously it’s a little more complicated but from a big picture standpoint, either something is increasing inflammation in you today and increasing your insulin resistance or (hopefully) the opposite is happening and serotonin is moving your insulin through your blood stream like a mag lev train.
I believe it's about integration with RCS. Now, I don't know much about rcs but presumably it's similar in features to imessage. So Google wants Apple to adopt RCS so you can send "blue" messages to others outside Apple's network.
Sometimes, if Im quick enough, pressing the reader view on my phone shows the whole article. It doesn’t work on every site just some that are lazy and just throw a divider up on the screen without hiding the actual content. That worked for me here. Otherwise, I just use the archive links HN users post.
Somebody posted this in HN, if use save it as the URL of a bookmark and run it on a page with a divider on screen it will delete it often enough that I keep on my bookmarks bar.
javascript:(function()%7Bdocument.querySelectorAll(%22body%20%22).forEach(function(node)%7Bif(%5B%22fixed%22%2C%22sticky%22%5D.includes(getComputedStyle(node).position))%7Bnode.parentNode.removeChild(node)%7D%7D)%3Bdocument.querySelectorAll(%22html%20%22).forEach(function(node)%7Bvar%20s%3DgetComputedStyle(node)%3Bif(%22hidden%22%3D%3D%3Ds%5B%22overflow%22%5D)%7Bnode.style%5B%22overflow%22%5D%3D%22visible%22%7Dif(%22hidden%22%3D%3D%3Ds%5B%22overflow-x%22%5D)%7Bnode.style%5B%22overflow-x%22%5D%3D%22visible%22%7Dif(%22hidden%22%3D%3D%3Ds%5B%22overflow-y%22%5D)%7Bnode.style%5B%22overflow-y%22%5D%3D%22visible%22%7D%7D)%3Bvar%20htmlNode%3Ddocument.querySelector(%22html%22)%3BhtmlNode.style%5B%22overflow%22%5D%3D%22visible%22%3BhtmlNode.style%5B%22overflow-x%22%5D%3D%22visible%22%3BhtmlNode.style%5B%22overflow-y%22%5D%3D%22visible%22%7D)()%3B%0A
Disabling javascript generally works too. I actually browse default js disabled, and if it seems like a site isn't working, I enable JavaScript for that domain.
Yeah I hear you. I’m pretty sure though I’ve come across sites that on a timed refresh have truncated the article. So the whole article was there until some process ran to check sign in status. Maybe that doesn’t happen anymore. I haven’t really noticed.
Woah woah woah. The sentiment here is pretty wild for me. Creating a platform that offers a free tier is a BUSINESS decision. Replit knew what they were doing bringing all of those free ‘customers’ online. They didn’t do it out of the goodness of their heart and they have to deal with the very real/costly aftermath of a bait/switch. Perhaps we should be used to this rug pull by now but that’s still what it is. I’ve never used replit but have been in the position to decide on creating a freemium model and I knew quite well what the consequences would have been. The idea that were saying it’s the users fault for falling for a tactic that’s origin is “yo man, try this … first hits free” is crazy to me. Now get off my lawn.
Yeah, they've also switched their complete concept around before, going from a simple web code editor to a deployment-based hobby hoster, already breaking the use cases (and simplicity) for many users.
I totally agree and would say that openly criticising such decisions is important, so that companies are a bit more careful with introducing usecase-breaking changes - including changing their business model in a way that makes it not viable anymore for many users.
Such things really make a company seem unreliable, but unfortunately it seems to have become common with the "ship early, break often" mentality especially in the start-up world.
Yes. We should be up to speed on safety issues surrounding the purchases we make. The third example is murder and we already have “regulations” for it. (I know arsenic and lead can be in muffins already. I’m assuming a large amount was added.)
I’m pretty sure that ransomware and other tactics that largely end with a significant crypto transfer is their end game. Evidently, they are really good at it - $1.7 billion in 2022.
So anything to slow down the researchers are my guess. Keep the drain open, so to say. Just my two cents.
For those who think that you can simply build something “fluid” or “flexible,” it’s a lot harder than it seems. A lot of the industry jargon comes from print and the printing process; margins, padding, kerning, spacing, etc. There is no such thing as a fluid layout on a printing press (as far as I know :-). So we are stuck with a language to describe design based on a different era. Additionally, in the design phase you HAVE to select a layout/viewport for proofs and examples. Which in turn the client will expect to look exactly right on every surface. There is obviously room for client education and pushback but fluid designs seem like an afterthought in html/css where we are adding new features on top of html/css that are best used in a fixed width based system.
If you learn non fluid design first it seems hard. In absolute terms, it's really just a matter of using flexbox and percents, and being willing to just scrap your design idea and do something else if it doesn't map nicely to something fluid.
Client education is a challenge and all, they often have ideas in mind that are very specific (For some reason clients invariably like the simplest thing that's the least general and most direct of a translation from a basic analog system...). But on the technical side... once you stop making designs that rely on being able to control exactly where everything goes it gets a lot easier.
reply