lyrenhex / verum-cli

Command-line client for Verum.

Hey 👋

😄 Pronouns: he / they

I'm a software developer at Arm and an undergraduate Computer Science student at the University of York. You're welcome to read more about my professional work at mheaton.dev. Otherwise...

Personal projects

You might know me from some of the projects I maintain:

• twedia, a music management solution for Twitch streamers (why?);
• eos, a progressive web application (PWA) to help track mental health and provide resources;
• the covid19-uk-rs library to interact with the 'Coronavirus in the UK' dataset using Rust bindings;
• or others! I have plenty more archived projects that I worked on and learned from. ⚡

Other than maintaining existing projects, most of my work at the moment is likely to be for university or open-source work in Arm.

(Your friendly reminder that any opinions are my own. Cheers!)

verum-cli's Issues

Blocking

For a system as "open" as Verum (despite there not being a central user directory), spam will likely become an issue later on. Verum Nodes should, by definition, not actively censor, and thus should not be responsible for the censorship of blocked messages. This leaves the task of block handling to the Verum clients.

Verum-CLI could handle this with a new block action, like so:

$ verum-cli block <verum id> which would block verum-id, and messages from this user would not be displayed.

There should therefore be two additional commands:

$ verum-cli blocked to list the blocked users, and
$ verum-cli unblock <verum id> to remove the verum id from the block list.

Groups

This is a fairly simple idea for grouping people.

In order to avoid constantly resending the same message to numerous people, Verum could support internal groups, which would operate like mailing lists. Users could create a group with verum-cli group <group> [action] [user] [user] [user].... If action is omitted, a new group with the name group would be created, with any users specified as members. action would support modification commands, such as add, remove, etc.

Then, when a user wishes to message a group, they may simply do verum-cli sendmsg <group> <message>, where group is the name of the group. Verum-CLI would identify that the recipient does not have a Node address (no '@' symbol), and assume the user is referencing a group. For each member of the group, it would then send a message thus:

<message> // as defined by the user

This is a group message, sent as you have been placed in <sender>'s <group> group.
You may ask to be removed, or block the user, if you do not wish to receive these messages.
The following people are members of this group: <list of fellow group members>