Petition to Warner Brothers
Include Proper Ravenclaw Crests on Merchandise!
Anyone that is a fan of both the Harry Potter books and movies clearly recognizes a discrepancy when it comes to Ravenclaw: For the movies, WB decided to change both the colors and the mascot of the House. To some this may seem a trivial thing, but for those of us that identified as Ravenclaws before the movies came out, it can be very disheartening and aggravating not to be able to purchase merchandise online and at WWOHP that feature the correct colors (blue&bronze) and correct mascot (the Eagle). As such, we have to rely on outside merchandisers providing us with items with the correct crest, therefore WB is losing out on money from Ravenclaw fans. This petition beseeches them to rectify this error and put out merchandise that has the crest as seen on Pottermore and other work approved by J.K. Rowling. This will make many HP fans happy and will increase revenue as more people will buy items once the error is corrected.
Petition to Music Streaming Services
Bring Peace to the Loudness War
Music streaming services need to properly manage audio loudness. We ask them to implement a loudness level in line with the Audio Engineering Society recommendations. No More Loudness JumpsMusic listeners’ number one complaint is when volume levels jump up and down. In contrast, loudness management can make for a far better listening experience: Quiet songs or albums are turned up and loud songs or albums are turned down. This is called “loudness normalization” — and the benefits are huge. When streaming services start using normalization, listeners will be happier and sound quality will improve across all services. Keep the Artists’ IntentStreaming services, please let artists choose how their music should sound! Some producers choose to master loud as part of their art. But other creators feel forced to master too loud (over-compress), compromising their vision because more dynamic music would sound lower than the “competition.” They mix and master to the level of the loudest streamer, adding unwanted distortion, pumping and clipping. This situation intensifies the Loudness War in music production and discourages creators from producing programs which are dynamic, open-sounding and impactful. Streaming services, please turn normalization on by default and choose the AES recommended loudness level (‘target’). This sensible target protects the sound quality of the original production and maintains loudness from track to track. When artists know and expect that loudness management will be used, they can finally follow their own vision without worrying about competing and we can enjoy the music exactly as they intended. Streamers: Let’s CollaborateWe know streaming services want to provide the best sound and service to their users. As music streaming hits the mainstream, now is the perfect opportunity to end the Loudness War by adopting universal loudness management. So please join the dialogue here at change.org. Let’s work together to make a better sounding audio world! Take Action!The Loudness War is over if you want it. Many people have been concerned for a long time about this issue… Sign this petition, asking streaming services to implement loudness normalization now, following the AES guidelines — and share it with your friends! References Wikipedia about the Loudness War. Loudness War links at MLA’s website MLA's white paper about Loudness Normalization for music Technical InformationThis petition focuses on music providers but all genres and services are affected by loudness issues, from podcasts to talk shows, music programs and videos. Tremendous progress in loudness measurement and management has already been made by groups like the EBU, the ITU and ATSC. The AES has produced this streaming recommendation: Recommendation for Loudness of Audio Streaming and Network File Playback: Audio Engineering Society Technical Document AES TD1004.1.15-10. Recommendation for loudness normalization by Music Streaming Services: Eelco Grimm, HKU University of the Arts Utrecht. Presented on May 22nd 2017 at AES 142nd convention in Berlin. Give Peace a Chance - Sign here now!
Petition to Archie Comics Publications
Reverse the Changes to the Sonic the Hedgehog Comic
There have been huge changes recently to Archie's Sonic the Hedgehog comic as well as its spin-offs, graphic novels and reprints. Many beloved characters that have existed for years have been erased in a reboot. The loss of these characters is having an extremely detrimental impact on the comic and we humbly ask for them to be reversed.
Petition to Satya Nadella (Microsoft.com), Microsoft
What Computer users want changed in Windows 10
To effectively implement and use Windows 10 in our homes and businesses, Microsoft must make changes to both the operating system and the policies the company put in place to support the new OS. Those changes fall into two categories: 1) Microsoft must give Windows 10 users more control over when updates are installed. We need the ability to delay or hide damaging updates that impact the computing experience, have undesirable side effects such as blue screens of death, or reduce the functionality to attached devices. Under the current system of mandated updates, we have been adversely impacted by forced driver and firmware updates plus other patches; we've wasted hours dealing with the unwanted side effects. As long-time Windows users, we understand the need to have quicker and more agile security updating. But this agility should not introduce additional risks to our systems. Windows 10 updates have already caused loss of system functionality, video and display issues, and other significant issues. [edit 11/5/2016: The 1607 release has added active hours, but the release is still mandating nearly weekly reboots which is unacceptable. We feel the updating process isn't getting better, but in fact worse. Users (and Journalists) complain that " ... get a new update to Anniversary Update and some things aren't working like they worked before. I wonder which of the updates I just got did something to it" and have a difficult time determining if a bug has been fixed in a particular release.] 2) Microsoft should provide detailed information on what's in each update -- along with what system changes we should see with each cumulative-update release. We applaud the cumulative-update model, but the lack of documentation doesn't let us to perform the due diligence required for safely deploying and maintaining Windows 10 systems in our organizations. [edit 11/5/2016 - Microsoft is now providing more detail here https://support.microsoft.com/en-us/help/12387/windows-10-update-history however the ability to track when a bug in a prior release has been fixed is still difficult to do. The Insider Feedback process doesn't provide an effective way to determine when reported bugs are resolved.] We have expressed our concerns on the Uservoice feedback platform here and here. We now use change.org's petition platform to express our concerns more broadly. We need control using our existing patching methodologies. We need communication. Sincerely, Your Windows customers
Petition to Federal Communications Commision (FCC)
Stop the FCC from Removing the Telecoil Compatibility Requirement from HAC Phones
The FCC has proposed new rules that would require Hearing Aid Compatibility (HAC) for all future consumer wireless devices, including next-generation technologies like Wi-Fi calling and Voice over LTE. The landmark consensus plan would, for the first time, establish a “path to ensure that all wireless handsets are accessible to and usable by people who use hearing aid devices and cochlear implants.” While a revision to HAC rules is welcomed, the FCC has also requested feedback about a controversial proposal from Apple, which would do away with the need for telecoil support in HAC mobile phones: From an FCC report dated November 20, 2015: ...Apple proposes that the Commission apply the ANSI standards as a “safe harbor” for hearing aid compatibility but to “reward innovators for finding other, better solutions that result in real accessibility even if they do not meet the ANSI standards.” Although Apple proposes this approach as an alternative method of meeting the existing benchmarks, we seek comment on whether to adopt it in conjunction with the Joint Consensus Proposal. We also seek comment on how to determine hearing aid compatibility outside of compliance with the applicable ANSI standard. We invite commenters to consider alternatives of this kind when evaluating the Joint Consensus Proposal. If Apple’s proposal is adopted, there are substantial risks to both consumers and hearing aid dispensing professionals. Consumers should not be limited to hearing aid models based on the type of phone that they own, and they should not have to buy new hearing aids should they decide to switch from an Apple phone to a Samsung phone. Likewise, audiologists and hearing instrument specialists should not have restrictions placed on which hearing aids they may recommend based on their patient’s mobile phone. Having a universal standard allows consumers to more freely choose a hearing aid device. Until a new digital wireless standard is universally adopted by all cell phone and hearing aid manufacturers, the FCC should continue to require support for the current universal technology - the telecoil - in HAC phones. Let the FCC know that you agree by signing this petition!