Difference between revisions of "Talk:Old Home Page"

From Audacity Wiki
Jump to: navigation, search
(point Baywolf to Proposed Front Page, summarise old spam filter issue)
(Move Talk:Old Home Page to Talk:Audacity Wiki Home Page so that users can give feedback on the current home page)
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{| style="background:#EEEEFF" width=90% align="center"
+
{{Intro|Please leave any comments about the design of the [[Audacity Wiki Home Page|Wiki Home Page]] (or anything else about the Wiki's content or functionality) on [[Talk:Audacity Wiki Home Page]].|}}
|This page is for discussion of matters relating to the '''content, functioning and features of the Audacity Wiki'''.
 
 
 
Please do not make technical support requests here, or general comments about the Audacity program. If you require technical support with Audacity, or wish to give us your views about it, please visit the {{external|[http://audacity.sourceforge.net/contact/ Contact Us]}} page on our main website.
 
|}
 
 
 
 
 
== 07 April 2008 Spam filter page saving problem ==
 
 
 
We had a problem when saving a page that contains new or pre-existing legitimate web addresses, the save was being blocked by the spam filter. We advised users to make a copy of the source then either save the page later, or save it with web addresses removed then resave it later from the copied source. Gale doesn't know exactly what the problem was and as at December 2009, using only our own spam blacklist, there doesn't seem to be a problem.   
 
 
 
 
== Green Earth ==
 
 
 
[[User:James|James]] Why is the sea green in the Earth-icon for 'multilingual'?  Is it a result of global warming :-) ?<br>
 
[[User:Galeandrews|Gale]] Probably more to do with "best image I could find at the time", also a "proper" colour sea would blend too much with the background. I'll see what can be done. I do think it's worth having, personally. 
 
:[[User:James|James]] Thanks Gale.  I'm fine with an icon for this too, it was just that the old sea-colour was distinctly odd.
 
 
 
 
 
== Home Page Feedback ==
 
 
 
JC: Oh yuck!  Too many colours.  It looks like a patchwork quilt.
 
 
 
GA: As stated it is an experiment (and many web designers would think the whole thing far too staid even now....). As it was, it looks to me if it's trying to be flashy but does not quite have the courage of its own convictions.... Colours are often used in web design to direct the eye.
 
 
 
We had quite a number of different text colours before for different sections didn't we (when we had white background),  but I don't think it worked too well as most of the text is links anyway. I would like to emphasize "Using Audacity" as it is the most important section  (I think). I was wondering also about highlighting other sub-sections like MP3 and devices (i.e. get back to the idea of emphasizing problem areas without having a huge "Problems" section). That may well not work.  For "Using Audacity" we could use the khaki colour for background that we use in three panels already, but that makes no sense to me from a logical point of view.  Unfortunately with a blue/grey background, it's quite hard to find a different colour that shows the links but is sufficiently different.     
 
 
 
Another approach might be to alternate two similar backgrounds between each panel, like the multilingual section at the bottom. I don't especially like that, but it looked the best solution to me for that case - with small text size there was far too much light colour. 
 
 
 
The colour used for the link to foreign tutorials is of course the one we already use for multinational content.
 
 
 
Any comments about the section structure? I don't really care for "Audacity in the wider world" any more than "Beyond Audacity" but I haven't been able to come up with anything better yet.
 
 
 
JC: Gale, it's not possible to have everything highlighted! 
 
 
 
<font color="blue"> James: Perfectly possible to have key things highlighted, you say you don't like it though and it's a respectable opinion. My preference would have been not to colour in khaki the sections where we now do so, but just to span highlight the relevant text, but you did not like that. I'm fine with that but it increases the patchwork effect you complain of. </font>
 
 
JC:  You're currently wanting to highlight specific pieces in some sections, and one whole section.  To make the using-audacity stand out more it could be taken out of the two column layout and put above it, as a single column, centred, same width as now, i.e. with 'white space' left and right of it.
 
 
 
<font color="blue"> I think having "Using Audacity" same width as now with 1/4 (presumably light blue) space either side would look would far odder than what we have now.  Spreading it across the whole width, (tutorials one side, tips the other) is a possibility. Either disturbs what I was trying to do which was to get the more user-centric issues on the right and more "esoteric" on the left.  I don't want to get more hung up about colours than on the structure.  </font>
 
 
 
JC: However, look at the page stats.  They give the best guide of what people are most interested in. 
 
 
 
<font color="blue"> The stats have two aspects, what are viewed (exist) and what are searched for (may not exist, which suggests "music" is not prominent enough though that word does now appear on the Home Page). Current page views will probably under-emphasise tip-related articles as Tips is now a category linked to on the Home Page and should generate more hits for Tips pages. The stats would suggest to me that MP3/LAME might not be prominent enough on the Home Page, but that was always going to be the price of getting rid of "Problems", and what I was trying to counteract in some way. </font>
 
 
 
JC: I don't think moving the using-audacity section will be that much help to people finding what they want to find quickly.
 
 
 
<font color="blue"> I tend to agree, mainly as it would disturb the structure too much, but honestly think (e.g. for new users who aren't searching for anything in particular) that the main contents part of this page needs more visual "pointers". You can read the lists of links but there is little "feel" about what belongs where, how sections are differentiated from each other, and where you should look first. I'm not alone, as I know a few professional web designers and they make the same complaint (apart from it being "boring"/"no images" etc.)
 
 
 
Gale </font>
 
 
 
---
 
 
 
Ok, I'm the new guy (here), but I've been a Wikipedian for about 5 years, and was responsible for the MythTV wiki transition to Mediawiki and much of the design there, so hopefully what I have to say here will be useful...
 
 
 
and I don't think the front page is bad at all.  :-)
 
 
 
I run my text up quite a piece, size-wise, and "Using Audacity" is above the fold, even for me.  So that's good.  I would swap it to the left column, though, I think.  My personal priority layout would be:
 
 
 
Whole column:
 
Community
 
 
 
Left column:
 
Using
 
Formats
 
Tech
 
Wider World
 
 
 
Right column:
 
About
 
Wiki
 
Developing
 
 
 
Whole column:
 
Multilingal
 
 
 
Otherwise, you're trying to do roughly what the ThinkWiki home page does, by boxing off different categories of items, and it's pretty decent.  I think I might try to use *slightly* fewer levels of nested boxes, or alternatively put a break line in above each box's attached label.  And I actually *like* the color coded background idea: one color for user items, one for developer/project items, one for wiki-specific items, and a separate one for "Community", which is sort of broken up into those three categories itself.
 
 
 
Oh, and I'd run the lede over white, not a color.
 
 
 
Take it for what it's worth.  Merry Christmas.  :-)<br>--[[User:Baylink|Baylink]] 09:25, 25 December 2009 (CST)
 
 
 
'''[[User:Galeandrews|Gale]]: 26Dec09''' Thanks for joining. Yes I think Wiki "traditionalists" may still quite like the current front page. However, James is the guy who's been working on a [[Proposed Front Page|new, much leaner front page]] which we plan to launch in February 2010. As you can see from the [[Talk:Proposed Front Page|discussion]], I've had some reservations but think it's "probably" better for new users to find things than the current list. Your ideas would be welcome. 
 
 
 
 
 
== Requests for edits to Home Page ==
 
 
 
'''Due to a recent very ugly hack attack on the Home Page, we're locking the Home Page so that only those with Sysop privileges can edit it.'''
 
 
 
Please use this section to request any edits you want to make to the Home Page, for example to add a link to a new page you created onto the Home Page, or to correct a typo you spotted. If you make regular and significant contributions to the Wiki and need to edit the Home Page, we'll consider granting you Sysop status, which you can request [[User talk:Galeandrews|here]].
 
   
 
 
 
----
 
 
 
 
 
== Restoring pages after spam ==
 
 
 
This wiki has suffered spam attacks now and then. If it happens again, you may aid restoring it by following the instructions at the [[Removing Spam]] page.
 
 
 
[[User:Suf|Suf]] 12:55, 23 June 2007 (PDT) (modified)
 
 
 
== PlugIn / plug-in ==
 
 
 
The front page has instances of both.  I don't really care which is deemed canonical, but I was trying to search the page for instances of plugin/plug-in so consistency would be a good thing.  Perhaps PlugIn was written in camel case out of habit from other wiki systems, which treat those as WikiWords?  But MediaWiki doesn't care, so just pick one and standardize it.
 
Thanks, [[User:Philip|Philip]] 09:43, 13 March 2006 (PST)<BR>
 
<span style="color:green;font-style:italic">Unfortunately as we allow users to freely edit, we'll never get consistency (I'd  personally prefer all pages to have spaces between words for the reasons you state). But if any one wants to write a page with suggested standard words and phrases when writing here, go ahead. In the case of plugins, Audacity calls its folder "Plug-ins" (hyphenated) and I suspect that usage is the more correct. - Gale
 
</span>         
 
 
 
== vandalism and links without spaces ==
 
 
 
Is it possible to block regular vandals? It's not good to go two days with porn-spam on the front page. Also, some of the links on the main page don't contain fingerspaces. Should they be added? [[User:Tommylommykins|Tommylommykins]] 10:11, 9 November 2006 (PST)
 
<span style="color:green;font-style:italic"><BR>Yes sysops can block vandals indefinitely, prevent them creating accounts and automatically block the last IP address used by the vandal, and any subsequent IPs they try to edit from. Actually we're gradually getting rid of the pointed finger external links as many do not like them and instead encourage users to use [[Template:External]] for external links which makes links italicised with no pointing finger.  </span>
 
 
 
 
 
== Orphaned pages ==
 
 
 
There are really a lot of orphaned pages.  The only ways to get to these pages is by hitting the "Random page" link in the navigation bar, by hitting "Special pages" then "Orphaned pages" or by seeing them in the "Recent changes" list soon after they've been made.  Someone in charge of the wiki might want to check these pages and either delete them or create links where they would be appropriate.
 
 
 
(That really was the long way of saying that people really aren't going to see those pages)
 
 
 
[[Special:Lonelypages]]
 
 
 
You will also find that users have created pages for themselves which is redundant.  We have user pages that are linked when using our signature with 3 or 4 tilde like this <nowiki>~~~~</nowiki> <br>[[User:A Witt|A Witt]]
 
<br>[[User:A Witt|A Witt]] 16:05, 20 January 2007 (PST)
 
 
 
<span style="color:green;font-style:italic">Most of the orphaned pages have now been removed. The few remaining pages are still considered for actions. There is also a new page ([[Pages suggested for deletion]]) where anyone can suggest pages to be removed. (23:05, 9 July 2007 (PDT))
 
</span>
 
 
 
== Need for a style guide? ==
 
 
 
Is there a need for a "style guide" for this Wiki? Recently the pages seem to become more and more colorful, and different editors use color slightly differently. Personally I think it would be a benefit to our readers if we kept to "general Wiki style", with only a few specific "Audacity Wiki styles". It would also benefit the editors, as it would limit the amount of html tags to be used.
 
 
 
Things that there could be a guide for are:
 
* Plainlinks or not for external links. ''(I prefer classic style, i.e. with the trailing little arrow icon.)''
 
* Use of '''''if you want to ... click [[here]]''''' or not. ''(I prefer writing out a [[descriptive link name]], not just '''here'''.)''
 
* Use of colors.
 
* How to format a page intro, before the first heading.
 
 
 
''([[User:Suf|Suf]] 23:30, 9 July 2007 (PDT))''
 
<span style="color:green;font-style:italic"><BR> Some colouring is I think useful to the users and lack of colour in my opinion is a serious drawback on technical Wiki pages. I think you agree with <span style="background-color:#CCFFCC; color:#a0522d">  this</span> for application menu paths (the principle if not the colours). I have been using green for something that is a HINT or an advisory and #BA55D3 for an imperative type of declaration.<BR><BR>
 
It is not easy to draw rules about "here" or "descriptive names". Sometime the flow of the text makes it easier to say "you can download the XYZ software [here]." Also can you add a mouseover to links giving a description? Some say you should put a plain text link so you can copy and paste it easier for future use, but that seems to be discouraged on Wikis and should only be done in exceptional cases because of the length of many URLs. <BR><BR>
 
How to format a page intro. might be good. E.g. "_TOC__"  to force a table of contents when there are less than four categories is little known.<BR><BR>
 
Plainlinks or not are controversial. I hate the classic trailing arrow myself and Wiki and non-Wiki links should display in slightly different colours. Against this Internet Explorer seems to add the space where the trailing arrow would otherwise be anyway, and I have not yet figured a way that makes plainlinks persist across paragraphs in a Wiki so quite a few extra tags are sometimes needed to use them. You can use double breaks within a span as I did here.<BR><BR> 
 
I think you can go too far regimenting style on a Wiki. It is a place for creation and within reason there ought to be some latitude if what is being done "differently" is an aid to intelligibility. For example someone might come up with something that looked so good that we might want to use it regularly in our own contributions. - Gale </span>
 
 
 
 
 
==Sound Tracks from within Wikimedia==
 
 
 
Are there plans for a demo section of Audacity created sound files here?  We would like to be able to reliably create sound tracks and activate them from within wikimedia software at en.wikiversity.org so if a demon section is planned it would be helpful to us if good notes could be taken.  If such were emailed to me I could relay them to our developers and users or the notes could be posted here or at en.wikiversity.org as part of some tutorials in building web presence for user products.  Thanks for reading!  [[User:Mirwin|Mirwin]] 16:00, 3 November 2006 (PST)
 
 
 
 
 
==Spam Measures==
 
From [[User:NT|NT]] 22:27, 9 October 2007 (PDT)
 
 
 
;Q<nowiki>:</nowiki><i>Can I ask what anti-spam methods have and have not worked well for you here?</i>
 
 
 
A:We have an Audacity spam blacklist (blocks spam URLs) which sysops can add to, as well as the Wikimedia blacklist.   
 
 
 
 
 
;<i>FWIW I'm involved in another wiki, and we've found that protecting the odd page or 2 has made matters worse, as the spammers then target assorted other pages, which just makes for more revert work.</i>
 
 
 
Protecting the home page is merely to keep it visible and prevent the hacker posting his tag there (as opposed to link spammers who will almost always target pages well inside the structure anyway).
 
 
 
 
 
;<i> We're planning to get captcha up and running to cut back the present spam.</i>
 
 
 
It generally only prevents automated spam, though.
 
 
 
: yes, that seems to be our main problem there.
 
 
 
 
 
;<i> Meanwhile we arrange the most targeted page so that added spam doesnt display.</i>
 
 
 
Do you mean by using a filter?
 
 
 
Gale
 
 
 
: I didnt set that one up and dont know the details, but i can give you the page addy if you'd like to check it out. It saves us a lot of work. Spammers think they've posted, but it doesnt show to readers.
 
[[User:NT|NT]] 19:39, 17 October 2007 (PDT)
 
 
 
<font color="green">
 
Hi - by all means post the web address here but at the moment it sounds as if some sort of keyword filtering is used. Does the spam poster see it  and no-one else? Does that make him stop if he thinks the page will remain, or does he rejoice at his success and spam a lot more (and maybe some it gets past the protection)? </font>
 
 
 
Gale
 
 
 
 
 
== Downloads Page ==
 
 
 
* I made a new downloads page [[Downloads]] [[User:Arlen|Arlen]] 20:45, 3 July 2009 (PDT)
 
* '''[[User:Galeandrews|Gale]] 05 July 09:''' Thanks for the idea (and for your contributions to [[Feature Requests]]). However one of the links you made on the download page was broken, and apart from that, I don't think the page served any purpose given the downloads page on our main site. Also the logo top left of every Wiki page links to our home page and its hover text mentions downloads. If your page had some special content such as tips for downloading, recommended download managers that can cope with redirected links or something like that, well, maybe we can think again. Thanks, anyway.
 
 
 
 
 
== Logo ==
 
 
 
Hi, you could reduce your bandwidth and download time (more than 10 secs for dialup-users) if you optimized the Audacity logo on this page.
 
 
 
Using optipng it came down from 82KB to 16KB!:
 
 
 
$ optipng /Users/Shared/NEW_AudacityTransMediaWiki.png
 
OptiPNG 0.4.8: Advanced PNG optimizer.
 
Copyright (C) 2001-2005 Cosmin Truta.
 
 
 
** Processing /Users/Shared/NEW_AudacityTransMediaWiki.png
 
155x135 8-bit RGB-alpha non-interlaced
 
Input file size = 84104 bytes
 
Input IDAT size = 83856 bytes
 
Trying...
 
  zc = 9  zm = 8  zs = 0  f = 0        IDAT size = 17869
 
  zc = 9  zm = 8  zs = 1  f = 0        IDAT size = 17198
 
  zc = 1  zm = 8  zs = 2  f = 0        IDAT size = 25517
 
  zc = 9  zm = 8  zs = 3  f = 0        IDAT size = 19472
 
  zc = 9  zm = 8  zs = 0  f = 5        IDAT size = 15565
 
  zc = 9  zm = 8  zs = 1  f = 5        IDAT size = 14284
 
  zc = 1  zm = 8  zs = 2  f = 5        IDAT too big ... abandoned at 97.77%
 
  zc = 9  zm = 8  zs = 3  f = 5        IDAT size = 13714
 
 
 
The best parameters are:
 
  zc = 9  zm = 8  zs = 3  f = 5        IDAT size = 13714
 
 
 
New file size = 13842 bytes (70262 bytes decrease)
 
New IDAT size = 13714 bytes (70142 bytes = 83.65% decrease)
 
 
 
I uploaded the optimized image: http://wiki.audacityteam.org/images/a/a7/NEW_AudacityTransMediaWiki.png
 
  
 
[[Category:Participation]]
 
[[Category:Participation]]

Latest revision as of 04:27, 4 February 2010

Please leave any comments about the design of the Wiki Home Page (or anything else about the Wiki's content or functionality) on Talk:Audacity Wiki Home Page.