TL;DR Site updates reflecting a backlog of policy changes and tidy ups.
I believe all these changes were discussed previously here - if not
please comment.
Hi All,
Both Hacker Public Radio and GNU World Order were on the "Top Stories"
of Hacker News over the weekend.
Addressing some of the points in the comments, the syndication.php page
was updated to remove the reference to mp3's been patent encumbered. The
sizes of the feeds have been increased, and additional playout sites
were listed.
These were also added to the footer:
Removed Google Play.
Change the Archive.org link to our project page.
Added links to iTunes, Google Podcasts, PlayerFM, Spotify, MixCloud.
(If there are more out there please send them on.)
In addition there have been some changes made to the "Contribute", and
"Stuff you need to know page" to clarify our policies that were
previously discussed here on Mailing list, and on the Community News shows.
Changed everywhere from "We are a Community podcast network" to "We are
a Community podcast" - note the outros still need to be updated.
Changed Contribute page:
From "Your show will not be moderated."
To "Your audio will not be moderated."
Changed the "Stuff you need to know page":
Reorganized the sections.
Changed the link to the unmaintained site "Hacker Media", to reference
"Free Culture Podcasts"
Changed links from http to https
Changed "Your show will not be moderated." to "The audio of your show
will not be moderated."
Changed "We do not vet, edit, moderate or in any way censor any of the
shows on the network" to "We do not vet, edit, moderate or in any way
censor any of the audio you submit"
Added:
"We <strong>do</strong> transcode the audio into different formats.
Please note that this only relates to the audio you upload.
The rest of the meta-data (branding/summaries/tags/show notes/etc.), are
managed by the HPR Community, and <strong>may</strong> be edited.
The show <a href="https://hackerpublicradio.org/eps.php?id=2210";>hpr2210
:: On Freedom of Speech and Censorship</a> describes the agreed approach
to this topic."
Added:
<h2 id="accessibility">Keep accessibility in mind.</h2>
<p>
When you includes output from the command line in the show notes,
posting screen-shots of console or terminal output makes it impossible
for screen readers to access the text.
Always try to include the raw output ( eg: embedded in <pre> tags)
<br />
Include descriptive language in any link texts.
<br />
Avoid structures like: <em>"For accessibility information click <a
href="#accessibility">here</a>"</em><br />
Rather use: <em>"For more information click our <a
href="#accessibility">accessibility page</a>"</em><br />
</p>
--
Regards,
Ken Fallon
http://kenfallon.com
http://hackerpublicradio.org/correspondents.php?hostid=30
_______________________________________________
Hpr mailing list
[email protected]
http://hackerpublicradio.org/mailman/listinfo/hpr_hackerpublicradio.org
