We Don’t Need A Native .visually-hidden - Dennis "WebAxe": http://www.webaxe.org/we-dont-need-visually-hidden/ It'd be trivial for me to implement such a feature, but yes my focus is on fighting these other issues...
I'm now registered as co-maintainer of Haskell CSS Syntax on Hackage, since that package appeared to be unmaintained. And I've released CSS-Syntax 0.1.0.1, compatible with Text 2!
That'll help make it easier for others to contribute to the Argonaut Stack, avoids some dependency conflicts...
See if I can catch wereHamsters attention to see how they want to play this... Haven't had much luck previously, hence why I asked Hackage for these permissions...
I'm still not seeing text displaying, but I silenced that crash!
Fixed an issue in my logic for determining whether I have a run of inlines. I don't know if the issue will reoccur, but this did need fixing! Much like my other fixes!
Really getting down to the wire fore LibrePlanet demo, but hopefully I'll have it running tomorrow!
Found my bug! I didn't complete a refactor in CatTrap allowing me to capture runs of inlines to render! Switching from a recursive routine to a co-recursive routine.
Still struggling to locate where the text data is getting dropped...
It's coming through in the input. But not in the output. Traced it through to the styling input.
Fixed a couple issues though with determining which elements should be rendered as inline text... That would be part of it, but seemingly not all of it!
Started debugging some issues #Haphaestus now that I've hooked all the pieces together... I'm not seeing any text though, & apparently (according to some printf debugging) it's not in the layout tree...
Also LOL-worthy, against the backdrop of utter lack of transparency was "We believe that accurately predicting future capabilities is important for safety. Going forward we plan to refine these methods and register performance predictions across various capabilities before large model training begins, and we hope this becomes a common goal in the field."
Trying to position themselves as champions of the science here & failing.
Okay, taking a few moments to reat (some of) the #gpt4 paper. It's laughable the extent to which the authors are writing from deep down inside their xrisk/longtermist/"AI safety" rabbit hole.
Things they aren't telling us: 1) What data it's trained on 2) What the carbon footprint was 3) Architecture 4) Training method
But they do make sure to spend a page and half talking about how they vewwy carefuwwy tested to make sure that it doesn't have "emergent properties" that would let is "create and act on long-term plans" (sec 2.9).
A browser developer posting mostly about how free software projects work, and occasionally about climate change.Though I do enjoy german board games given an opponent.Pronouns: he/him#noindex