What is the relation to https://pigeons.computer/ ?

Open
#20 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github, shell
Domain
documentation

Research direction

Inspect README.md, the GitHub About section, and the pigeons.computer Open source and installation sections. Align the project links and installation URLs across GitHub and the landing page; it is done when both sites link to each other and present the same installation link.

Written by the indexing model from the issue text.

Description

https://pigeons.computer/ seems to be the landing page of this project, but right now neither the landing page links the GitHub page, nor the GitHub page links the landing page, which puts me off as a new user.

What I expect:

  • The About section of GitHub to link to https://pigeons.computer/ (or in README.md, or in both)
  • https://pigeons.computer/ links to GitHub page (pigeons.computer already has the appropriate "Open source" section)
  • Right now, installation instructions use different domains (curl -fSsL https://vorc.s3.us-east-2.amazonaws.com/pigeons-install.sh | bash for GitHub, and curl -fSsL https://pigeons.computer/install.sh | bash for pigeons.computer). I expect them to use the same link.

pigeons.computer is a great way to access your ssh machines behind firewalls, I am excited for the work you do at iroh. But in it's current state, pigeons makes bad first impression and just looks shady because of the mentioned reasons.

Sidenotes

Your other site https://www.iroh.computer/sendme has the same problem, and it even has already an issue raised: https://github.com/n0-computer/sendme/issues/77

https://www.dumbpipe.dev/ gets it right though (except for the installation methods which are different between the site and the GitHub page)

Dominant language
Rust
Stars
207
Forks
9
Avg merge
12h 25m
Merged PRs (30d)
2

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from n0-computer/pigeons

All issues in n0-computer/pigeons

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.