Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)TA
Posts
3
Comments
58
Joined
2 yr. ago

  • I'd say a battery is at least something that should be "chargeable", either one time or rechargeable. I dont think you can use solar cells to store energy back into the sun.

    Not saying that my definition does work for the dirt fuel cell, talked about in the article, though.

  • I would look into a library that does manipulation of odt (or docx). Code whatever algorithm you need to do the restructuring. Now your left with an in memory representation of the document that you can hopefully figure out how many pages it spans, or save it to a temporary file.

    All depends really on how feature rich the odt libraries are and/or how deep you want to dive into the spec.

    I feel like this is an XY problem. Is there an underlying issue your trying to resolve?

  • Interestingly, as ChatGPT might be trained on these ELI5 questions and as a result they are asked more infrequently, it might get worse over time or out of date on these types of questions by its own doing. I especially wonder how bad this influence will get on subjects that you'd normally search stackoverflow for.

  • I wonder if internally the emoji's are added through a different mechanism that doesn't pick up the original request. E.g. another LLM thread that has the instruction "Is this apologetic? If it is, answer with exactly one emoji." After this emoji has been forcefully added, the LLM thread that got the original request is trying to reason why the emoji would be there, resulting in more apologies and trolling behaviour.

  • Just thinking. Maybe there's a non linear relation between the uptake and the amount of alcohol. As for other products, they usually have a nutritional information table per 100g that you can thus read as percentages.

  • Explained by someone that doesn't know the technical side super well.

    1: It's a new protocol for displaying. The main difference from X11, as I understand it, is a simplification of the stack. Eliminating the need for a display server, or merging the display server and compositor.

    2: Some things impossible (or difficult) with X11 are much better supported in Wayland. Their not necessarily available, as the Wayland protocol is quite generic and needs additional protocols for further negotiation. Examples are fractional scaling & multiple displays with differing refresh rates.

    Security is also improved. X11 did not make some security considerations (as it is quite old, maybe justifiably so). In X11 it's possible for any application to "look" at the entire display. In Wayland they receive a specific section that they can draw into and use. (This has the side-effect of complicating stuff like redshifting the screen at night, but in my experience that has fully caught up).

    3: If you're interested, are in desktop application development (but I have no experience in that regard) or have a specific need for Wayland.

    4: I think X won't die for a long long time if "ever". I'm not super familiar with desktop app development, but I don't think it requires more work to keep supporting X.

    On the other hand, most of the complaints about Wayland I've heard were ultimately about support. At some point, when you're a normal user, the distro maintainer should be able to decide to move to Wayland without you noticing, apart from the blurriness being gone with fractional scaling.