pull down to refresh

By the way, I only recently noticed the existence of @CHADBot here on SN #1075719. Didn't realize there were bots here, at least not the ones that post.
So it got me thinking if I could create a Bitcoin Calendar Bot for SN. The reason for my interest is two-fold:
  • I believe the community could (more often than not) benefit from having historical Bitcoin events to discuss – such events often help us learn from history, meaning we may avoid future traps the world is preparing for us.
  • This community is like no other and I am sure Bitcoin Calendar project would benefit from the collective knowledge of SN plebs. In fact it already had more than once: #942058, #947707, #947887
What do you say, @k00b? Who's blessing do I need to get and where can I start if I go for it?
42 sats \ 2 replies \ @ek 18h
Thanks for your interest! We have API keys but since our resources are limited (don't want to become bot support, fight against abuse etc.), we enable them for accounts on a case-by-base basis for now.
I like your idea! I will get back to you regarding this within four weeks, if not earlier. We still have some important stuff to finish before we can start to think about handing out new API keys or even API key access by default.
@remindme in 4 weeks
reply
100 sats \ 1 reply \ @Tony OP 18h
Thanks a lot for your reply! It’s actually good that I’ll have another month to polish a few things.
I’ll also be happy to adjust the publications to best fit Stacker News instead of posting everything I gathered in the database — while I’m working on having as many milestones and Bitcoin related events documented as possible, I understand that not all of them will be beneficial for SN community.
Thanks for your work and looking forward to your reply.
P.S. sorry, didn’t notice the API info - checked FAQ and decided that the best way was to tag k00b and ask directly.
reply
21 sats \ 0 replies \ @ek 17h
P.S. sorry, didn’t notice the API info - checked FAQ and decided that the best way was to tag k00b and ask directly
no worries, good point regarding the FAQ, we should probably mention it in there somewhere
reply