• 0 Posts
  • 64 Comments
Joined 9 months ago
cake
Cake day: August 21st, 2024

help-circle
  • i’m glad you’re taking it as intended, i was worried about my tone…

    a version that could be used in a restricted setting would

    • be offline-first (or online-optional, even)
    • install and work with minimal privileges (no curl|sudo bash)
    • have few to zero external dependencies that need vetting (to get past IT)
    • send and store very minimal amounts of data off-device (especially important for PII like user accounts)
    • use only audited and proven crypto and auth (because nobody should be rolling their own there)
    • allow bring-your-own-database setups for the server (because some places run the same DB software for everything)
    • play well with other tools on a posix system, e.g. make sure data files are structured text rather than binary (for future-proofing)
    • if running in a browser-based environment, preferably work without scripts enabled (to eliminate XSS risks)
    • if running in a native environment, be open and reproducible (so builds can be verified)
    • keep to itself; e.g. make sure to keep stuff in its own namespace and not spread files around (for the server this is usually accomplished by containerization but not everyone allows running stuff like docker)


  • I work with governmental organisations and heavy industry. spotty internet, data privacy, changing laws, cleanroom areas, IT audits, travel to places with less savoury governments, telemetry that shouldn’t be stored but is due to some flag someone forgot, takeover of the server, ulterior motives, you name it. needing a network connection means it has to be assumed compromised, and short of letting my IT dept host its own version, you can’t convince me otherwise. I need to be able to 1) sync data only when on a verified safe network, and 2) trust the server that data goes to and from.

    when it comes to what something could be used for… are you doing market research, or basic research? building a tool usually means you have a need for that tool. If you’re trying to market something, do a proper test with a control group. just going “i made a thing, i don’t know what it’s good for” isn’t going to pull in crowds, especially if there is a barrier such as account creation to actually use the thing.

    Edit:

    also, your page is missing basic accessibility features. all the links are <button>s, not <a>s, so they’re not properly picked up.




  • lime!@feddit.nutoProgrammer Humor@programming.devRelatable
    link
    fedilink
    English
    arrow-up
    1
    ·
    27 days ago

    i think that’s just a fundamental problem with designing magic systems though. if you design it logically, it doesn’t feel like magic. if you design it by feel, it doesn’t make sense. if you want it to feel magic but still be tricky to learn, it becomes a mess.

    in the context of minecraft mods there’s also not much you can do.









  • lime!@feddit.nutoLinux@programming.devThe Wizard and His Shell
    link
    fedilink
    English
    arrow-up
    10
    ·
    edit-2
    1 month ago

    but like… none of this makes the terminal more powerful.

    something like the Arcan lash/cat9 shell is a massive leap forward in terminal technology that may potentially completely change how we use it. it does this by understanding what makes the terminal productive: pipelining, batch processing and scripting.

    meanwhile this is just… a skin.






  • the main thing is that the system end-users interact with is static. it’s a snapshot of all the weights of the “neurons” at a particular point in the training process. you can keep training from that snapshot for every conversation, but nobody does that live because the result wouldn’t be useful. it needs to be cleaned up first. so it learns nothing from you, but it could.