update first jocalsend post with link to second
This commit is contained in:
parent
8a03ea1798
commit
97503635a9
1 changed files with 2 additions and 3 deletions
|
@ -2,7 +2,7 @@
|
||||||
title = "Jocalsend: actually useful software if you're a weirdo like me"
|
title = "Jocalsend: actually useful software if you're a weirdo like me"
|
||||||
slug = "jocalsend"
|
slug = "jocalsend"
|
||||||
date = "2025-08-22"
|
date = "2025-08-22"
|
||||||
updated = "2025-09-02"
|
updated = "2025-09-03"
|
||||||
[taxonomies]
|
[taxonomies]
|
||||||
tags = ["software", "sundry", "proclamation", "localfirst", "useful", "p2p"]
|
tags = ["software", "sundry", "proclamation", "localfirst", "useful", "p2p"]
|
||||||
+++
|
+++
|
||||||
|
@ -49,8 +49,7 @@ spec](https://github.com/localsend/protocol), which means that anyone can make t
|
||||||
implementation, which is where jocalsend comes in. I plan on writing a follow-up[^follow-up]
|
implementation, which is where jocalsend comes in. I plan on writing a follow-up[^follow-up]
|
||||||
about the design and implementation of jocalsend, but that's going to be a much longer and
|
about the design and implementation of jocalsend, but that's going to be a much longer and
|
||||||
even-more-niche-interest post, so I'll just skip that for now. Stay tuned, though, if that's a
|
even-more-niche-interest post, so I'll just skip that for now. Stay tuned, though, if that's a
|
||||||
boat-floater for ya!
|
boat-floater for ya! UPDATE! That post [is now live](/rnd/jocalsend-development)!
|
||||||
|
|
||||||
## How do I install it?
|
## How do I install it?
|
||||||
|
|
||||||
### Via cargo
|
### Via cargo
|
||||||
|
|
Loading…
Reference in a new issue