Rick, didn't Anthony already explain to you, that it is not Greasemonkey that did this? And also he asked for further details to be able to maybe tell you whom to shout at instead of the Greasemonkey people that do not deserve to be the target of your anger as it is not Greasemonkey that does this?
Cheers Björn Am Samstag, 21. September 2019 21:06:23 UTC+2 schrieb Rick Bauer: > > Facebook has nothing to do with my post so please create a post related to > your post and your Facebook script. > > I want to know what makes greasemonkey admins think they know what scripts > I want to run and what on earth makes them think they have the right to > remove scripts I have chosen to install and run from my browser without my > knowledge or permission? > > I could understand no longer distributing it or allowing it to be hosted > on their site but I feel it is very disrespectful and likely illegal to > remove things from my browser without my knowledge or permission. > > It is not in any way related to facebook or the problems you are > describing so please don't confuse this thread with unrelated problems. > > On Sat, Sep 21, 2019 at 2:00 PM LWChris <lwc...@gmx.de <javascript:>> > wrote: > >> Just to make it clear: >> >> Greasemonkey or Greasemonkey scripts cannot delete Facebook posts >> directly, all any script could do is provide an easy way to automate what >> you'd have to do by hand on Facebook. So if there is the ability to delete >> an old Facebook post by clicking a "Delete" link and confirm a popup >> dialog, a dedicated script could click the link and confirm the popup for >> you. >> >> It sounds like you have such script that tries to automate deleting old >> posts, and chances are Facebook updated something on their side and now the >> script does no longer know what to do because the page's source code is now >> different at a certain part that the script needed to find the things it >> needed to click on. >> >> An arbitrary example to illustrate what I mean would be that the delete >> links were previously tagged with "fb-action-delete-post" and now they're >> named "fb-action-remove-post". The script tries to identify the delete link >> by looking for a post's "fb-action-delete-post" link; now it doesn't find >> that link, hence it doesn't know what to do and does nothing. >> >> Usually, script authors will fix such issues on their side and update the >> script at the website it was hosted on. However there a chance the script >> has been abandonned by the original author, or (s)he hasn't fixed it yet, >> or the automated update doesn't work. If you remember where you go the >> script from, try visiting that page and see if there have been any updates >> published. >> >> Chris >> Am 20.09.2019 um 23:23 schrieb Dan Almashy: >> >> While someone is on looking, can I ask why my greasemonkey doesn't >> delete my old facebook posts etc when I tell it to? I have tried it >> multiple times on firefox and it goes through the motions but never does >> actually delete anything. I have stuff from 9 years ago and just want to >> clear most of it other than recent stuff, maybe I need to do something >> other to make it work? >> >> >> On Friday, September 20, 2019 at 2:16:54 PM UTC-4, Rick Bauer wrote: >>> >>> What on earth makes anyone at greasemonkey think they have the mental >>> capacity to decide for me which scripts I want to run and more importantly >>> who feels they have the right to just remove scripts I use regularly from >>> MY browser? >>> >>> I'm not even sure that is legal without permission of the owner. >>> >>> This is completely disrespectful to your users and is an insult the same >>> as if you told your users you could care less how they feel or what they >>> want. >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "greasemonkey-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to greasemonkey-users+unsubscr...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/greasemonkey-users/da5c619d-e018-4a95-ae3e-8b84859ceb76%40googlegroups.com >> >> <https://groups.google.com/d/msgid/greasemonkey-users/da5c619d-e018-4a95-ae3e-8b84859ceb76%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "greasemonkey-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to greasemonkey-users+unsubscr...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/greasemonkey-users/228c35c6-bf95-0d6c-7b61-ba285637c4d2%40gmx.de >> >> <https://groups.google.com/d/msgid/greasemonkey-users/228c35c6-bf95-0d6c-7b61-ba285637c4d2%40gmx.de?utm_medium=email&utm_source=footer> >> . >> > > > -- > CONFIDENTIALITY NOTICE: This e-mail, including attachments, may include > restricted, protected, and/or proprietary information, and may be used > only > for the person or entity to which it is addressed. If the reader of this > e-mail is not the intended recipient or his or her authorized agent, the > reader is hereby notified that any dissemination, distribution or copying > of this e-mail is prohibited. If you have received this e-mail in error, > please notify the sender by replying to this message and delete this > e-mail > immediately. Notice: The disclosure of private information is strictly > prohibited by federal regulation. Unauthorized release of private > information may result in administrative, civil and criminal sanctions. > > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to greasemonkey-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/greasemonkey-users/fc2dfb65-76d4-426f-865b-52fa6cc526d7%40googlegroups.com.
