pinpon alternatives and similar packages
Based on the "network" category.
Alternatively, view pinpon alternatives based on common mentions on social networks and blogs.
-
compendium-client
Mu (μ) is a purely functional framework for building micro services. -
resolv
Domain Name Service (DNS) lookup via the libresolv standard library routines -
network-data
Network data structures in Haskell (IP, UDP, TCP headers, etc) -
windns
Domain Name Service (DNS) lookup via the Windows dnsapi standard library -
hatexmpp3
XMPP client with synthetic filesystem (9P) and (optional) graphical (GTK3) interfaces -
hsendxmpp
sendxmpp clone and drop-in replacement, sending XMPP messages via CLI -
LDAPv3
Lightweight Directory Access Protocol V3 (LDAPv3) RFC4511 implementation -
transient-universe-tls
Secure communications for transient-universe -
iwlib
A binding to the iw library for getting info about the current WiFi connection. -
network-uri-lenses
lenses for http://hackage.haskell.org/package/network-uri -
network-simple-wss
Simple Haskell interface to TLS secured WebSockets -
percent-encoder
A simple, fast percent encoder/decoder for bytestrings -
google-oauth2-easy
📛 Easy Google Authentication integration - Authorization Code & Refresh Token
Clean code begins in your IDE with SonarLint
Do you think we are missing an alternative of pinpon or a related project?
README
pinpon
pinpon
is a silly little service that implements an
Internet-enabled doorbell in Haskell, using
Amazon Simple Notification Service to notify
subscribers that the button has been pushed. Effectively, it's a
simple REST service which, when POST
ed to, will send a notification
to an SNS topic. You can then build a client application which
subscribes to that topic and notifies the user when the doorbell has
been pressed. No such client application is included in the pinpon
package, but an iOS app may be made available at some point in the
future.
The package provides a pinpon-gpio
executable, intended for use on
Linux systems with GPIO functionality. When the specified GPIO pin is
triggered (e.g., via a momentary switch such as
this one),
pinpon-gpio
will POST
a notification to the specified pinpon
server.
Why not simply build the Amazon SNS functionality into the
pinpon-gpio
executable and eliminate the pinpon
REST service?
Chiefly because the host system running the pinpon-gpio
executable
may be particularly vulnerable to physical attacks (after all, it is
presumably hooked up to a doorbell button that is exposed in a public
space). I did not feel comfortable storing my Amazon AWS credentials
on such a device, nor even allowing such a device to communicate
directly with the public Internet. By proxying the AWS access via a
more physically secure host running the pinpon
server on my internal
network, I can better protect my AWS credentials and limit network
access on the GPIO device to just the pinpon
service.