Difference between revisions of "Talk:Main Page"

From Mumble Wiki
Jump to: navigation, search
(blablub: removal)
 
(48 intermediate revisions by 16 users not shown)
Line 1: Line 1:
== Bitrate ==
+
'''Note:''' Solved/Implemented suggestions will be removed. Add new headline for new topic. Indent replies through colons ':'.
  
How about give Mumble the option to set a max bitrate for audio stream ?
+
== Google captcha ==
  
if u got it right, the data volume can increase in some cases 5.8 Mbit/s and thats for only 10 users
+
Imo the google captcha is annoying, wouldn't it be enough to show it just once in the beginning?
i dont know anyone, who got a 23 Mbit/s connection for a private internet access, to hear a 40 ppl server case.
+
Or at least just sometimes?
  
It's O.K. on LAN, but i don't see it in an Internet-Based voice chat.
+
== Timeline for change being applied to Upstream public wiki is too long  ==
  
== Re: Bitrate ==
+
I noticed that changes to the public wiki are applied very slowly.
 +
Can't that be a little faster?
 +
At least changes made by Members of the team or even "trustful" users could be applied faster imo.
  
First of all, this is not a comment about the wiki, it's a question, and as such belongs on the SF forums :) (Click SourceForge to the left).
+
== Add link to audio page ==
  
Second, this has been included in murmur for over a year now ;)
+
You might consider linking to the [[audio]] page in the section for the client.
 
+
For clarity it should be named '''Audio Options'''.
== Please add some important links on the main page like "Building from Source", "Server HOWTO" ==
 
 
 
I have searched for an installation guide (building from svn source), but I could not find anything on the official mumble webpages. I think a [[Building from Source]] guide would be a good idea, because the last binary release is a little bit old and there are already many external HOWTOs which try to describe this procedure but they are not up-to-date. A [[Server HOWTO]] would also be nice. Oh, I see there are already articles like [[Configuring Murmur]] and [[Running Murmur]], but no page links to them.
 
Maybe you can design the main page more clearly like [http://www.mediawiki.org/wiki/MediaWiki] or [http://wiki.cookie-craft.de/en/index.php/Main_Page]. -- [[User:Xylo|Xylo]] 09:09, 20 June 2007 (PDT)
 
 
 
== Re:  Please add some important links on the main page... ==
 
 
 
I couldn't agree more. And of course the should be displayed in a somewhat organized way.
 
 
 
No clue for the layout but here are some examples:
 
 
 
Installing
 
===
 
Building from Source: http://mumble.sourceforge.net/Building_from_Source
 
Dev Tools: http://mumble.sourceforge.net/Development_Tools
 
 
 
Server Setup
 
===
 
Server Coniguration: http://mumble.sourceforge.net/Configuring_Murmur
 
Running the Server: http://mumble.sourceforge.net/Running_Murmur
 
Init Skript: http://mumble.sourceforge.net/Murmur_Init_Script
 
ACL & Groups: ACL and Groups
 
 
 
Client Setup
 
===
 
Advanced Client Configuration: http://mumble.sourceforge.net/Main:Advanced_client_configuration
 
Supported Games: http://mumble.sourceforge.net/Games
 
 
 
Misc
 
===
 
Commercial_Hosting: http://mumble.sourceforge.net/Commercial_Hosting
 
Errors: http://mumble.sourceforge.net/Connection_Failed
 

Latest revision as of 10:46, 16 April 2022

Note: Solved/Implemented suggestions will be removed. Add new headline for new topic. Indent replies through colons ':'.

Google captcha

Imo the google captcha is annoying, wouldn't it be enough to show it just once in the beginning? Or at least just sometimes?

Timeline for change being applied to Upstream public wiki is too long

I noticed that changes to the public wiki are applied very slowly. Can't that be a little faster? At least changes made by Members of the team or even "trustful" users could be applied faster imo.

Add link to audio page

You might consider linking to the audio page in the section for the client. For clarity it should be named Audio Options.