- Install Jira CLI, generate the API token and follow the initiation process. Make sure you can see a list of issues by using
jira issue list
. - Install fzf and setup some default configs if you like.
- Put this code below into your
.zshrc
(I'm not sure about.bashrc
, did not test it.
set noshowmode | |
set noruler | |
autocmd ColorScheme * highlight link ModeNFGC StatuslineNC | |
autocmd ColorScheme * highlight link ModeNFGCS LineNr | |
autocmd ColorScheme * highlight link ModeIFGC DiffAdd | |
autocmd ColorScheme * highlight link ModeIFGCS DiffAdded | |
autocmd ColorScheme * highlight link ModeRFGC Search | |
autocmd ColorScheme * highlight link ModeRFGCS Repeat | |
autocmd ColorScheme * highlight link ModeVFGC CursorIM |
I've commented a few times about some issues I see with the scalability of ActivityPub - the protocol behind the Fediverse and its best-known implementation Mastodon. A couple of folks have asked for more elaboration, so ... here it is.
First, let me add some disclaimers and warnings. I haven't devoted a lot of time to looking at ActivityPub, so there might be some things I've misunderstood about it. On the other hand, I've brought bigger systems - similar node counts and orders of magnitude more activity per node - from broken to working well based on less study of the protocols involved. So if you want to correct particular misconceptions, that's great. Thank you in advance. If you want to turn this into an appeal to authority and say that I'm wrong only because I haven't developed a full ActivityPub implementation or worked on it for X years ... GTFO.
What is ActivityPub? It's an HTTP- and JSON-based protocol for exchanging information about "activities". An activity could be many things.
- Official docs from Redis https://redis.io/commands
- Nodejs Redis client https://github.com/redis/ioredis
If Redis is running on the same machine, it will connect to the default Redis server localhost
on port 6379
.