• 0 Posts
  • 32 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle


  • You can’t build a box that will survive long without your help. You’re maintaining a living system, not a sculpture. It needs someone at the wheel making decisions. Updates will have breaking changes. Tokens and certificates will expire. Eventually hardware will fail.

    The best you can do is provide an easy way to export the important data into a digestible format for your loved ones to manage with the skills they have. If that means pushing it into a managed service owned by Big Tech, so be it. You don’t want to tacitly hurt them for their lack of interest in self-hosting.






  • I’m not sure I understand your question.

    Eat has its own major mode which is used when you open a standalone buffer via the eat function.

    When it’s embedded in Eshell it mostly just does the right thing whenever you invoke a command that uses terminal control codes (e.g. htop) – and many of those can be closed with q, yes.

    I assume Eat is activated for any program listed in the eshell-visual-commands variable (but I’ll admit I don’t really understand how that works). The notable new minor modes present when I run htop in eshell are Eat--Eshell-Local and Eat--Eshell-Process-Running.





  • Thank you for calling that out. I’m well aware, but appreciate your cautioning.

    I’ve seen hallucinations from LLMs at home and at work (where I’ve literally had them transcribe dates like this). They’re still absolutely worth it for their ability to handle unstructured data and the speed of iteration you get – whether they “understand” the task or not.

    I know to check my (its) work when it matters, and I can add guard rails and selectively make parts of the process more robust later if need be.



  • I’d ask why they don’t make it optional (I’m not a Brave user) but it seems it was.

    Another issue is that Strict mode is used by roughly 0.5% of Brave’s users, with the rest using the default setting, which is the Standard mode.

    This low percentage actually makes these users more vulnerable to fingerprinting despite them using the more aggressive blocker, because they constitute a discernible subset of users standing out from the rest.

    Given that, I’m inclined to agree with the decision to remove it. Pick your battles and live to fight another day.






  • There are a lot of analogies but they all fail in some way. I think PBS Spacetime does the best in general, with good graphics to back up the words.

    My layman’s explanation is probably all stuff you’ve heard before. Massive objects “warp” spacetime and things that get stuck in those “wells” eventually fall to the bottom due to drag (from a variety of sources).

    You’ve also probably seen the rubber sheet with a bowling ball in the middle used to represent that warping. To visualize that in 3D, I like to imagine a 3D grid of nodes and edges (like a jungle gym of joints and bars) where the whole thing is flexed inward towards a center point. More warped near the center, less warped further out. That kind of conveys the acceleration from gravity felt by things around that center mass.


  • Thank you for calling this aspect out. I’m surprised so many people are overlooking it. I protest YouTube for the same reasons, but I’ve got one more to add.

    When they merged Google Music into YouTube, the service became worse. I’d often have music streaming throughout the day over my speakers, but that broke after the merge.

    Anytime I watched a video on my phone that had Content ID-recognized music in it (even in the background), they would cut the stream to my speakers because I am only allowed one stream with any music in it at all.

    This isn’t the behavior when you use the ad supported service. Only the paid.

    Not to mention all the proper features of Google Music that didn’t carry forward.