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/)J

jokob

@ jokob @lemmy.world

Posts
3
Comments
14
Joined
3 yr. ago

  • NetAlertX - Network presence detection now with workflow automation 🔀

    Jump
  • Removed

    NetAlertX: Lessons learned from renaming a project

    Jump

  • Which distro?

    Jump

  • I switched to it also because my debian host got out of date and now it's difficult to upgrade and I'm scared to reinstall it. If it was NixOS I would be able to redo the whole thing in a few minutes. So I'm creating / learning how to create a template to roll it out to my other builds.

  • Which distro?

    Jump

  • I just installed NixOS and the repeatability of it is pretty neat. I like the idea of having one file that sets up 90% of any pc going forward. Not sure how often I'll use it, but feels neat.

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Oh cheers a lot, doing what I can! Messages like this make my day so much better. Trying to stay positive and move things forward. 👍

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • I know it's not perfect, but hopefully this will improve the editing experience a bit:

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Thanks for the constructive feedback.

    1. I'll keep thinking how to improve the interface selection to simplify the first-time setup. It's a bit lower on my priority list, but the suggestions are valid.
    2. I'm trying to balance configurability and ease of use and so far the current input is OKAY - it limited the number of wrong setups significantly and it still gives options to include additional arguments. But fair point of having more robust input validation. In general, the initial configuration UX, although very important, is less important than day-to-day tasks so I prioritize accordingly. Still, there is lots of to improve and if this was something that made me money I'd be able to spend more time on the niceties - I'm really focused on the core functionality at this point with approx a 80/20 time investment split.
    3. I didn't have any feedback on the workflow yet, but I'll keep this in mind to make it more user-friendly. Once you select the devices they are pre-populated in the grey area so I didn't get any feedback of it being counter-intuitive.

    Still it's weird you had issues on FF as I use it as my main driver. 🤔

    Thanks again for the feedback and if you can, please submit an issue for quick UX improvements here-and-there. Again, trying to balance where I spend my time to improve the app 😉

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Hey, thanks for trying out NetAlertX.

    I'm using FF as my primary browser so not sure about why your experience is so different.

    I think I've done alright, writing an app that is configurable via json manifests, dynamically loaded settings and a plugin system everyone can contribute to.

    There are of course things to improve, and almost everything listed in your post is something on my long to-do list. It's very easy to find flaws in things, but what's more difficult is to contribute to the community and improve things.

    So if you are up for a challenge - open a PR and help me improve things step by step.

    Thanks in advance if you decide to help out! Otherwise, comments like these make free open-source work unenticing🙏

    EDIT: Fixed the empty settings (hopefully), added a remove last button on the subnets setting.

    Oh also - there is a well documented bulk-editing feature: https://github.com/jokob-sk/NetAlertX/blob/main/docs/DEVICES_BULK_EDITING.md VLANS are documented here: https://github.com/jokob-sk/NetAlertX/blob/main/docs/SUBNETS.md#vlan-example

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • 😅

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • Open an issue and I will help out

  • Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

    Jump

  • I was thinking about that sooo much, but difficult to find a free domain for networking-related projects. I think I delayed the rename by a month because I couldn't decide. So yeah, I am not the happiest about the X at the end myself, but I also don't have that much money to get a proper domain, so NetAlertX it is :)

  • Selfhosted @lemmy.world
    jokob @lemmy.world

    Pi.Alert is dead...💀 Long live NetAlert X 🚀 (network monitoring)

  • Selfhosted @lemmy.world
    jokob @lemmy.world

    Half a million pulls celebratory post: Pi.Alert: 💻🔍 WIFI / LAN network monitor and notifications