in reply to RFC: new module WebService::Discord::Webhook

Bad name. You wrote a client, yet you name it service. That's super confusing.


holli

You can lead your users to water, but alas, you cannot drown them.
  • Comment on Re: RFC: new module WebService::Discord::Webhook

Replies are listed 'Best First'.
Re^2: RFC: new module WebService::Discord::Webhook
by jcb (Parson) on Sep 04, 2019 at 02:55 UTC

    To make this even more confusing, a "Web hook" is usually a URL on your server that receives requests as a result of events somewhere else. Discord is using the term almost completely differently to refer to an HTTP API for posting notifications to Discord chats, instead of a mechanism for receiving events from Discord at some chosen URL.

    Unless Discord intends for these API URLs to be set as "Web hooks" in other services and produce notifications in a Discord chat?

    I would suggest a name more like WebService::Discord::Notifier.

Re^2: RFC: new module WebService::Discord::Webhook
by hornpipe2 (Sexton) on Sep 03, 2019 at 19:33 UTC
    Haha. The one comment I've gotten on Reddit was to change the name to this (from Net::Discord::Webhook) - the PAUSE guide recommends using either WWW or WebService when referring to modules that interoperate with a web-based service.

    Two hardest problems in computer science, indeed...

      Yeah well, then, just append append something to furher qualify the real nature? Ideas:
      WebService::Discord::Webhook::(Client|Interface|Call|SendTo)


      holli

      You can lead your users to water, but alas, you cannot drown them.