301
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 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
301 points (97.5% liked)

Selfhosted

40183 readers
527 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