Is this project still active? Yes it is

Is there any update or at least some estimation on when to expect the release?

(I’m looking forward using pijul for my pet-project, but would like to start with version 1.0)

1 Like

Pijul itself is ready-ish, I have been working for the last 2-3 days on deploying the new version of the Nest. This was complicated by a number of technical details, but I hope to be done today.


That’s really great news, thank you!

1 Like

Signed up to Discourse just to set like to this message.

That’s some great news! I’ve been following Pijul for a long time, and I’m very excited for the release.

Do you have any plans on how to maximize adoption? The release will give Pijul some exposure. Are you going to write blog post(s) synchronized with the release, etc.? Or are you going to release somewhat silently at first?

There’s a frightening amount of stuff to write, and it will take me a while to explain everything.
My current plan is, I’m actually releasing it as I’m writing this answer. There is almost no documentation, but I’ll write it one page at a time in the next few days. I’ll also write a blog post tomorrow to explain what I’ve been doing.

Oh, and after talking to Florent, we have finally decided to change the name. More on that in my blog post tomorrow.


DONE! Thanks for your patience.

See https://anu.dev and https://nest.anu.dev


If I already have an account on the Pijul Nest, can I use the same username and password for the Anu Nest? Or do I need to make a new account?

At minimum @pmeunier needs to fiddle some oauth settings for the new domain, e.g. for me Github login redirects to nest.pijul.com, and Google errors with

The redirect URI in the request, https://nest.anu.dev/oauth/google, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs, visit: https://console.developers.google.com/apis/credentials/oauthclient/{your_client_id}?project={your_project_number}

1 Like

The obvious https://nest.anu.dev/anu/anu is missing revision history but otherwise looks good, and I do like the shorter name.

Great work!

Getting an error when trying to install:

error: failed to run custom build command for `thrussh-libsodium v0.2.0`

I guess it’s probably obvious but…
Any ideas?

I had pijul compiling, but for anu, I get

 error: linking with `cc` failed: exit code: 1
[snip huge cc command]
 = note: /usr/bin/ld: cannot find -lzstd
         /usr/bin/ld: cannot find -lxxhash
         collect2: error: ld returned 1 exit status

@orestis @joyously
Try to get all the libraries mentioned in the Getting Started page first.

Thanks for the suggestion. Although I had them all installed looks like I obviously did something wrong the first time… After purging and reinstalling libsodium it now works. Thanks! Excited to see how it goes!

I’m so excited about this! Also excited to see the libanu module in there… I could see this being useful for building decentralized applications.

I have noticed that the pijul’s nest is done, while anu’s nest seems online, but never returns result. Is this related to the possibility to rollback the decision to rename pijul?

I’m indeed rolling this decision back, and redeploying everything. Now, the Nest has changed significantly in the last few weeks, and stability is not its best feature at the moment.
Sorry about all this, hopefully I manage to publish the (long) blog post I’ve prepared to explain all this.

1 Like

The old Nest is available as https://old-nest.pijul.com, but the HTTPS certificates are broken (I will try to fix that as soon as I can).

Looking forward to trying this out soon! But right now, anu.dev and nest.anu.dev are inaccessible. HTTP Strict Transport Security is active and the certificate seems to be invalid?

1 Like

@pmeunier can I suggest switching xxhash to pure rust implementation? This additional C dependency is probably unnecessary.

1 Like