Set up IRC logging
- Dominant language
- JavaScript
- Stars
- 6.8k
- Forks
- 573
- PR merge metrics
- No merged PRs in 30d
Description
```
bret: ya so its hyperirc -> hypercored websockets -> hyperirc-web =)
09:28 Bret Comnes sweeeet
09:29 → hyperirc-712a528 joined (~nodebot@83.167.197.104.bc.googleusercontent.com)
09:29 bret: oh wasn't tailing before but just added o/
09:29 712a528f5202bd670b75a26a3e06e8a0c76773cd815a719076d39ac3d7b39824
09:29 Bret Comnes yay!
09:29 → chjh_ joined (~chjh@104.254.92.61)
New messages
09:29 now you can read via `hyperpipe ./db 712a528f5202bd670b75a26a3e06e8a0c76773cd815a719076d39ac3d7b39824
```
```
hmm seems like live hyperpipe may be broken
09:32 or not? anyways, bret thats how we run chat.datproject.org. Let me know if there are more questions. Want to make that UI more generic/easier to add other channels just haven't had time
```
Contributor guide
Research direction
The issue only contains an IRC chat transcript mentioning hyperirc, hypercored websockets, hyperirc-web, and hyperpipe ./db; no repository file, entry point, or test is named. First clarify the desired logging behavior and locate the relevant setup before defining what completion looks like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100