cmaster11

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

I've been using Code for half a year, these past couple weeks have been a totally different experience I'm on max 20, and seeing my weekly quota going bust in ~3 days is a bit absurd when nothing has significantly changed in the way I work

For whoever else is having the same problems, worth voting these kind of issues. There needs to be more transparency over what goes on with our subscriptions.

The app currently operates on the locale of your browser, so it will adapt the events naturally to the local time. The countdown will be based on your local timezone

I built this web app a couple of years ago because I always need to know what meetings are coming up, and I've never found a satisfactory solution. So, a web app that throws countdowns at me, as well as playing ping sounds/flashing the screen when meetings are approaching. Free as of now.

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

Hi, Notify17 author here :)

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#... ).

Hi! Thanks for the notice, is this error still happening?

Thanks a lot! Hope you can find even more useful features in Notify17! ;)

I'm sorry, I must have explained myself badly earlier.

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.

Eheh well, self-promotion is kinda vital for who makes his own product! ;)

Question, how was using Scala on Android? :O

Hi!

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!

Yeah, KDEConnect is nice too :)

Notify17 is more of a SaaS for who desires an immediately ready system to generate notifications.

Answer from another comment: https://news.ycombinator.com/item?id=19937017 reply

:)

Yes, I'm aware at first sight, for non Golang users, it may look a not-so-friendly syntax, but Go templates are just too powerful to not use them :D

Thank you a lot, it has been a long journey, and seeing your own product coming out it's and indescribable feeling XP

Best of luck to you too!!! If you want to keep in touch, feel free to mail me at alberto@notify17.net :)

Weeeell, it's in the planssss :D :D :D Happy to let you know, when it will happen in the future!

I am finding out more and more they're not competing products: https://news.ycombinator.com/item?id=19937017

Done that too :)

But then, when you need templates, and send payloads from webhooks, there it gets messy..

I made Notify17 exactly to avoid that mess :D

There are no processes running in the background in this app (apart from a periodic check every 10 minutes for new notifications, which lasts very few seconds). I use it all day long and never have issues with battery, because the CPU is used only when it receives a new notification.

No, this free forever is meant to stay and get bigger in the future.

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 :)

Thanks a lot!!!

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.

Cool!!

You can access arrays with `{{ index .myArray 0 }}` ( https://notify17.net/docs/templates/#arrays ). Notify17 uses golang templates :)

Yes, I understand the point there :) I will add it to the list of features, because I can see a biiig market there :D

Hi, yes it will in first place rely on FCM. I already thought to have a second variant which would be independent. If you're interested, let me know :)

Compared to pushover, Notify17 is conceptually easier to set up and first-use (meaning, you create an account and you can already test notifications). I didn't like the not-so-immediate concept of pushover.

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.

Hi, I'll copy the same answer from a previous post ( https://new.reddit.com/r/devops/comments/bmujjg/made_a_new_n... ):

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.

Thanks a lot! :D

Thanks a lot for the wish! I hope many will find this tool useful :)

The pricing for the moment is intentional. My first category of end-users and single customers.

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.

It's just for beta testers, meaning this will be temporary (3 months for now, with good chance it will be renewed or made permanently). The biggest challenge here is determining what a good number is for a free tier, to help small users properly and not impact on the business for bigger ones.