Thank you for your responses, especially on a Sunday. They give us some insights and at least a couple temporary workarounds to use, while the issues are being addressed :) much appreciated
316 karma · joined May 17, 2019
I always have multiple screens around, and I dedicate a vertical panel to this app.
Lately, I've upgraded it to also support booking rooms by querying for free rooms and "fast booking" them depending on a custom priority list. I have a personal use case for this one: even periodic meetings don't have assigned rooms, so I can just bulk-book the first available rooms for the next couple of weeks for every meeting that does not have an associated one.
I hope this app can help others find some help for their corporate lives, as it did for me :D
I just wanted to point out that there is not a single part of the flow which is not encrypted at rest, and, apart from text-processing areas, in transit.
All user-content arguments sent to the hook endpoints (to generate notifications) are obscured for the whole flow of the notification generation. Which causes trouble when trying to debug issues, but oh well, I believe privacy is more important than anything else in this context.
I dream for this tool to be used by devops people (I'm mainly one of them!), so I value the privacy element in this project above all. It happens that I end up asking users "what the hell did you type there to break things to much" :D
For the matter of logs, I'm so happy about having used Go for this project, because I can mask fields here and there nicely (e.g. https://github.com/cmaster11/structs/blob/master/structs.go#... ).
Notify17 and Pushover share some competing features, clearly, because both are notification services. From that point of view, there can be competition, no discussion about it.
At the current moment, however, I feel they have different visions. I want Notify17 to be, at least in its initial phases, a personal/small team tool, more than a mass distribution one. I want user to personalise their notifications, and integrate Notify17 in their workflow. More than targeting 10s of thousands of notifications to huge groups, I imagine more single users or small teams creating their own templates world.
I'm not excluding that, as Notify17 will grow, it could become a competitor of Pushover. Especially when the alerting features will grow and improve. They're just targeting, in my pure opinion and for this initial growth phase, a different user base and a different vision.
Question, how was using Scala on Android? :O
You're not the only one reporting this error, I'll look into it as soon as possible :)
Android client is in active development, but I'm afraid I cannot exactly predict when it will be ready. I prefer to not give in this context an esteem which could be wrong, sorry for this. :)
P.s. thanks a lot!
Notify17 is more of a SaaS for who desires an immediately ready system to generate notifications.
:)
Best of luck to you too!!! If you want to keep in touch, feel free to mail me at alberto@notify17.net :)
But then, when you need templates, and send payloads from webhooks, there it gets messy..
I made Notify17 exactly to avoid that mess :D
This post is talking about a way much bigger plan for beta testers, which I want to keep going in the future too.
There will always be a free forever basic plan, because I'm a developer myself, and I know how much I do hate services that ask you for the CC when creating an account :)
Actually, for the website I relied heavily on antd ( https://github.com/ant-design/ant-design/ ) for the design. I cannot really say how long it took because it's always been developed alongise the backend.
Aaaand yes, I LOVE golang, even more after creating Notify17 using it. The clarity of that language is impressive.
You can access arrays with `{{ index .myArray 0 }}` ( https://notify17.net/docs/templates/#arrays ). Notify17 uses golang templates :)
I belive Notify17's UI is friendlier for users, less cluttered. Clearly Notify17 has less features overall (for the moment), because it focuses on few core concepts, which are simple notifications ( https://notify17.net/docs/api-endpoints/#raw-notifications ) and notification templates ( https://notify17.net/docs/templates/ ).
The two products have two distinct philosophies. At the time I evaluated pushover, I thought it was too enterprisey, not suitable for simple daily usage. Therefore, I tried to create a friendlier service :)
The tradeoff, for the moment, is probably less features overall (you can see a list of features here: https://notify17.net/docs/features/ ). The benefit is that you have a UI that lets you manage your content (in my opinion clearly) way far more easily than with pushover.
Amazon SNS is not a competitor of Notify17 in first place, because SNS is a general purpose publish-subscribe system, while Notify17 is a solution that accepts HTTP payloads, and processes them to generate notifications, which you can see in a web browser or on the iOS app (in future also Android one). They're conceptually a lot different.
Because of this core difference, I cannot say there's any plan to compete with SNS.
I originally envisioned Notify17 to be a personal hub, more than an enterprisey tools (in the beginning clearly. If business grows, sure the model will change).
I'm not trying to compete on tools like PagerDuty, which already do their jobs very well. For now, Notify17's main goal is alerting/reporting on a smaller scale.
From a startup perspective, the team is building up, it's in a phase where the main features are working, it's no more a prototype (backend/iOS), but how users will want to use the product is still a question (therefore the call for beta users). I want to have a solid set of features that I know users will use before trying any big jump.