search

monero-ecosystem / meta

General management, info and governance of the Ecosystem project
https://moneroecosystem.org
34 stars 3 forks source link

Add: go-telegram-monerotipbot #61

Closed omani closed 5 years ago

omani commented 5 years ago

hello folks,

here it finally is: here is https://github.com/omani/go-telegram-monerotipbot from the successfully fully funded CCS proposal.

the repo is empty. and I will push the code as soon as we moved this (empty) repo to the ecosystem. I do this for operational reasons and Im sure you all understand why.

The final go-telegram-monerotipbot pointing to the monero-ecosystem (URL) will be placed into the README and START notification of the bot (in telegram you see a start message when you start a bot).

The bot is going live (mainnet) tomorrow (sunday) at 9pm UTC. I am glad we finally found a trustfully member of the community who will host the bot and who wants to remain anonymous (for obvious and understandable reasons).

Thank you all for all your support.

cheers! sun

erciccione commented 5 years ago

I will push the code as soon as we moved this (empty) repo to the ecosystem

@omani this would mean that the Maintainers would have to blindly vote to add a project which we cannot see. This is not a feasible approach. Please push the code first. What's the issue with pushing the code to your repo and then transfer it?

wants to remain anonymous (for obvious and understandable reasons).

This is unrelated to the discussion about adding the project, but i want to point out that i don't know if people will use the bot, knowing that somebody they don't know is holdingfor their money. I for example, would never use it with these premises. It's also true that anybody can build their own tipbot, but i don't know how many people will use the "original" version.

omani commented 5 years ago

@erciccione the reason to add a project which we cannot see is the timing. the monerotipbot is going live today and we wanted to avoid appearances of copies on telegram before 9pm UTC today.

and to your last point. yes I fully agree and what you said there is absolutely the way it should be: ideally everyone who wants to operate this bot in their own group can do so by running their own instance. what I was trying to do here was to protect the spoofing of the "official" one already existing on the telegram BEFORE the launch (switch to mainnet) today.

omani commented 5 years ago

actually, when I think about this, this approach doesn't make that much sense. I want the people to use their own bot anyway. so why this avoidance of something.

I will push the code and start new.