• lime!@feddit.nu
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    from the overview i can’t really tell what it is, although it sounds like onenote, which i’ve never really gotten along with. also yeah, the online requirement thing means it’s not suitable for secure work.

    • Kevisthename@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      Hey- Thanks for the feedback. You’re right about the lack of overview or clear purpose- I’m aiming for more of a “just type and share instantly” kind of thing. At the end of the day, I guess what I want to know is- what could this be used for, you know? I might have one idea, but I could be wrong.

      Curious- and it may sound basic but I don’t wanna assume- is offline use important for you mostly because of security or something else (travelling/using hotel wifi, etc).

      • lime!@feddit.nu
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        2 months ago

        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.

        • Kevisthename@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          Wow! This is great stuff! Really appreciate you taking the time to lay this out.

          I get your point: in high-stakes, security-conscious environments like yours, needing a persistent internet connection is a non-starter. Your two conditions (sync only on verified safe networks + trusted server endpoints) are a clear, actionable framework I hadn’t articulated so well before-thank you.

          Cheers for calling out the muddiness around purpose. I started this as a tool to scratch a personal itch, but I’ve been deliberately open-ended in trying to understand where others see value. Still, the lack of clarity does become friction-especially when account creation is required up front. I’ll be rethinking that flow and messaging.

          Also noted (and agreed) on the accessibility issue. I’ll fix the <button> vs <a> problem-thank you for catching that.

          what would a deployable/self-managed version for an environments like yours look like?

        • Kevisthename@lemmy.worldOP
          link
          fedilink
          arrow-up
          0
          ·
          1 month ago

          Hi! Just circling back here- what does this mean? I’d like to action it: “Page is missing basic accessibility features” - Can you provide more detail on location perhaps or just more info in general!

          • lime!@feddit.nu
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            1 month ago

            basically this

            in short,

            • semantic html (<nav>, <main>, <aside> etc). ban use of <div> unless there is no fitting tag.
            • aria roles (which you will need less of with semantic html)
            • logical grouping, which facilitates
            • structured text that flows in a screen reader
            • never ever ever use <button>s instead of <a>nchors for links unless you have a very good reason.

            also, don’t use the wording “circling back” unless you want people to get office ptsd.