Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation is too good, not appropriate for common scenarios #72

Open
GoogleCodeExporter opened this issue Nov 10, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. download and install dircproxy
2. then set it up...

What is the expected output? What do you see instead?
I would like to see an absolute zero knowledge howto for configuring and 
connecting dircproxy 
and configuring irssi to use it. Preferably a video, the current documentation 
is misleading and 
verbose for most common scenarios. A video dump on youtube for something like 
dircproxy 
would make sense; don't make it too good; just tell the basics. Current 
documentation is 
probably too good. A target would be that a novice could set it up in just 10 
minutes, without 
having to know the gritty details or read/understand the whole application 
inside out.

An example of a misleading setup is the password in the connection classes and 
the location of a 
password in the irssi config core. Connection to a proxy and connecting to a 
network has a 
different password? I don't know. 

Another example are the connection classes. Do i need to specify what channels 
i want to join on 
my server? I also read that i can join them automatically from the client. I 
guess its pretty smart, 
but i'm totally lost here. Where do i find a list for all options in a 
connection class, and do i even 
want to set them on a server?

What version of the product are you using? On what operating system?
macirssi (irssi with an appealing shell) and latest version of dircproxy

Please provide any additional information below.
thanks for considering this request :)

Original issue reported on code.google.com by elger.jo...@gmail.com on 14 May 2010 at 11:51

@GoogleCodeExporter
Copy link
Author

This is not a defect, i forgot to set that field correctly. Its priority is 
correct. Cannot change this information, so 
enjoy this incorrect categorization :)

Original comment by elger.jo...@gmail.com on 14 May 2010 at 11:55

@GoogleCodeExporter
Copy link
Author

Hey, that sound like something good for you to do!

This is an open source project, you know ;-)

Original comment by noel.w8tvi on 14 May 2010 at 1:36

  • Added labels: Type-Other
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

I was daunted by the config. At first. But then I thought of other configs I've 
read, hundreds of pages long... Quickly skimming through the example config and 
some trial and error is not bad at all. Took me half an hour to set it up.

Original comment by link68...@gmail.com on 17 Jun 2012 at 5:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant