SpringNet v0.3.0 Release – Protocol update and bug fixes
This slightly delayed 3-week-cycle release is pretty boring and brings in the protocol changes that enables multiple responses to be combined effectively into a stream of responses, with a ‘service/multi’ header and an End of Transmission response code to complete the stream. This is technically a cleaner approach compared to using delimiters as it locks the size of a chunk to a size instead of a special sequence of characters used to end a response, thus allowing any sequence of characters to be in the chunk without having to escape them. It also makes the stream data format agnostic. This protocol update makes breaking changes to previous version of the plugin.
SpringNet v0.2.0 Release – Categories, Widget and more
This 3-week-cycle minor release makes the bulletin service more powerful by introducing categories. With categories, the bulletins can be rapidly sorted into relevant groups enabling a user to quickly find the information they need on the network within their area. As demonstrated on our frontpage, we can view all bulletins that provide information about events or services while filtering out the ones that we’re not interested in.
Included in the release is the widget `Explorer` that enables this category exploration. Neater interface changes mean clicking on a node URI automatically opens a popup with their profile.
Another addition to the system is the ability to get a node’s certificate with a given URI which can then be used to import into the keyring. This feature is found under Keyring > Import. Finally, a pull request of a certificate can be made once it is signed, allowing distribution of updated certificates across the network. This feature can be found in Keyring > Certificate.
Note: Patch release 0.2.1 was made shortly after the 0.2.0 release which made a critical fix — the new Explorer widget lacked a public facing gateway, resulting in a situation where only administrators could us it. This has been fixed, along with a couple of minor styling issues.Posted October 19, 2016 2:02 pm by springadmin
WordPress Native Node
As the software has progressed for the web based node, it seems quite possible to have a version of the node running purely as a native WordPress plugin. This differs from the current WordPress plugin which allows you to connect to and manage your node running on a separate domain or subdomain. With the aim to make Spring as accessible as possible on a technical level, having a plugin like this really builds toward that aim by making the installation of the software and connecting to the network even easier! As a bonus it removes some load off servers because an external request is using the WordPress installation directly as the gateway, instead of bouncing off to another server before accessing the internal network.
With that in mind, this week we’ll be researching how to go about strapping a Spring network node directly into the back of a WordPress powered site and hopefully have some alpha build plugin in the next few of weeks.
It is looking very possible to strap the node software into the back of WordPress!Posted September 19, 2016 11:03 am by Charlie Fyvie-Gauld