Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

About 'Article 13 - Copyright Proposal'?

more options

While trying to use 'your method' of either contacting, or being contacted by, 'an MEP' about the issue, I was disconnected TWICE during that call to me. I was NOT at ANY point, connected to either the Female MEP (call 1), nor the Male MEP (call 4). My 2nd&3rd call tries were 'rejected' due to 'whoops' error! wtf???? Has ANYBODY had an input with ANY MEP using 'your method' of contact? It has failed FOUR TIMES for me. I am in the UK. I used a mobile phone number each time. IF the number called by 'your method' MUST be a 'geographial landline number', then you should say that on the 'call now' page! Last point is: Who pays for these calls? Being that I never got connected to a live person, not even once after four attempts, it had better not be me paying for trying to help you. This issue is far too important to be wasting 'potential votes' (for you/us) because 'your method' does not work (for me). All call attempts - and THIS message was typed - using Firefox browser & Fire TV 'box' crappy virtual keyboard, with Alexa voice remote (no voice control of keyboard). If you want our 'help/votes', you need to fix 'your method'. If the cause of the problem is outside of your control, then I apologise for my possibly incorect assuptions. I will try contact via a different route. Thanks for making myself & other readers of Wikipedia articles aware of this issue.

While trying to use 'your method' of either contacting, or being contacted by, 'an MEP' about the issue, I was disconnected TWICE during that call to me. I was NOT at ANY point, connected to either the Female MEP (call 1), nor the Male MEP (call 4). My 2nd&3rd call tries were 'rejected' due to 'whoops' error! wtf???? Has ANYBODY had an input with ANY MEP using 'your method' of contact? It has failed FOUR TIMES for me. I am in the UK. I used a mobile phone number each time. IF the number called by 'your method' MUST be a 'geographial landline number', then you should say that on the 'call now' page! Last point is: Who pays for these calls? Being that I never got connected to a live person, not even once after four attempts, it had better not be me paying for trying to help you. This issue is far too important to be wasting 'potential votes' (for you/us) because 'your method' does not work (for me). All call attempts - and THIS message was typed - using Firefox browser & Fire TV 'box' crappy virtual keyboard, with Alexa voice remote (no voice control of keyboard). If you want our 'help/votes', you need to fix 'your method'. If the cause of the problem is outside of your control, then I apologise for my possibly incorect assuptions. I will try contact via a different route. Thanks for making myself & other readers of Wikipedia articles aware of this issue.

All Replies (2)

more options

It is now too late (for me at least) to add my 'vote' in support of mozillas position to REJECT Article 13 as described on the Wikipedia page that brought the issue to MY attention, but also the page 'linked to' by a 'banner ad' on the same 'WikiP' page. To Mozilla in particular, if the only reason I saw ANY mention (on WikiP) of Article 13 is because of my use of FF browser on Fire TV, then you did a very poor job of letting people know, in time for people to respond in 'your' & perhaps their own 'favour'. NOT ENTIRELY 'your' fault, since don't watch, listen to 'news' or read 'news'papers, so if I did I could have responded in time - maybe. Also, above 'OP' was written & posted a lot more than '1 day' ago - more like 3 or 4. 2ay is now JULY 5th.

more options

Do you mean there was a problem connecting your call using this page:

https://changecopyright.org/call-now

I'm not sure what technology is or was used by that page, so it's difficult to troubleshoot whether there could have been a permissions problem on Firefox's side (e.g., access to your microphone) or an issue on the server.