I license past and future contributions under Apache 2.0 license.

Although, AGPL-3.0 is great license for this kind of a project, it doesn't play well with current design and I want to allow certain companies to use it internally in near feature for e.g. perforce alternative with fully encrypted chat platform based on matrix.

ansi_term is Unmaintained

| Details | | | ------------------- | ---------------------------------------------- | | Status | unmaintained | | Package | ansi_term | | Version | 0.12.1 | | URL | https://github.com/ogham/rust-ansi-term/issues/72 | | Date | 2021-08-18 |

The maintainer has adviced that this crate is deprecated and will not receive any maintenance.

The crate does not seem to have much dependencies and may or may not be ok to use as-is.

Last release seems to have been three years ago.

Possible Alternative(s)

The below list has not been vetted in any way and may or may not contain alternatives;

• anstyle
• console
• nu-ansi-term
• owo-colors
• stylish
• yansi

Dependency Specific Migration(s)

• structopt, clap2

See advisory page for additional details.

Potential segfault in the time crate

| Details | | | ------------------- | ---------------------------------------------- | | Package | time | | Version | 0.1.45 | | URL | https://github.com/time-rs/time/issues/293 | | Date | 2020-11-18 | | Patched versions | >=0.2.23 | | Unaffected versions | =0.2.0,=0.2.1,=0.2.2,=0.2.3,=0.2.4,=0.2.5,=0.2.6 |

Impact

Unix-like operating systems may segfault due to dereferencing a dangling pointer in specific circumstances. This requires an environment variable to be set in a different thread than the affected functions. This may occur without the user's knowledge, notably in a third-party library.

The affected functions from time 0.2.7 through 0.2.22 are:

• time::UtcOffset::local_offset_at
• time::UtcOffset::try_local_offset_at
• time::UtcOffset::current_local_offset
• time::UtcOffset::try_current_local_offset
• time::OffsetDateTime::now_local
• time::OffsetDateTime::try_now_local

The affected functions in time 0.1 (all versions) are:

• at
• at_utc
• now

Non-Unix targets (including Windows and wasm) are unaffected.

Patches

Pending a proper fix, the internal method that determines the local offset has been modified to always return None on the affected operating systems. This has the effect of returning an Err on the try_* methods and UTC on the non-try_* methods.

Users and library authors with time in their dependency tree should perform cargo update, which will pull in the updated, unaffected code.

Users of time 0.1 do not have a patch and should upgrade to an unaffected version: time 0.2.23 or greater or the 0.3 series.

Workarounds

No workarounds are known.

See advisory page for additional details.

Some people may find it controversial but as we talked internally, it's just another layer of security and I plan to implement custom server lib with nanoserde for fast compilation.

More info on what is lunatic: https://lunatic.solutions

This also requires custom drivers for some databases:

• [ ] Scylla
• [ ] Supabase
• [ ] Firebase
• [ ] neo4j (for social graphs)

other popular ones like redis are ported already, not sure about RedisGraph.

Requires further testing:

• Apache Pulsar
• Apache Kafka
• Apache Arrow

This is second most important part of the network, right after login handler. It should be able to send mails, deliver scope-based notifs to clients etc.

Each service or clients itself may produce messages using multiple topics and dispatcher will have to decide which individual user or group should receive certain mesasge(s) or emails.

Each user registered in the network will receive unique Fólkvangr ID, it can be used as alternative login method if there are client tokens approved by the SysAdmin.

Warning: It should be used as internal login method for professional services and not something like twitter clone or other public social media.

~~stupid missclick sent empty message 🤦🏼‍♂️~~