Talk:Old 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 page on our main website.
|Home Page Changes|
We're experimenting with the look and feel of the Home Page at the moment to try and get more interest in it, encourage more (non-spam) editing, and encourage more developers to join Audacity so as to push it forward faster. So there may be rapid changes to the Home Page or even reversions back to what appeared a few minutes ago! Please bear with us, but post any comments in "Home Page Feedback" below.
Home Page Feedback
JC: "Yellow on blue looked terrible - try emphasizing by grouping".
GA: It was a bit gauche maybe, but deliberate. We need to draw attention to this to get people more involved, coming back frequently to check. Also I suspect relatively few notice recent changes at the side and my watchlist at the top. Grouping with "finding pages" together takes an extra line, but probably it's useful anyway. But we should try and play with colours a bit I think, even within our standard panels. There is a lot on the front page and though it looks nice there is nothing yet to distinguish the sections visually. I think we should try a background for keeping up to date, for a while anyway. Want to suggest another colour?
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 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.
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, Philip 09:43, 13 March 2006 (PST)
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
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? Tommylommykins 10:11, 9 November 2006 (PST)
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.
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)
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 ~~~~
A Witt 16:05, 20 January 2007 (PST)
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))
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.
(Suf 23:30, 9 July 2007 (PDT))
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 this 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.
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.
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.
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.
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
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! Mirwin 16:00, 3 November 2006 (PST)
From NT 22:27, 9 October 2007 (PDT)
- Q:Can I ask what anti-spam methods have and have not worked well for you here?
A:We have an Audacity spam blacklist (blocks spam URLs) which sysops can add to, as well as the Wikimedia blacklist.
- 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.
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).
- We're planning to get captcha up and running to cut back the present spam.
It generally only prevents automated spam, though.
- yes, that seems to be our main problem there.
- Meanwhile we arrange the most targeted page so that added spam doesnt display.
Do you mean by using a filter?
- 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.
NT 19:39, 17 October 2007 (PDT)
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)?