Following https://keepachangelog.com/en/1.1.0/ and using
Added
for new features.Changed
for changes in existing functionality.Deprecated
for soon-to-be removed features.Removed
for now removed features.Fixed
for any bug fixes.Security
in case of vulnerabilities.
- reconnections should work better now, both for libc and wasm
- removed mdns calls, so it doesn't flood my home network
- re-arranged file names in the flmodules section, to better fit with the
template
module - changed the names of the networking messages
- added an
Overlay
module to abstract the network handling - more changes in names of the messages to remove ambiguities
- Updated versions of most dependencies
- use tokio::sync::watch to pass configuration from
Translate
toBroker
- re-arranged modules:
- removed flnet
- put all arch-dependant code to flarch
- replaced feature-flags "wasm", "libc", "nosend" with #[cfg(target_family="(wasm|unix)")]
- updated login screen in flbrowser
- flnet went into flarch and flmodules
- Create a template to fill out
- License files
- Devbox
- Create a proxy module that links to the html display
- Added a webproxy module to send GET requests from another node
- Add background processing of broker messages
- Re-arranging crates and publish
- Adding examples
- cleaned up for a release of flnet
- merged flnet-libc and flnet-wasm into flnet
- simplified directory hierarchy
- Moving stuff around to make it easier to understand
- Rewrite of networking layer
- Use real gossiped decentralized message passing
- Offer crates for using parts of fledger directly
- Rewrote big parts of the library and application to make it more modular
- Using thiserror::Error instead of String
- Added signature to the connection with the signal-server, thanks to Bolton Bailey [email protected] during the IC3 Hackathon
- More stable everything
- Clean up a lot of locking issues
- Fixing issues
- Add docker-compose.yaml
- Fix node Running
- Run some nodes constantly on https://fledg.re to have a minimum consensus
- Make the https://web.fledg.re a bit nicer and more automatic
- Simple ping test with the nodes
- CLI node using headless Chrome
- Have website https://fledg.re running and pointing to an up-to-date Fledger code
- add ICE connection through the server
- use websockets to connect to server
- implement connection in Node
- start the idea