notifo VS neo

There’s a bunch of communication software listed there. notifications Looks like the only C# one for custom communication software.

I am working on notifo, a notification service: https://github.com/notifo-io/notifo

Nice article. Very strange that I have not discovered your product earlier. I have built something myself at https://github.com/notifo-io/notifo, but I would have never done it if I would have seen your solution. Just trying it out now.

I cannot prove it, but there is no business value in improving the performance. The company and me are basically the same and I have no employees, I work as a freelancer and mjml has been built for another Open Source project, where I don't make money with: https://github.com/notifo-io/notifo.

Btw: I created my own notification system: https://github.com/notifo-io/notifo, I followed this principle:

I am working on a server to publish different kind of (push) notifications like mobile push, web push, email, sms and so on: https://github.com/notifo-io/notifo

I have build a notification server: https://github.com/notifo-io/notifo ... My goal is to test all the different channels in the CI, e.g. email, webhook, messaging and so on.

I am working on Notifo since a while: https://github.com/notifo-io/notifo

Neo (3400 GitHub Stars) https://github.com/neo-project/neo

Some discussion that covers many of the arguments on both sides here: https://github.com/neo-project/neo/issues/2118

Take a look at something like https://github.com/neo-project/neo or https://github.com/Felandil/tangle-.net to see how much work is really required just to get something basic up and running.

Yes, this was a topic of considerable debate during N3's development. The degree to which one considers it a serious issue really depends on what one sees as the key features of governance--stability vs. democratic expression, etc. Of course, the basic fact of a node falling out of the top 21 isn't weird; the question is more around how easy it should be to get back in.

It's good discuss the voting mechanism and other aspects of NEO. Have you seen the comments on GitHub? A lot of people and devs (also people ^_^) are there, for example: https://github.com/neo-project/neo/issues/2598

One, there has been quite a bit of discussion over the past year about the design of the new governance system, and its potential flaws with respect to promoting node turnover--e.g. here, but also at various times in this sub (sidebar, you'll see that your "votes are reset" idea was proposed in that thread, say). As an oversimplified TL;DR, I think many--myself included--would agree with you that the system tends to promote the status quo. Where things get muddy is whether that's a feature or a bug. For reasons of both regulatory compliance and stability, the Neo team has intentionally designed a system where turnover, while possible, isn't specifically incentivized; that is, in their view it should happen because there's a strong, governance-related reason for it, not because of financial incentives.

The governance model has been designed to incentivise stability while still allowing flexibility. However, the issue you raise is already being discussed on GitHub here: https://github.com/neo-project/neo/issues/2598