Closed
Bug 1234465
Opened 9 years ago
Closed 6 years ago
Drop link "SeaMonkey.be Extension list" and clean up community info on SeaMonkey website
Categories
(SeaMonkey :: Website, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RainerBielefeldNG, Assigned: pg99696)
References
()
Details
Attachments
(4 files)
Currently it looks like an unconditioned recommendation to download add-ons via <http://users.skynet.be/fa258499/extensions.html>. But contents of that page is very outdated, a warning should be added.
Comment 1•9 years ago
|
||
That page, with "SeaMonkey.be" in the title but a URL for some Belgian user's user site (and with his actual login rather than an alias) was last updated on 2009-08-07, at the time of SeaMonkey 1.1.17 and before the first Toolkit Transition alpha builds. The FAQ that goes with it is equally obsolete. Pages at users.skynet.be/xxxxxxxx/ and below, where xxxxxxxx is an 8-character alphanumeric username (which can be replaced by a user-chosen alias of any length) can only be modified over ftp, by opening ftp://users.skynet.be/ with the 8-character username as the username and the correct password chosen by the user. I suspect that Skynet user fa258499 is AWOL or maybe forgot to remove that page when he switched over to Chrome, Opera, or what-have-you. Without his password no one can modify the page (unless he stops paying his dues for his Internet connection, in which case Skynet, now Proximus, might someday take the site down). AFAIK the only thing we can do is avoid linking to it, but if Google mentions it in the results for a search on SeaMonkey, then I guess we can do nothing about that particular aspect of the problem, unless we can convince MoFo to act in one of two ways: (a) negotiate with Google that they blacklist that site in their listings as "obsolete information". I doubt Google would accept. (b) start a trial "against person or persons unknown" in a Belgian court of law for abuse of the SeaMonkey trademark, which IIUC still "belongs" to MoFo. I doubt MoFo will agree to do that, considering the difference in law systems (written "French-style" law vs. Common "British-style" Law) and in languages (French or Dutch vs. English), to say the least.
Comment 2•9 years ago
|
||
I tried to contact him (or her) by email, but the message bounced, as follows: Delivery to the following recipient failed permanently: fa258499@skynet.be Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domain skynet.be by mx101.skynet.be. [195.238.20.25]. The error that the other server returned was: 550 #5.1.0 Address rejected. Either Skynet regards me as a spammer, or the user doesn't exist anymore. I suspect the former, because earlier today (or yesterday depending on your timezone) I got a bounce from Skynet for a family message (with one "To" and five "Cc", of which two were at @skynet.be) with the error message "Suspected spam, under investigation". I'll attach the message itself as a message/rfc822 attachment.
Comment 3•9 years ago
|
||
Updated•9 years ago
|
Attachment #8700984 -
Attachment mime type: text/plain → message/rfc822
Comment 4•8 years ago
|
||
That's BenoitRen's old website. He hasn't been active in SeaMonkey since graduating. I think it's best to remove that link as he's rather unlikely to be back.
Reporter | ||
Comment 5•8 years ago
|
||
The "how to hack extensions" still might have some interesting hints, and may be experienced users / add-on-hackers can find som work. Also "How to hack extensions to make them compatible with SeaMonkey" might be interesting. So if there is a place for hints for possibly interested users where they might search, te link should be moved to there. But for normal users that repository only will be worrying. So please drop that link
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Add warning hint that contents of "SeaMonkey.be Extension list" is outdated → Drop link "SeaMonkey.be Extension list"
Comment 6•8 years ago
|
||
(In reply to Rainer Bielefeld from comment #5) > The "how to hack extensions" still might have some interesting hints, and > may be experienced users / add-on-hackers can find som work. Also "How to > hack extensions to make them compatible with SeaMonkey" might be > interesting. So if there is a place for hints for possibly interested users > where they might search, the link should be moved to there. The place would be in developer.mozilla.org. There is already a page there regarding how to adapt an extension to SeaMonkey. However all that is now subsumed by the SeaMonkey Addon Converter. > But for normal users that repository only will be worrying. > So please drop that link Agreed.
Updated•6 years ago
|
Product: Websites → SeaMonkey
Comment 7•6 years ago
|
||
Pankaj, maybe you would like to work on this one. I think the following Links on https://www.seamonkey-project.org/community can be removed or altered: Alter: Move the a new "Other Web Resources" links sections at the bottom. Not much in it for SeaMonkey anymore. Planet Mozilla http://planet.mozilla.org/ Bug Writing Guidelines > https://developer.mozilla.org/En/Bug_Writing_Guidelines is now: > https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Drop: Mozilla User Community Sites International Mozilla Sites both redirect to https://www.mozilla.org/en-US/contribute/ There is nothing on this page useful for SeaMonkey users anymore. Rainer, what do you think?
Flags: needinfo?(pg99696)
Flags: needinfo?(RainerBielefeldNG)
Assignee | ||
Comment 8•6 years ago
|
||
(In reply to Frank-Rainer Grahl (:frg) from comment #7) > Pankaj, > > maybe you would like to work on this one. Thanks, I would really like to work on this. > > I think the following Links on https://www.seamonkey-project.org/community > can be removed or altered: > > Alter: > > Move the a new "Other Web Resources" links sections at the bottom. Not much > in it for SeaMonkey anymore. I am not able to understand this thing. Can you please explain more about it? > Planet Mozilla > http://planet.mozilla.org/ > > Bug Writing Guidelines > > https://developer.mozilla.org/En/Bug_Writing_Guidelines > is now: > > https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Okay, this can be done. > Drop: > > Mozilla User Community Sites > International Mozilla Sites > both redirect to https://www.mozilla.org/en-US/contribute/ These will be removed. > There is nothing on this page useful for SeaMonkey users anymore. > > Rainer, > what do you think?
Flags: needinfo?(pg99696) → needinfo?(frgrahl)
Assignee | ||
Comment 9•6 years ago
|
||
(In reply to Pankaj Garg from comment #8) > (In reply to Frank-Rainer Grahl (:frg) from comment #7) > > Pankaj, > > > > maybe you would like to work on this one. > Thanks, I would really like to work on this. > > > > I think the following Links on https://www.seamonkey-project.org/community > > can be removed or altered: > > > > Alter: > > > > Move the a new "Other Web Resources" links sections at the bottom. Not much > > in it for SeaMonkey anymore. > I am not able to understand this thing. Can you please explain more about it? > > Planet Mozilla > > http://planet.mozilla.org/ > > > > Bug Writing Guidelines > > > https://developer.mozilla.org/En/Bug_Writing_Guidelines > > is now: > > > https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines > Okay, this can be done. > > Drop: > > > > Mozilla User Community Sites > > International Mozilla Sites > > both redirect to https://www.mozilla.org/en-US/contribute/ > These will be removed. > > There is nothing on this page useful for SeaMonkey users anymore. > > > > Rainer, > > what do you think? One more thing I want to ask, will I remove "SeaMonkey.be Extension list" section also?
Comment 10•6 years ago
|
||
> One more thing I want to ask, will I remove "SeaMonkey.be Extension list" section also? Yes this is obsolete. >> Alter: >> >> Move the a new "Other Web Resources" links sections at the bottom. Not much >> in it for SeaMonkey anymore. > I am not able to understand this thing. Can you please explain more about it? It is a weblog and there is some general content in it which might be useful to SeaMonkey users so we should keep it. But I think we should move this entry down to the end. The ones with SeaMonkey specific content should come first.
Flags: needinfo?(frgrahl)
Comment 11•6 years ago
|
||
Moving it down like in the picture.
Assignee | ||
Comment 12•6 years ago
|
||
(In reply to Frank-Rainer Grahl (:frg) from comment #10) > > One more thing I want to ask, will I remove "SeaMonkey.be Extension list" section also? > > Yes this is obsolete. > Okay. > >> Alter: > >> > >> Move the a new "Other Web Resources" links sections at the bottom. Not much > >> in it for SeaMonkey anymore. > > I am not able to understand this thing. Can you please explain more about it? > > It is a weblog and there is some general content in it which might be useful > to SeaMonkey users so we should keep it. But I think we should move this > entry down to the end. The ones with SeaMonkey specific content should come > first. Okay. Got it.
Assignee | ||
Comment 13•6 years ago
|
||
Please assign this issue to my name.
Updated•6 years ago
|
Assignee: nobody → pg99696
Status: NEW → ASSIGNED
Reporter | ||
Comment 14•6 years ago
|
||
(In reply to Frank-Rainer Grahl (:frg) from comment #7) > what do you think? I agree!
Flags: needinfo?(RainerBielefeldNG)
Assignee | ||
Comment 15•6 years ago
|
||
Sorry for delay. Please review my patch file.
Attachment #8990534 -
Flags: review?(frgrahl)
Comment 16•6 years ago
|
||
Comment on attachment 8990534 [details] [diff] [review] 1234465-seamonkey.patch Great! Big thanks.
Attachment #8990534 -
Flags: review?(frgrahl) → review+
Comment 17•6 years ago
|
||
https://hg.mozilla.org/SeaMonkey/seamonkey-project-org/rev/3bd14b931118e493d6372ac02efbb535ee06331a
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Summary: Drop link "SeaMonkey.be Extension list" → Drop link "SeaMonkey.be Extension list" and clean up community info on SeaMonkey website
Version: unspecified → Production
You need to log in
before you can comment on or make changes to this bug.
Description
•