> Ok.I caught up with our oncall and This seems related to the Fly.io incident that is reported in our status page. Our login does call things in the Fly.io API
> we are already in touch with Fly and will see if we can speed this up
3,099 karma · joined October 24, 2016
https://github.com/b0o
> Ok.I caught up with our oncall and This seems related to the Fly.io incident that is reported in our status page. Our login does call things in the Fly.io API
> we are already in touch with Fly and will see if we can speed this up
It has a unique UI that I haven't seen before in similar tools, allowing you to see the relative L/C/H across all of the colors in the palette using graphs. It makes it much easier to create a palette that looks cohesive.
> Structured cloning algorithm defines the semantics of copying a well-defined subset of ECMAScript objects between Code Realms. This algorithm is extensible by host enviroment to support cloning of host objects.
https://github.com/dslomov/ecmascript-structured-clone
Eventually, in 2015, it was suggested to expose the `structuredClone` algorithm as an API:
> Has anyone ever proposed exposing the structured clone algorithm directly as an API? Katelyn Gadd was musing about fast deep copy in JS on Twitter, and I proposed a hack to use postMessage to do so[1], which works but it's a little roundabout. Since structured clone is a primitive that the web platform is built on it seems like a primitive that ought to be exposed. I know this exists in other languages (Python has copy.deepcopy[2]) and there's an npm "deepcopy" module[3] with lots of downloads so this is clearly something people use.
https://lists.w3.org/Archives/Public/public-webapps/2015AprJ...
> The adverse effects associated with long-term high protein/high meat intake in humans were (a) disorders of bone and calcium homeostasis, (b) disorders of renal function, (c) increased cancer risk, (d) disorders of liver function, and (e) precipitated progression of coronary artery disease.
- https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4045293/
High protein intake is associated with elevated levels of IGF-1, and "High IGF-1 levels increased the relationship between mortality and high protein":
> Respondents aged 50–65 reporting high protein intake had a 75% increase in overall mortality and a 4-fold increase in cancer death risk during the following 18 years. These associations were either abolished or attenuated if the proteins were plant derived. Conversely, high protein intake was associated with reduced cancer and overall mortality in respondents over 65, but a 5-fold increase in diabetes mortality across all ages.
> These results suggest that low protein intake during middle age followed by moderate to high protein consumption in old adults may optimize healthspan and longevity.
- https://www.cell.com/fulltext/S1550-4131(14)00062-X
Also important to note that one of the authors of the OP article is an employee of FrieslandCampina, the world's largest dairy co-operative and one of the top 5 dairy companies in the world.
The only other things I can think of are to only allow embedding content from certain domains (the article mentions that Writer.com's CSP lists `*.cloudfront.net` which is not good), or to not allow the LLM to return embedded content at all (sanitize it out). This should even be extended to markdown links - it would be trivial to create a MITM link shortener that exfiltrates data via URL params and quickly redirects you to the actual destination.
This isn’t really feasible to implement if your app runs on lambda or edge functions, you’d need a persistent server.
Here’s a diagram I drew of a simple approach that came to mind: https://gist.github.com/b0o/a73af0c1b63fccf3669fa4b00ac4be52
It would be awesome to see this functionality built into BricksLLM.
hi Comment guifg=#7e7490 gui=bold,italic
In Kitty, set the desired fonts: font_family IosevkaTerm Nerd Font Mono
italic_font IosevkaTerm Nerd Font Mono
bold_font IosevkaTerm Nerd Font Mono
bold_italic_font Iosevka Term SlabUsing this approach, you can use up to 4 different fonts: One for normal text, one for italic, one for bold, and one for bold italic. And the font for each group doesn't necessarily need to be that style, e.g. you can use a non-bold version for the `bold` font, etc.