How to remove a bug report attachment?

users
#1

I just discovered that a rtf file I attached as an example file when I reported a bug with rtf imports losing the register tags is now *very* available when doing a Google search.
The problem is that this file was never meant to be public, as it contains a short genealogical report with living people in it. This is not even legal to publish on the net.
I never thought that such file attachements would be made publicly available!!!

How is it possible to get this RTF file removed/deleted?

The bug was fixed BTW..

#2

Bjørn K Nilssen wrote:

I just discovered that a rtf file I attached as an example file when I
reported a bug with rtf imports losing the register tags is now *very*
available when doing a Google search.
The problem is that this file was never meant to be public, as it
contains a short genealogical report with living people in it. This is
not even legal to publish on the net.
I never thought that such file attachements would be made publicly
available!!!

How is it possible to get this RTF file removed/deleted?

The bug was fixed BTW..

      This may or may not work: Try going to the Bug page and leave a comment that you want your file to be removed. They may or may not do so. Also, it may take a couple of days before anyone sees your message.

--Dan

#3

You might want to contact the Service Maintainers via the
sitewranglers@lists.freedesktop.org
Mailing List.

I assume that you don't need to be subscribed to send them a mail, but if you
are not, it might take a while until your mail gets moderated.

List info:
http://lists.freedesktop.org/mailman/listinfo/sitewranglers

Cheers,
Nino

#4

Thanks!
I already did that, but I guess I'll have to wait a few days to see if anything happens.
I also managed to remove/change the file name, which shows the rtf with all tags visible. But the Google 'Show as HTML' still shows the fully readable document :frowning:

#5

Hi :slight_smile:
If you uploaded the file to somewhere then try goign back to where you uploaded it and remove it from there.

I had a look through the thread
http://nabble.documentfoundation.org/rtf-import-broken-in-3-5-1-td3877445.html
but i couldn't find the upload link in there.  If you did use Nabble then you can go back to your post and edit out the link.  Subsequent replies might be more difficult to deal with but people here are usually willing to help.

Another way might be to email "postmaster" here but i can't find the right address right now.  The postmaster address might be in
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/

Best first thing to try is fidning where you uploaded the file and see if you can remove it from there. 
Regards from
Tom :slight_smile:

#6

Hi :slight_smile:
If you uploaded the file to somewhere then try goign back to where you uploaded it and remove it from there.
I had a look through the thread
http://nabble.documentfoundation.org/rtf-import-broken-in-3-5-1-td3877445.html
but i couldn't find the upload link in there. If you did use Nabble then you can go back to your post and edit out the link. Subsequent replies might be more difficult to deal with but people here are usually willing to help.

Another way might be to email "postmaster" here but i can't find the right address right now. The postmaster address might be in
http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/

Best first thing to try is fidning where you uploaded the file and see if you can remove it from there.

The bug is at https://bugs.freedesktop.org/show_bug.cgi?id=48193
The only thing I could do was to tag it as 'obsolete', which doesn't stop Google from indexing it.
I could also change the file name and MIME type, but not remove it :frowning:
It still pops up first when Googling for 'Magnus Hildershavn', and the 'Show HTML' still shows the formatted original file :frowning:
I've been on several closed and open beta teams through the years, but I have never ever before seen any of my attached/posted example files popping up on Google!
IMO it is not a good policy to make such files available to robots.

Regards

#7

Hi :) 
Ahhh.  I see.

When i tried googling the suggestion it came up 2nd, not 1st.  For other people it may appear much lower down.  Still the fact it appears at all is the problem, not the exact position.

I don't know if the problem has already been sorted out but when i did click on the google link or the bug-report's link i got a mess of what appeared to be fairly garbled coding, such as ...

par \pard\fi0\li1832\plain\f3\fs20

Is it possible to further edit the contents of the attachment to make it even more incomprehensible?

Since the attachment is on the bug-reporting site rather than the email-list i don't think postmaster would be able to help.  Is there a devs mailing list to ask?  I think posting a bug-report and adding a comment to the existing report has been the best way to contact the devs tbh but if there is a list then it might be worth contacting them there too. 
Regards from
Tom :slight_smile:

#8

Hi :)Ahhh. I see.

When i tried googling the suggestion it came up 2nd, not 1st. For other people it may appear much lower down. Still the fact it appears at all is the problem, not the exact position.

I don't know if the problem has already been sorted out but when i did click on the google link or the bug-report's link i got a mess of what appeared to be fairly garbled coding, such as ...
par \pard\fi0\li1832\plain\f3\fs20

Is it possible to further edit the contents of the attachment to make it even more incomprehensible?

I made several attempts, but they all ended up as new comments, while the original text was unchanged.

Since the attachment is on the bug-reporting site rather than the email-list i don't think postmaster would be able to help. Is there a devs mailing list to ask? I think posting a bug-report and adding a comment to the existing report has been the best way to contact the devs tbh but if there is a list then it might be worth contacting them there too.

I guess that after I added the bug comment I'll have to wait a few days to see if anything happens?
I also sent a mail/request to that listwrangler@.. address.

Problem is that I was contacted by one of those whose data was now made public, wondering how this could have happened, as I've told everybody that info on living persons would not be made public.
It is quite embarassing..

#9

Hi,

I guess that after I added the bug comment I'll have to wait a few days to see
if anything happens?

Nobody will read this comment.

I also sent a mail/request to that listwrangler@.. address.

hopefully you used the right destination address (it's sitewranglers@..., not
listwranglers...)

Problem is that I was contacted by one of those whose data was now made public,
wondering how this could have happened, as I've told everybody that info on
living persons would not be made public.
It is quite embarassing..

Internet *is* public and therefore should be used with care.

Nino

#10

Hi,

I guess that after I added the bug comment I'll have to wait a few days to see
if anything happens?

Nobody will read this comment.

Are you sure about that?
After a few unsuccessful attempts at removing it I found that a few new comments had been added.
Then I received a mail saying that a person who was following the topic had 'unsubscribed' - probably because he received too many nonsense-messages/comments?

I also sent a mail/request to that listwrangler@.. address.

hopefully you used the right destination address (it's sitewranglers@..., not
listwranglers...)

Sorry about that - yes, I did use the right address, and so far I have received a message saying that it will be moderated because I'm not a subscriber to that list - but eventually will be posted there, if it passes the moderation gate...

Problem is that I was contacted by one of those whose data was now made public,
wondering how this could have happened, as I've told everybody that info on
living persons would not be made public.
It is quite embarrassing..

Internet *is* public and therefore should be used with care.

Yes, but I have always considered such bug sites as un-indexed by and invisible to search engines, like PM/DM's on forums and Facebook etc. Apparently I was wrong..

#11

Bug-tracking systems of most (all?) free and open source software are public.

If in doubt, try opening any bug report in another browser or "Private mode".
If it is readable for you, then it is readable for search engine crawler.
Of course pages may provide <meta name="Robots">, but it's only up to crawler
authors if they comply these. One search engine will, another will not. The
most popular, Google, currently does comply to these.

#12

Yes, but I have always considered such bug sites as un-indexed by and
invisible to search engines, like PM/DM's on forums and Facebook etc.
Apparently I was wrong..

Bug-tracking systems of most (all?) free and open source software are public.

If in doubt, try opening any bug report in another browser or "Private mode".
If it is readable for you, then it is readable for search engine crawler.

Yes, but the attachements are not really readable by me directly, and neither do they need to be to the robots. Finding info about the bugs on Google is fine, but as attachments are not really part of the page content of those bug pages I don't think it should be made available for indexing by crawlers.

Of course pages may provide <meta name="Robots">, but it's only up to crawler
authors if they comply these. One search engine will, another will not. The
most popular, Google, currently does comply to these.

Exactly - and as most people use Google it would prevent most people from seeing it.