Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a25bc35c89617089

Jump to content

Talk:Oisc of Kent

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 2 years ago by Alarichall in topic Oisc v Æsc

Untitled

[edit]

The website http://www.angelfire.com/ego/et_deo/balthae_dynasty.wps.htm provides an alternate theory, that Oisc was not Hengest's son. Could this be possible? Perhaps this was the truth, but was 'changed' so that the Kings of Kent were deemed as descendants of Woden.

Deaþe gecweald 07:58, 30 March 2007 (UTC)Reply

If Oisc were really Hengest's son or grandson, the dynasty would have been called Hengistingas or Hengestingas. Some go so far as to claim that Hengest was mythical: personally I reckon he was real, but Oisc was most likely not related to him. —Preceding unsigned comment added by 82.10.100.97 (talk) 00:42, 13 January 2009 (UTC)Reply

Aescwine Association?

[edit]

Aisc/ Oisc and Aescwine seem to be associated with each other. They both live in eastern England and they both have a son with an ending name that uses a snapping tongue followed by the letter "a". Like Octa and Sledda. This is merely just my suspicious theory though, it may or may not make any differece.

Oisc v Æsc

[edit]

If he was King of Kent, what is the sense in Wikipedia continually using the Northumbrian form of his name, Oisc, rather than Æsc? Bede isn't the only source for his name. Paul S (talk) 10:57, 12 August 2014 (UTC)Reply

Nine years later, I have spelled out what's going on here! Alarichall (talk) 13:48, 8 October 2023 (UTC)Reply