#7 Nest usability & contribution issues

Opened by turion on November 6, 2020
turion on November 6, 2020
  • Ctrl+Enter doesn’t create a new discussion
  • When editing a post in an anu nest discussion, I have to edit HTML instead of Markdown
  • The Code for nest.anu.dev seems not to be online, is that intentional?
Alphare on November 6, 2020

Piggy-backing off of this: I don’t get mail notifications (or notifications of any kind, really) if someone answers me.

hyperfekt on November 6, 2020

Keeping this going:

  • Entering invalid credentials on login does not display any kind of error.
  • The signup mail gets tossed into the spam folder at ProtonMail, even though DKIM and SPF seem to pass. I pulled it out, maybe that’s enough to teach ProtonMail.
hyperfekt on November 6, 2020
  • Attempting to upload a heavy profile picture leads to a connection reset.
pmeunier on November 9, 2020

The Code for nest.anu.dev seems not to be online, is that intentional?

This is intentional. I don’t have the resources to maintain too many open source projects.

notramo on November 11, 2020

Will it be closed source proprietary software always?

pmeunier on November 11, 2020

Will it be closed source proprietary software always?

Hopefully this will change when I have the resources (in terms of money, time and “psychological bandwidth”) to make it open source.

pmeunier on November 13, 2020

Ctrl+Enter doesn’t create a new discussion

Fixed

When editing a post in an anu nest discussion, I have to edit HTML instead of Markdown

Fixed

Piggy-backing off of this: I don’t get mail notifications (or notifications of any kind, really) if someone answers me.

I believe I’ve fixed that too. I’ve tried to go a little lighter on emails with this release, but that might have been a little too light. Email for discussions were opt-in, but they are opt out (you get registered automatically if you start a discussion or comment on one, and you can click on the “unsubscribe” link in the email to unsubscribe from the discussion).

Attempting to upload a heavy profile picture leads to a connection reset.

This now leads to a connection reset only if it is larger than 10Mb. Files larger than 1Mb will just yield an error.

krixano on November 13, 2020

I was wondering if there were plans to add the ability to make some things on a repo private… like making the whole repo private, or just making the change info (and downloading) private while the discussions remain public.

Also, I suggested this previously on the old nest, but I wanted to make sure it wasn’t forgotten - a feature to download a repo as a zip from the nest website.

arijid79 on November 16, 2020

If I click on the edit button and edit a discussion’s title and click the Ok button, nothing happens, no reloading, no page redirection

pmeunier on November 26, 2020

@krixano: there are plans in that direction. The permissions are implemented, but there’s no UI yet. This will probably come when Pijul is slightly more mature, with CI and things like that. Before that, the Nest should also become more social, get repository indexing and things like that.

voroskoi on November 29, 2020

Hi,

Today I have tired to push some changes to my repo, but I always hit this error message:

Key "y4MaK2QsPoesg3eLDSfv4NSKkYo8f4Nngxm2K3YbhWY" (with agent) rejected

Password authentication works. I have tried removing the pub key (which works file) and then re-adding it, which does not. My browser drops a Secure Connection Failed message when I push the add button.

ammkrn on November 29, 2020

Please consider changing the nest layout so that the most recent discussion items appear first. As an issue tracker I can understand the idea of having it sort of like a queue where ideally you would clear out the old stuff first, but ‘most recent -> least recent’ seems so overwhelmingly common that it’s worth going with the flow.

pmeunier on November 29, 2020

@voroskoi: This isn’t really an error message, and we should remove it. The connection may work, it just means it won’t use the key from your agent. The reasoning is that if you took the time to setup an agent, you probably want to know it’s not being used.

@ammkrn: Good idea.

voroskoi on November 29, 2020

@pmeunier: Actually I have only one key loaded in my ssh-agent and that is not the one in the error message. Also nest should ask for the key’s passphrase if it would accept the key, but I can login with my pw for the site. So that is a password login, not a ssh-key login. I have no idea where that key come from, I have thought it is something nest-related.

~ on  master [!] ❯ keychain --clear

 * keychain 2.8.5 ~ http://www.funtoo.org
 * Found existing ssh-agent: 1210
 * ssh-agent: All identities removed.

~ on  master [!] ❯ cd code/learn.go/
~/code/learn.go on  master [!] ❯ pijul push voroskoi@nest.pijul.com:learn-go
Password for voroskoi@nest.pijul.com: ⏎                                                                                                                                                        
~/code/learn.go on  master [!] ❯ keychain id_ed25519

 * keychain 2.8.5 ~ http://www.funtoo.org
 * Found existing ssh-agent: 1210
 * Adding 1 ssh key(s): /home/voroskoi/.ssh/id_ed25519
 * ssh-add: Identities added: /home/voroskoi/.ssh/id_ed25519

~/code/learn.go on  master [!] ❯ pijul push voroskoi@nest.pijul.com:learn-go
Key "y4MaK2QsPoesg3eLDSfv4NSKkYo8f4Nngxm2K3YbhWY" (with agent) rejected
Password for voroskoi@nest.pijul.com:
pmeunier on November 29, 2020

@voroskoi: it seems your key isn’t properly added on the Nest. I’m redeploying right now, it should be ok in a few minutes.