WapSNMP is an SNMP client library for Go. It allows you to query SNMP servers for any variable, given its OID (no MIB resolution). It has been written to be in the Go style, which means it should be very resistant to all error conditions. It's entirely non-blocking/asynchronous, very fast, and will timeout, not block. It's also surprisingly small and easy to understand. It supports SNMPv2c or lower (not 3, due to its complexity), and supports all methods provided as part of that standard. This library works with OIDs and does not support OID-to-name translation.
form is a library designed to allow seamless, high-fidelity encoding and decoding of arbitrary data in application/x-www-form-urlencoded format and as url.Values. It is intended to be useful primarily in dealing with Web forms and URI query strings, both of which natively employ said format. Unsurprisingly, form is modeled after other Go encoding packages, in particular encoding/JSON, and follows the same conventions (see below for more.) It aims to automatically handle any kind of concrete Go data value (i.e., not functions, channels, etc.) while providing mechanisms for custom behavior.
Weed-FS is a simple and highly scalable distributed file system. There are two objectives: to store billions of files, and to serve the files fast! Instead of supporting full POSIX file system semantics, it implements only a key-file mapping. Instead of managing all file metadata in a central master, it manages file volumes in the central master and lets volume servers manage files and the metadata. This relieves concurrency pressure from the central master and spreads file metadata into volume servers' memories, allowing faster file access with just one disk read operation. It is modelled on Facebook's Haystack design paper. Only 40 bytes of disk storage are required for each file's metadata, and disk reads are O(1).
filegive easily sends or receives files point-to-point, with authentication and ciphering, and the other side only needs a Web browser. No third party server is involved in the transfer. It can use common NAT traversal protocols like uPnP and NAT-PMP, manually forwarded ports, or a public ssh server.