dickmao
/
nndiscourse
Protected
1
1
0
Fork 1
Code Issues 1 Pull Requests 1 Packages Projects Releases Wiki Activity

Does this work with https://discourse.doomemacs.org/ ? #10

New Issue
Closed
opened 2021-09-26 12:56:14 +00:00 by NightMachinery · 3 comments
NightMachinery commented 2021-09-26 12:56:14 +00:00 (Migrated from github.com) 
(require 'nndiscourse)
(progn
  (custom-set-variables '(gnus-select-method
                          '(nndiscourse "discourse.doomemacs.org" (nndiscourse-scheme "https")))))

I get

‘nndiscourse-register-process’: dead process discourse.doomemacs.org
goto-history-element: End of history; no default available
nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1
nndiscourse (discourse.doomemacs.org) open error: ‘’.  Continue? (y or n) y
Opening nndiscourse server on discourse.doomemacs.org...
Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying
Opening nndiscourse server on discourse.doomemacs.org...failed: 
Checking new news...
Reading active file from discourse.doomemacs.org via nndiscourse...
Opening nndiscourse server on discourse.doomemacs.org...
Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying
Opening nndiscourse server on discourse.doomemacs.org...failed: 
Checking new news...done
No news is good news
Warning: Opening nndiscourse server on discourse.doomemacs.org...failed: ; Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying; Opening nndiscourse server on discourse.doomemacs.org...failed: ; Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying; nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1; ‘nndiscourse-register-process’: dead process discourse.doomemacs.org
``` (require 'nndiscourse) (progn (custom-set-variables '(gnus-select-method '(nndiscourse "discourse.doomemacs.org" (nndiscourse-scheme "https"))))) ``` I get ``` ‘nndiscourse-register-process’: dead process discourse.doomemacs.org goto-history-element: End of history; no default available nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1 nndiscourse (discourse.doomemacs.org) open error: ‘’. Continue? (y or n) y Opening nndiscourse server on discourse.doomemacs.org... Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying Opening nndiscourse server on discourse.doomemacs.org...failed: Checking new news... Reading active file from discourse.doomemacs.org via nndiscourse... Opening nndiscourse server on discourse.doomemacs.org... Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying Opening nndiscourse server on discourse.doomemacs.org...failed: Checking new news...done No news is good news Warning: Opening nndiscourse server on discourse.doomemacs.org...failed: ; Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying; Opening nndiscourse server on discourse.doomemacs.org...failed: ; Server nndiscourse+discourse.doomemacs.org previously determined to be down; not retrying; nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1; ‘nndiscourse-register-process’: dead process discourse.doomemacs.org ```
dickmao commented 2021-09-26 13:37:40 +00:00 (Migrated from github.com)

Alas, no. A discourse that requires login is not read-only, and nndiscourse is only read-only.

Uninteresting backstory:
https://github.com/dickmao/nndiscourse/issues/8#issuecomment-728474409

As of the time I wrote nndiscourse, the CSRF of Discourse essentially required a full-fledged browser. My post https://meta.discourse.org/t/user-api-keys-specification/48536/33?u=dickmao

Edit: Hmmm... that link shows someone quite recently claiming to have gotten read-write to work. Not going to pursue it until I need more than one hand to count the number of nndiscourse users in the world.

Alas, no. A discourse that requires login is not read-only, and nndiscourse is only read-only. Uninteresting backstory: https://github.com/dickmao/nndiscourse/issues/8#issuecomment-728474409 > As of the time I wrote nndiscourse, the CSRF of Discourse essentially required a full-fledged browser. My post https://meta.discourse.org/t/user-api-keys-specification/48536/33?u=dickmao _Edit: Hmmm... that link shows someone quite recently claiming to have gotten read-write to work. Not going to pursue it until I need more than one hand to count the number of nndiscourse users in the world._
NightMachinery commented 2021-09-26 13:51:19 +00:00 (Migrated from github.com)

@dickmao I also get this error for Julia's Discourse though:

Checking new news...
Reading active file from discourse.julialang.org via nndiscourse...
Opening nndiscourse server on discourse.julialang.org...
nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1
‘nndiscourse-register-process’: dead process discourse.julialang.org
Opening nndiscourse server on discourse.julialang.org...failed: 
Reading active file via nndraft...done
Checking new news...done
No news is good news
Warning: Opening nndiscourse server on discourse.julialang.org...failed: ; ‘nndiscourse-register-process’: dead process discourse.julialang.org; nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1
Mark set
@dickmao I also get this error for [Julia's Discourse](https://discourse.julialang.org/) though: ``` Checking new news... Reading active file from discourse.julialang.org via nndiscourse... Opening nndiscourse server on discourse.julialang.org... nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1 ‘nndiscourse-register-process’: dead process discourse.julialang.org Opening nndiscourse server on discourse.julialang.org...failed: Reading active file via nndraft...done Checking new news...done No news is good news Warning: Opening nndiscourse server on discourse.julialang.org...failed: ; ‘nndiscourse-register-process’: dead process discourse.julialang.org; nndiscourse-sentinel: process /Users/evar/.rvm/rubies/ruby-3.0.0/bin/bundle exited abnormally with code 1 Mark set ```
dickmao commented 2021-09-26 14:16:16 +00:00 (Migrated from github.com)

I'm afraid the ruby process is failing. make test-run-interactive is one way of debugging it, but I suspect your patience has run out. Incidentally, this is how discourse.julialang.org looks on this side.

nightmachinary

I'm afraid the ruby process is failing. `make test-run-interactive` is one way of debugging it, but I suspect your patience has run out. Incidentally, this is how discourse.julialang.org looks on this side. ![nightmachinary](https://user-images.githubusercontent.com/7578770/134811580-d2f4f2fe-4eb0-4327-b86f-179447a0fa6a.png)
❤️ 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels   
bug

Something isn't working   
dependencies

Pull requests that update a dependency file   
documentation

Improvements or additions to documentation   
duplicate

This issue or pull request already exists   
enhancement

New feature or request   
good first issue

Good for newcomers   
help wanted

Extra attention is needed   
invalid

This doesn't seem right   
question

Further information is requested   
wontfix

This will not be worked on
No Label
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: dickmao/nndiscourse#10
There is no content yet.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?