Browse Source

Updates the readme to reflect the two new commands: [un]block

sloumdrone 3 years ago
  1. 11


@ -15,11 +15,20 @@ Follow this with quoted text to add a message to the chat log<br>
View the chat log. Pass an integer for the number of recent posts you would like to view (defaults to 5)<br>
`gab -l 20`
-b, --block, block<br>
Block a user (you will not see their messages) by passing the user's name<br>
`gab -b username`
-u, --unblock, unblock<br>
Unblock a previously blocked user by passing the user's name<br>
`gab -u username`
## Notes
In order to keep gab reasonably snappy and reduce unneccessary file bloat, individual user chatlogs are limited to ~12kb in size. This is generally enough to have a solid backlog of text while letting ancient conversation naturally get forgotten (at least as far as the computer is concerned).
You may think to yourself: "hey, can I just edit my chatlog directly?" The answer is: yes. But in most cases you shouldnt. The program knows that it should not display any lines that are not formatted the way it expects. It also knows that the future has not happened yet and so you could not have said anything in the future. However, you could in theory get a timestamp for a future time to essentially schedule a comment, sort of? Times that it could be appropriate to edit a chat log include: correcting spelling from a previous post, changing what you said to either provide more accuracy or annoy your friends and win an argument of some form, or to delete a message. I think the best part about gab is that it is decentralized: you own your log and it is independent of program execution. As such, you have the right to remove stuff from it. You can unsay things, sort of (not from people's ears/eyes, but from being seen in the log again). This ability to be forgotten or to decide you no longer want something representing you has largely been lost on the internet and I am happy to have created something with this ability. Just remember, with great ability comes great responsibility (dont be a jerk and try not to be weird about how you edit your log).
At present there is nothing to prevent a user from spamming. I plan to implement a block feature that would prevent users from seeing messages from users on their blocked list.
Blocking/unblocking has been added in version 2.1. The hope is that on larger systems or systems with varried users that do not all get along harmoniously a user can prevent spam or aggressive (or otherwise obnoxious) users from appearing in their chatlog. This blocking can be undone at any time by issuing the `unblock` command. When a user gets unblocked any messages that were missed while they were blocked (that have not been wiped out by the ~12k file limit) will be viewable.