#Tag
To be able to index #reaction on the awesome-rust list, it must have > 50 stars. Well, 50 stars on framagit and 50 stars on github are far from equivalent, but it should be feasible! It already has 34 stars. If you have an account on Framagit, would you star it?
➡️ https://framagit.org/ppom/reaction
Boosts welcome!
#reaction #reactionrust #framagit
To be able to index #reaction on the awesome-rust list, it must have > 50 stars. Well, 50 stars on framagit and 50 stars on github are far from equivalent, but it should be feasible! It already has 34 stars. If you have an account on Framagit, would you star it?
➡️ https://framagit.org/ppom/reaction
Boosts welcome!
#reaction #reactionrust #framagit
To be able to index #reaction on the awesome-rust list, it must have > 50 stars. Well, 50 stars on framagit and 50 stars on github are far from equivalent, but it should be feasible! It already has 34 stars. If you have an account on Framagit, would you star it?
➡️ https://framagit.org/ppom/reaction
Boosts welcome!
#reaction #reactionrust #framagit
After a lot of researching and thinking, I finally started coding reaction's (upcoming) plugin system!
It will permit to write custom stream, filter and action logic, in Rust.
It'll make use of stabby, a crate easing the definition of a stable ABI in Rust, thus permitting reaction and its plugins to be compiled separately, at different times.
Roadmap: https://blog.ppom.me/en-reaction-v2/#plugin-system
stabby: https://docs.rs/stabby/
#reactionrust #reaction #rust #plugin #stabby #nlnet
(1/n)
After a lot of researching and thinking, I finally started coding reaction's (upcoming) plugin system!
It will permit to write custom stream, filter and action logic, in Rust.
It'll make use of stabby, a crate easing the definition of a stable ABI in Rust, thus permitting reaction and its plugins to be compiled separately, at different times.
Roadmap: https://blog.ppom.me/en-reaction-v2/#plugin-system
stabby: https://docs.rs/stabby/
#reactionrust #reaction #rust #plugin #stabby #nlnet
(1/n)
Two big new features:
- Full IP support (built-in regex, ip ranges, different actions on IPv4 and IPv6...)
- Options for action deduplication
See the release for a more detailed changelog:
https://framagit.org/ppom/reaction/-/releases/v2.2.0
Two big new features:
- Full IP support (built-in regex, ip ranges, different actions on IPv4 and IPv6...)
- Options for action deduplication
See the release for a more detailed changelog:
https://framagit.org/ppom/reaction/-/releases/v2.2.0
For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.
Question is: should I publish it as a separate crate?
For the needs of #reaction, I wrote a very dumb #Rust#KV db which wraps BTreeMaps and a redis-like log file for persistance.
It's orders of magnitude faster than common KV #database (heed/lmdb, fjall, sled) because it's RAM-first.
But it doesn't have transactions, and it persists write operations asynchronously, after the write is done.
Those features make a lot of sense for reaction imo, but I don't know if it would be useful to others.
Question is: should I publish it as a separate crate?
This is a more stable release than previous rc.
Admins are encouraged beta-test it before the first stable v2!
https://framagit.org/ppom/reaction/-/releases/v2.0.0-rc2
#reaction #rust #release
A space for Bonfire maintainers and contributors to communicate
