302
submitted 6 months ago by jokob@lemmy.world to c/selfhosted@lemmy.world

After thinking for about a year about it I decided to rename the project to 🚀NetAlertX. This will help prevent confusion about which fork someone is using, and differentiate it from the now stale upstream project. With about 1800 or so commits over the stale project, I thought, this project deserved a new name. It will also remove the confusion about only supporting Raspberry Pi's 😵

On top of the rename, I implemented ✨unlimited icons - just find an SVG you like and use it 😄.

The rename from PiAlert to NetAlertX should be pretty straightforward and existing setups should work fine, no manual migration steps should be necessary. Still, caution is recommended.

Check this https://github.com/jokob-sk/NetAlertX/issues/633 thread for edge-cases and the guide https://github.com/jokob-sk/NetAlertX/blob/main/docs/MIGRATION.md if you decide to change your docker-compose.

you are viewing a single comment's thread
view the rest of the comments
[-] jokob@lemmy.world 14 points 6 months ago* (last edited 6 months ago)

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

[-] ikidd@lemmy.world 4 points 6 months ago

OK, sorry to discourage you, it wasn't my intent. I updated to FF 125 during my evaluation and that didn't fix anything, but switching to Chrome and things started working made me think this is just another project designed for Chrome. I've tried to help on projects like that and the attitude I've always gotten back is "then use Chrome like everyone else, weirdo".

I used to project manage a programmer team, and UI is the biggest user complaint I would get hit by. So I'm pretty sensitive to non-intuitive UI design. At this point, I'd rather edit the conf file than use the Settings page. Not sure how to reload that conf file other than to restart the container.

I wish I had time to spend on this submitting actual code, because I like a lot of what I see. Best I could do is add to your list of todo's by creating issues and it sounds like you have plenty on that list already. If you want a couple more, open the spoiler below. In any case, have fun on your project and don't let assholes like me bring you down.

spoiler

  1. Remove Last: this isn't great. A selectable list with Edit and Delete buttons is more usable and standard. I saw all those Remove Last buttons throughout the Settings, and it's not much better than Remove All if you have to delete every entry after the faulty one to fix your list. There's plenty of settings that have a dozen items in the list that would all have to be re-entered manually as text.

  2. Dropdowns pre-validate input. Making a box that you can put random additional arguments into means you have to chop up the input in arguments to validate, or maybe you aren't validating it until you press Save, in which case you're making it even tougher to validate the entire file. You can only show items in the dropdown that are valid for that input. Several pages of docker virtual interfaces and named networks is probably not what you want in the dropdown. Eth0 is not a standard interface name anymore in most distros.

  3. That bulk-editing workflow; so I pick items on one page, why would I expect that they'd be carried over when I go to a completely different page in another section of the application? And in that section, there's nothing to indicate that clicking on the gray bar in the middle of the warning text orange box would pop up the list of devices so I can do things with them. What I typically see in things like this is checkboxable list items and a toolbar or menu at the top of the list on the Devices page to perform actions.

[-] jokob@lemmy.world 3 points 6 months ago

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 😉

this post was submitted on 20 Apr 2024
302 points (97.5% liked)

Selfhosted

39677 readers
186 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS