home.social

Search

28 results for “benjamineskola”

  1. @benjamineskola @tusharhero @oatmeal

    #LLMs are a distraction & he misses imo a big point.

    #emacs allows you to uniquely configure it to your needs, to suit your worflow

  2. @benjamineskola @tusharhero @oatmeal

    #LLMs are a distraction & he misses imo a big point.

    #emacs allows you to uniquely configure it to your needs, to suit your worflow

  3. @benjamineskola @tusharhero @oatmeal

    #LLMs are a distraction & he misses imo a big point.

    #emacs allows you to uniquely configure it to your needs, to suit your worflow

  4. @benjamineskola @tusharhero @oatmeal

    #LLMs are a distraction & he misses imo a big point.

    #emacs allows you to uniquely configure it to your needs, to suit your worflow

  5. @benjamineskola @tusharhero @oatmeal

    #LLMs are a distraction & he misses imo a big point.

    #emacs allows you to uniquely configure it to your needs, to suit your worflow

  6. @benjamineskola

    Yes I mean chown.

    For some odd reason my usage of chown gave only warnings the past few years when I used the current 21 year old syntax.

    Thank you for the correction and Enlightenment

    #chown
    #chmod #syntax #formatting #command #Linux #BSD

  7. @benjamineskola

    in either case, previous versions remain available.

    Correct. Even if the controller of the public #git repo takes it down without warning, the community can still fork the project based on the local copies of the repo that various people have lying around.

    It seems to me like the core problem is not about using a copyleft licence or not, but about assigning ownership.

    It's both. If you have #permissive licensing or copyright assignment (or similar), then one entity can take their ball and go home, closing all future versions that they make. If you have #CopyLeft and you don't have copyright assignment, then they can't.

  8. @MutualityWSDEs @OliverNoble @Stevenheywood @benjamineskola @Loukas

    And there he is! He's finally exited his far left closet! 😂😂😂😂

    My colleagues are in contact with that #Gooners blog to fully unmask you! #Cuz #Fam #Blud😎

  9. ben @benjamineskola ·

    RE: ec.social-network.europa.eu/@E

    This is good as far as it goes but is still non-binding. Disappointing if that’s the best they can do.

  10. Fingerprint scanning on Linux seems very unreliable. I have it set up, and it can definitely recognise a fingerprint and authenticate based on that, but there seem to be far more false negatives than I’m used to.

    Can’t tell if this is the fault of #fprintd or if the #thinkpad fingerprint reader is just less reliable than the ones in macbooks, or what.

    (Seems to occur cross-distro: #debian mainly but was no better in others.)

  11. Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.

  12. Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.

  13. ben @benjamineskola ·

    Every changelog autogenerated from a commit history using is its own argument against ‘Conventional Commits’.

  14. Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.

  15. Every changelog autogenerated from a commit history using #ConventionalCommits is its own argument against ‘Conventional Commits’.

  16. Trying out #aerc and I want to like it (it has some fancy feature like embedded terminal etc) but there are some weird behaviours that don’t seem quite right. Sorting the way I want seems impossible (whether I do `sort date` or `sort -r date` it always appears to be reverse-chronological, not chronological; `sort from -r date`seems close to what I want but is inexplicable); and threads get reorganised on every delete so if I read through a thread and delete messages as I go, it might suddenly decide that the next message is actually one from a different thread.

    I used #mutt back in the day and I see #neomutt has imap support now, so I’ll be giving that a try next.