XPost: alt.html

On 10/19/2021 8:40 PM, Dale wrote:

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?

did a web search and found this ...

https://www.w3docs.com/snippets/html/open-hyperlink-in-a-new-window.html

for a new window ...

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

can't quite see the new tab


--
Mystery? -> https://www.dalekelly.org/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?


--
Mystery? -> https://www.dalekelly.org/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/19/2021 5:53 PM, Dale wrote:

On 10/19/2021 8:40 PM, Dale wrote:

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?

did a web search and found this ...

https://www.w3docs.com/snippets/html/open-hyperlink-in-a-new-window.html

for a new window ...

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

can't quite see the new tab

Whether the new page opens in a new tab or new window is a function of
the user's setting for their browser. Also, if the user's browser
setting is to open a new tab, whether that tab remains behind the prior
tab or is in front of it is a function of another user's setting.
Nothing you do in the HTML will affect whether the user gets a new
window or a new tab, and nothing will affect whether a new tab is behind
or in front of the prior tab.

--
David E. Ross
"A Message to Those Who Are Not Vaccinated"
See my <http://www.rossde.com/index.html#vaccine>.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/19/21 9:06 PM, David E. Ross wrote:

nothing will affect whether a new tab is behind or in front

That may be the case today. But I remember in the early to mid 2000s
first the pop ups (over / front) and then the pop unders (under /
behind) wars. So there was a way that you could influence things to be
behind or in front years ago. I don't know if it is still the case today.

Then there are pop-up blockers which will thwart this.

And let's not speak about the div tags with Z value that puts them in
front of all of the content in the single page / tab.



--
Grant. . . .
unix || die

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

On 10/19/21 6:53 PM, Dale wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

My experience with this years ago surprised me somewhat.

Don't think of it as a "new tab" so much as a "named tab". Meaning that
the link gets opened in the tab with the name of the target. That tab
will be new if it doesn't already exist. If it does already exist, it
will be the existing window.

With this in mind, I took to having links open in different targets:

<a href="https://www.w3docs.com/" target="w3docs">w3docs</a>
<a href="https://www.wikipedia.com/" target="wikipedia">Wikipedia</a>

The value of the name can be random if you want. But the different
links should use different target values if you want different tabs for
them.

At least that's how I remember things being 10+ years ago.



--
Grant. . . .
unix || die

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

On 10/20/2021 1:28 AM, Grant Taylor wrote:

On 10/19/21 6:53 PM, Dale wrote:

<p>This <a href="https://www.w3docs.com/"
target="_blank">hyperlink</a> will open in a new tab. </p>

My experience with this years ago surprised me somewhat.

Don't think of it as a "new tab" so much as a "named tab".  Meaning that
the link gets opened in the tab with the name of the target.  That tab
will be new if it doesn't already exist.  If it does already exist, it
will be the existing window.

With this in mind, I took to having links open in different targets:

<a href="https://www.w3docs.com/" target="w3docs">w3docs</a>
<a href="https://www.wikipedia.com/" target="wikipedia">Wikipedia</a>

The value of the name can be random if you want.  But the different
links should use different target values if you want different tabs for
them.

At least that's how I remember things being 10+ years ago.

Thank YOU!

--
Mystery? -> https://www.dalekelly.org/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/19/2021 11:06 PM, David E. Ross wrote:

On 10/19/2021 5:53 PM, Dale wrote:

On 10/19/2021 8:40 PM, Dale wrote:

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?

did a web search and found this ...

https://www.w3docs.com/snippets/html/open-hyperlink-in-a-new-window.html

for a new window ...

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

can't quite see the new tab

Whether the new page opens in a new tab or new window is a function of
the user's setting for their browser. Also, if the user's browser
setting is to open a new tab, whether that tab remains behind the prior
tab or is in front of it is a function of another user's setting.
Nothing you do in the HTML will affect whether the user gets a new
window or a new tab, and nothing will affect whether a new tab is behind
or in front of the prior tab.

Thank YOU!

--
Mystery? -> https://www.dalekelly.org/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

David E. Ross:

On 10/19/2021 5:53 PM, Dale wrote:

On 10/19/2021 8:40 PM, Dale wrote:

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?

did a web search and found this ...

https://www.w3docs.com/snippets/html/open-hyperlink-in-a-new-window.html

for a new window ...

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

can't quite see the new tab

Whether the new page opens in a new tab or new window is a function of
the user's setting for their browser. Also, if the user's browser
setting is to open a new tab, whether that tab remains behind the prior
tab or is in front of it is a function of another user's setting.
Nothing you do in the HTML will affect whether the user gets a new
window or a new tab, and nothing will affect whether a new tab is behind
or in front of the prior tab.

Wrong - target="_blank" will always open a link a a new tab or window
and the user can not prevent this.

Therefore I generally recommend against this! I user can always decide
to open a link in a new tab if he wants to - but if target="_blank" is
present a user can NOT force the browser to open the link in the current tab/window. Mostly this is only done for SEO to keep the current web
site open even if you link to another site.

--
Arno Welzel
https://arnowelzel.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

In message <sko9mk$9r2$1@tncsrv09.home.tnetconsulting.net> Grant Taylor <gtaylor@tnetconsulting.net> wrote:

On 10/19/21 6:53 PM, Dale wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

My experience with this years ago surprised me somewhat.

Don't think of it as a "new tab" so much as a "named tab". Meaning that
the link gets opened in the tab with the name of the target. That tab
will be new if it doesn't already exist. If it does already exist, it
will be the existing window.

With this in mind, I took to having links open in different targets:

<a href="https://www.w3docs.com/" target="w3docs">w3docs</a>
<a href="https://www.wikipedia.com/" target="wikipedia">Wikipedia</a>

The value of the name can be random if you want. But the different
links should use different target values if you want different tabs for
them.

At least that's how I remember things being 10+ years ago.

s is all correct, but _blank and _new are special cases.



--
Like the moment when the brakes lock/And you slide towards the big
truck/You stretch the frozen moments with your fear

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the
user's preferences). It opens a new WINDOW, which the Browser may decide
to open as a tab, or not.

It is also possible to attempt to open a new window using JavaScript, but
most browsers block this as abusive behavior (again, depending on user preferences, but blocking so-called pop-ups is often the default
behavior).


--
First we must assume a spherical cow.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/20/2021 7:13 AM, Arno Welzel wrote:

David E. Ross:

On 10/19/2021 5:53 PM, Dale wrote:

On 10/19/2021 8:40 PM, Dale wrote:

Hi!

I know how to code a link.

But can you code that link to open in a new browser tab?

Or a new browser window?

did a web search and found this ...

https://www.w3docs.com/snippets/html/open-hyperlink-in-a-new-window.html >>>
for a new window ...

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

can't quite see the new tab

Whether the new page opens in a new tab or new window is a function of
the user's setting for their browser. Also, if the user's browser
setting is to open a new tab, whether that tab remains behind the prior
tab or is in front of it is a function of another user's setting.
Nothing you do in the HTML will affect whether the user gets a new
window or a new tab, and nothing will affect whether a new tab is behind
or in front of the prior tab.

Wrong - target="_blank" will always open a link a a new tab or window
and the user can not prevent this.

Therefore I generally recommend against this! I user can always decide
to open a link in a new tab if he wants to - but if target="_blank" is present a user can NOT force the browser to open the link in the current tab/window. Mostly this is only done for SEO to keep the current web
site open even if you link to another site.

No, you do not understand. The markup target="_blank" will open a new
page without closing the page containing that markup. Whether that new
page is in a new tab or a new window is controlled by the user's
browser, not by the markup.

In the version of SeaMonkey that I use, there are three separate sets of options:
* For a link intended to open a new window (e.g., target="_blank") when viewing someone else's Web page, I have the option of (1) replacing the
current window or tab, (2) opening a new tab in the current window, or
(3) actually opening a new window. I have selected option #2.
* When a script wants to open a new window, I have the option of (1)
open a new tab in the current window, (2) replace the current window, or
(3) open a new window. I have selected option #1.
* For a link not in a Web page in my browser but in some other
application (e.g., in an E-mail message [not using SeaMonkey's E-mail],
in the About window of some application), I have the option of (1)
replace the current browser window, (2) open a new tab in the current
browser window, or (3) launch a new browser window. I have selected
option #3.

NOTE WELL: I control where the new Web page appears. The parent Web
page -- my own or someone else's -- or other application does NOT
control this.

--
David E. Ross
"A Message to Those Who Are Not Vaccinated"
See my <http://www.rossde.com/index.html#vaccine>.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

On 10/20/2021 10:17 AM, Lewis wrote:

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the user's preferences). It opens a new WINDOW, which the Browser may decide
to open as a tab, or not.

It is also possible to attempt to open a new window using JavaScript, but most browsers block this as abusive behavior (again, depending on user preferences, but blocking so-called pop-ups is often the default
behavior).

Thank YOU!

--
Mystery? -> https://www.dalekelly.org/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

Lewis:

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the user's preferences). It opens a new WINDOW, which the Browser may decide
to open as a tab, or not.

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT
prevent this if target="_blank" is present.

Therefore I recommend NOT to do this on a regular basis but only for
very special cases where the user will understand *why* a new tab or
window will open when clicking the link.


--
Arno Welzel
https://arnowelzel.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

David E. Ross:

On 10/20/2021 7:13 AM, Arno Welzel wrote:

[...]

Wrong - target="_blank" will always open a link a a new tab or window
and the user can not prevent this.

Therefore I generally recommend against this! I user can always decide
to open a link in a new tab if he wants to - but if target="_blank" is
present a user can NOT force the browser to open the link in the current
tab/window. Mostly this is only done for SEO to keep the current web
site open even if you link to another site.

No, you do not understand. The markup target="_blank" will open a new
page without closing the page containing that markup. Whether that new
page is in a new tab or a new window is controlled by the user's
browser, not by the markup.

No - the user can *not* prevent getting a new tab or window.

In the version of SeaMonkey that I use, there are three separate sets of options:

[...]

And *no* option offers to *ignore* targets.

NOTE WELL: I control where the new Web page appears. The parent Web

No - you don't. If target attribute is present you CAN NOT prevent a new
tab or window to be opened. You can only decide if it's a tab or a
window. But in any case a *new* tab or window *will* open if a link
contains target="_blank".

On the other hand - *without* target="_blank" you *ARE* in control. You
can decide just to click the link and open it in the current tab *or*
you can use the context menu for the link (right mouse button or touch
and hold the link for a while on touch devices) and choose to open it in
a new tab or window.

I hope you understand now what my point is here.



--
Arno Welzel
https://arnowelzel.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

Grant Taylor wrote:

On 10/19/21 6:53 PM, Dale wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

My experience with this years ago surprised me somewhat.

Don't think of it as a "new tab" so much as a "named tab". Meaning that
the link gets opened in the tab with the name of the target.
That tab will be new if it doesn't already exist. If it does already
exist, it will be the existing window.

As defined in the HTML Specification(s), that is not so for certain reserved “target” attribute values:

"_self": same window/tab
"_blank": new tab (tabbed browsing) or window (windowed browsing)
"_parent": parent frame
"_top": topmost frame

At least that's how I remember things being 10+ years ago.

Next time, RTFM instead:

<https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a>

The “target” attribute can be used with named frames in the same way.

--
PointedEars
FAQ: <http://PointedEars.de/faq> | <http://PointedEars.de/es-matrix> <https://github.com/PointedEars> | <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

Lewis wrote:

It is also possible to attempt to open a new window using JavaScript, but most browsers block this as abusive behavior (again, depending on user preferences, but blocking so-called pop-ups is often the default
behavior).

The default behavior is often to block popups *that the user did not cause consciously*, different from what you describe in the first sentence:
*those* popups are NOT blocked by default.

A proper way to do this would be

<a href='foo' target='bar'
onclick='return !window.open(this.href, this.target, "width=200,height=200")'
>…</a>

The advantage of additionally using client-side DOM scripting here is that
it is more likely that a window will be opened instead of a tab, that properties of that window can be suggested (here: viewport width and height,
in pixels), and that fallback approaches can be tried (for example, showing
an element instead of a popup if the latter does not work).

However, spaghetti code like above should be avoided, for example by using
a custom method that is only passed the essential information –

<a href='foo' target='bar'
onclick='return !my.open(this, {width: 200, height: 200})'
>…</a>

– or by adding event listeners dynamically (caveat: the listeners will not work before the document was loaded), for example

document.addEventListener('load', function () {
document.links['link-foo'].addEventListener(
'click',
function (e) {
if (my.open(
e.target || e.srcElement,
{width: 200, height: 200}))
{
e.preventDefault();
return false;
}
},
false);
});

…

<a href='foo' target='bar' id='link-foo'>…</a>

A possibility for a fallback then would be

let my = {
open: function (target, props) {
let w = null;

if (!(w = window.open(target.href, target.target,
Object.entries(props).map((entry) => `${entry[0]}=${entry[1]}`)
.join(','))))
{
/* If the popup window cannot be created, create an element box
with the content */
if (…)
{
/* If that worked, prevent default action */
w = true;
}
}

/* Prevent default action if any of the above worked */
return w;
}
};

--
PointedEars
FAQ: <http://PointedEars.de/faq> | <http://PointedEars.de/es-matrix> <https://github.com/PointedEars> | <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | Please do not cc me./Bitte keine Kopien per E-Mail.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

In message <4375919.LvFx2qVVIh@PointedEars.de> Thomas 'PointedEars' Lahn <PointedEars@web.de> wrote:

Lewis wrote:

It is also possible to attempt to open a new window using JavaScript, but
most browsers block this as abusive behavior (again, depending on user
preferences, but blocking so-called pop-ups is often the default
behavior).

The default behavior is often to block popups *that the user did not cause consciously*, different from what you describe in the first sentence:
*those* popups are NOT blocked by default.

A proper way to do this would be

<a href='foo' target='bar'
onclick='return !window.open(this.href, this.target, "width=200,height=200")'
>…</a>

thankfully not many people do user-hostile shot like that. If I got to a
site that did that I would drop into the shell at add them to my hosts
list so I could never load the site again.

document.addEventListener('load', function () {
document.links['link-foo'].addEventListener(
'click',
function (e) {
if (my.open(
e.target || e.srcElement,
{width: 200, height: 200}))
{
e.preventDefault();
return false;
}
},
false);
});

Not HTML now, so not really relevant to this discussion. But yeah, don't
do shit like that, it makes people very angry when new windows open on
their screens.


--
Given your quest-heavy lifestyle, there’s no guarantee any of you will live to
see Christmas.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

In message <itdaphFt4v8U2@mid.individual.net> Arno Welzel <usenet@arnowelzel.de> wrote:

Lewis:

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote:

<p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a>
will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the
user's preferences). It opens a new WINDOW, which the Browser may decide
to open as a tab, or not.

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT
prevent this if target="_blank" is present.

It certainly is possible, though I don't know if any current browsers
support that user option. But yes, there is nothing preventing a browser
for having an option "Do not allow clicks to open a new window."

Therefore I recommend NOT to do this on a regular basis but only for
very special cases where the user will understand *why* a new tab or
window will open when clicking the link.

Opening new windows for users is a speedy way to piss them off, and
using pop-=up windows is a sure way to lose users and have them never
return to your site.

--
One tequila, two tequila, three tequila, floor.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

On 10/23/2021 4:03 PM, Lewis wrote:

In message <itdaphFt4v8U2@mid.individual.net> Arno Welzel <usenet@arnowelzel.de> wrote:

Lewis:

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote: >>>> <p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a> >>>> will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the
user's preferences). It opens a new WINDOW, which the Browser may decide >>> to open as a tab, or not.

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT
prevent this if target="_blank" is present.

It certainly is possible, though I don't know if any current browsers
support that user option. But yes, there is nothing preventing a browser
for having an option "Do not allow clicks to open a new window."

Therefore I recommend NOT to do this on a regular basis but only for
very special cases where the user will understand *why* a new tab or
window will open when clicking the link.

Opening new windows for users is a speedy way to piss them off, and
using pop-=up windows is a sure way to lose users and have them never
return to your site.

My Web site includes a glossary of Internet terms, targeted to novices.
(There will always be novices.) Other pages on my site contain terms
defined in that glossary. Where that occurs, I have a link to the term
within the glossary; that link uses target="glossary".

According to the browser in use and its settings, the first time such a
link is clicked, this either opens a new tab or a new window, in either
case at the linked term. Subsequent clicks on links for other terms do
not open another glossary page but shift the existing glossary page to
the new term. This allows the user to maintain his or her place on the
page using the term while also seeing terms defined.

--
David E. Ross
"A Message to Those Who Are Not Vaccinated"
See my <http://www.rossde.com/index.html#vaccine>.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

On Sat, 23 Oct 2021 23:03:17 -0000 (UTC), Lewis wrote:

In message <itdaphFt4v8U2@mid.individual.net> Arno Welzel

<usenet@arnowelzel.de> wrote:

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT prevent this if target="_blank" is present.

It certainly is possible, though I don't know if any current browsers
support that user option. But yes, there is nothing preventing a browser
for having an option "Do not allow clicks to open a new window."

If I remember correctly, Firefox did have such an option back in the
day when web dee-zign-urz used target= a whole lot. I remember using
that option to cause such links to be opened in the same tab, unless
I Ctrl-clicked on them.

--
Stan Brown, Tehachapi, California, USA
https://BrownMath.com/
https://OakRoadSystems.com/

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

Lewis:

In message <itdaphFt4v8U2@mid.individual.net> Arno Welzel <usenet@arnowelzel.de> wrote:

Lewis:

In message <sknpai$ffl$1@dont-email.me> Dale <dale@dalekelly.org> wrote: >>>> <p>This <a href="https://www.w3docs.com/" target="_blank">hyperlink</a> >>>> will open in a new tab. </p>

No, the behavior of that is entirely up to the browser (and usually the
user's preferences). It opens a new WINDOW, which the Browser may decide >>> to open as a tab, or not.

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT
prevent this if target="_blank" is present.

It certainly is possible, though I don't know if any current browsers
support that user option. But yes, there is nothing preventing a browser
for having an option "Do not allow clicks to open a new window."

In fact no browser has this option - so it's pointless to mention that
this *could* be done technically to justify the use of target="_blank".


--
Arno Welzel
https://arnowelzel.de

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.html

In message <MPG.3bdf10046f75ba2198fe3a@news.individual.net> Stan Brown <the_stan_brown@fastmail.fm> wrote:

On Sat, 23 Oct 2021 23:03:17 -0000 (UTC), Lewis wrote:

In message <itdaphFt4v8U2@mid.individual.net> Arno Welzel

<usenet@arnowelzel.de> wrote:

Yes - but the browser WILL ALWAYS open something new! A user CAN NOT
prevent this if target="_blank" is present.

It certainly is possible, though I don't know if any current browsers
support that user option. But yes, there is nothing preventing a browser
for having an option "Do not allow clicks to open a new window."

If I remember correctly, Firefox did have such an option back in the
day

That's what I was thinking as well, but I cannot say for certain.

I think iCab and/or OmniWeb did this too, about 15-20 years ago.



--
'An appointment is an engagement to see someone, while a morningstar
is a large lump of metal used for viciously crushing skulls. It
is important not to confuse the two.'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)