Research view · Internetcore
The record
Every claim on the Internetcore page, with the kind of claim it is, its strength, the area it belongs to and the sources attached to it. Kind, strength and area are separate fields and are never merged. Untiered means the research supports the rule but sets no tier for it.
Back to Internetcore · The record as data · Brief.md
Coverage
- Research
- Partly sourced. 27 sources attached.
- Claims
- 115
- Documented
- 40 (Source attached: 40)
- Seen in the work
- 9
- Our reading
- 52
- Web translation
- 14
- Sources
- 27 on the record; 27 attached to a claim
- Open questions
- 7 open · 7 resolved
- Evidence images on the page
- 0
- Visuals made by Aesthetary
- 16
Areas
Claims
| ID | Claim | Kind of claim | Strength | Area | Sources |
|---|---|---|---|---|---|
| definition | Internetcore is a contemporary aesthetic that deliberately reconstructs and remixes the visual language of early personal computing and the web. | Our reading | — | — Recognition test | — |
| diagnostic | The diagnostic question: does the design intentionally aestheticize the visual language of obsolete computing or the early internet? Intent decides; age alone does not. | Our reading | — | — Recognition test | — |
| what | Internetcore treats obsolete digital interfaces as visual culture, borrowing from early websites, desktop operating systems, primitive browser interfaces and the vernacular graphics of the consumer internet. | Our reading | — | — Recognition test | — |
| intent | Internetcore is distinguished from old web design by intent, not by appearance: early sites looked the way they did because they had to; Internetcore recreates, exaggerates and recombines those conventions after the limits have gone. | Our reading | — | — Recognition test | — |
| sources-not-checklist | The source languages are not a checklist. Internetcore emerges from their deliberate quotation and recombination. | Our reading | — | — Recognition test | — |
| S-homepage | Tiled backgrounds; counters; badges; guestbooks; web rings; underlined links. | Our reading | — | — Recognition test | — |
| S-desktop | Windows; menus; dialogs; icons; folders; system controls. | Our reading | — | — Recognition test | — |
| S-browser | Chrome; address bars; status indicators; tabs and windows; loading states. | Our reading | — | — Recognition test | — |
| S-graphics | Pixels; GIF-like motion; bitmap assets; crude 3D; compressed imagery. | Our reading | — | — Recognition test | — |
| A1 | Interface becomes graphic material. | Our reading | — | — Recognition test | — |
| A2 | Digital resolution can remain visibly discrete. | Our reading | — | — Recognition test | — |
| A3 | Links, inputs, buttons and system controls may retain browser and OS associations. | Our reading | — | — Recognition test | — |
| A4 | Windows, dialogs and floating interface elements can replace conventional page sections. | Our reading | — | — Recognition test | — |
| A5 | Elements may appear primitive while being technically sophisticated underneath. | Our reading | — | — Recognition test | — |
| A6 | Badges, icons, cursors, separators, counters and tiny animations can function decoratively. | Our reading | — | — Recognition test | — |
| coherence | The visual language has to coherently reference internet and computing history, rather than using one nostalgic prop. | Our reading | — | — Recognition test | — |
| retrospective | Internetcore did not continue uninterrupted from the early web. Its retrospective quality is part of its identity. | Our reading | — | — History | — |
| H1 | Personal computing establishes the desktop-interface vernacular. | Our reading | — | — History | — |
| H2 | The public web develops its own visual conventions under severe technical constraints. | Our reading | — | — History | — |
| H3 | Personal homepages, portals, forums and increasingly sophisticated browser experiences diversify web culture. | Our reading | — | — History | — |
| H4 | Standardisation and professionalisation make many early conventions disappear. | Our reading | — | — History | — |
| H5 | Designers deliberately recover obsolete interface languages — as nostalgia, as cultural reference, and as resistance to homogeneous contemporary UI. | Our reading | — | — History | — |
| evidence-interpretation | Web 1.0 is historical evidence: its constraints were real. Internetcore is a later interpretation in which the constraints are quoted. | Our reading | — | — Boundary | — |
| B-y2k | Broader millennium-era futurism and consumer culture — not specifically about the internet itself. | Our reading | — | — Boundary | — |
| B-pixel | A rendering technique that can appear inside many aesthetics. On its own it classifies nothing. | Our reading | — | — Boundary | — |
| B-anti | Challenges conventional design norms. It need not reference obsolete computing at all. | Our reading | — | — Boundary | — |
| B-vapor | Nostalgia filtered through consumer and media culture, with its own music and art lineage. | Our reading | — | — Boundary | — |
| B-neo | Contemporary rawness and visible structure, without requiring internet nostalgia. | Our reading | — | — Boundary | — |
| L1 | Expose interface structure. Frames, bars and panels are visible, not hidden. | Our reading | — | Layout | — |
| L2 | Let hierarchy feel digital rather than editorial. | Our reading | — | Layout | — |
| L3 | Small modules can accumulate instead of becoming giant contemporary cards. | Our reading | — | Layout | — |
| L4 | Layering is legitimate when the desktop metaphor supports it. | Our reading | — | Layout | — |
| L5 | Imperfection should look intentional. | Our reading | — | Layout | — |
| L-metaphors | Three structural metaphors, each drawn from a source language: Document, Desktop, Portal. | Our reading | — | Layout | — |
| L-stack | On narrow screens the Desktop metaphor stops overlapping: windows stack in reading order, each keeping its title bar. Overlap that hides content on a phone is not a quotation, it is a bug. | Web translation | — | Layout | — |
| L-measure | The Document metaphor keeps a narrow measure even on wide screens — the narrow column survives as a chosen width, not a table limit. | Web translation | — | Layout | — |
| no-pixel-requirement | Internetcore does not require a pixel font. The typography must participate in the computing and internet reference. | Our reading | — | Typography | — |
| T-families | Four families of reference: system sans, bitmap or display, monospace, and the browser-default serif. | Our reading | — | Typography | — |
| T-costume | A pixel font everywhere is costume. | Our reading | — | Typography | — |
| T-jobs | Give each family one job: default serif for reading and display, system sans for interface, bitmap only where resolution is the subject (counters, status, specimens). | Web translation | — | Typography | — |
| T-size | Body text never in a bitmap face below 16px; bitmap faces render unevenly when scaled off their grid. | Web translation | — | Web translation: Accessibility | — |
| palette-source | There is no canonical Internetcore palette. Colour inherits from the digital reference being quoted: browser default, desktop UI, personal homepage, or a reduced contemporary reinterpretation. | Our reading | — | Color | — |
| C-values | Every colour value shown for a palette source is Aesthetary's; the saturated homepage set is adjusted so text on its grounds passes 4.5:1. | Web translation | — | Color | — |
| C-underline | Links stay distinguishable by more than colour — keep the underline. | Web translation | — | Web translation: Accessibility | — |
| radius | Rectangular interface primitives: hard edges, system-window geometry, pixel boundaries, native-control proportions. Rounded corners are not forbidden; they become suspicious when the interface reads as generic contemporary SaaS rather than obsolete computing. | Our reading | — | Interface | — |
| S-radius | Radius 0 on windows, fields and buttons. Where the quoted source itself rounds a corner, round only that element, and only to that degree. | Web translation | — | Interface | — |
| S-bevel | Depth comes from 1px bevels (light top-left, dark bottom-right), never from blurred shadows. | Web translation | — | Interface | — |
| UI-controls | Default-looking controls may retain browser and OS associations; windows, dialogs and floating elements can replace page sections. | Our reading | — | Interface | — |
| ui-translation | Historical Internetcore sources do not establish a canonical contemporary component library. The components shown are contemporary translations of the visual rules. | Web translation | — | Interface | — |
| UI-states | Every state, value and behaviour of the components shown: the bevel recipe, the extra outline on the default action, the sunken current-page marker and the block progress bar are Aesthetary's reconstruction. | Web translation | — | Interface | — |
| UI-a11y | Real form controls underneath; visible focus on everything; touch targets at least 32px tall; dialogs trap focus and close on Escape. | Web translation | — | Web translation: Accessibility | — |
| lofi-reason | Low fidelity should have a reason. Artefacts applied to everything are a filter, not Internetcore. | Our reading | — | Imagery | — |
| I-types | Six image types: compressed raster, GIF-like animation, bitmap icon, primitive CGI, webcam or personal imagery, scanned image. | Our reading | — | Imagery | — |
| M-vocab | A six-part motion vocabulary — blink, marquee travel, frame animation, loading and progress, cursor response, window movement — each either a historical behaviour or a contemporary recreation. | Our reading | — | Motion | — |
| M-reduced | Reduced motion should freeze the animation without removing the digital artefact that communicates the aesthetic. | Our reading | — | Motion | — |
| M-timing | Every timing value (4–8 frames per second, stepped; instant state changes; 1:1 window movement) and the limit of one looping element in view. | Web translation | — | Motion | — |
| M-a11y | Nothing flashes more than three times per second; honour prefers-reduced-motion; anything that moves for longer than five seconds can be paused. | Web translation | — | Web translation: Accessibility | — |
| refusal-1 | Internetcore requires a pixel font. No. Typography must participate in the reference; no face is required. | Our reading | — | — Misconception | — |
| refusal-2 | Internetcore has a canonical palette. No. Colour inherits from the source language being quoted. | Our reading | — | — Misconception | — |
| refusal-3 | Rounded corners are forbidden. No. They become suspicious once the interface reads as contemporary SaaS. | Our reading | — | — Misconception | — |
| refusal-4 | Internetcore is old web design. No. Web 1.0 is the source; Internetcore is the later quotation. | Our reading | — | — Misconception | — |
| unreliable-1 | = a pixel font | Our reading | Unreliable · our ranking | — Misconception | — |
| unreliable-2 | = an old website | Our reading | Unreliable · our ranking | — Misconception | — |
| unreliable-3 | = one nostalgic prop | Our reading | Unreliable · our ranking | — Misconception | — |
| meta-name-status | name status: Internet-culture term; where Internetcore and Webcore were first used is not yet on the record | Our reading | — | — History | — |
| meta-digital-translation | Personal sites, portfolios, small shops, archives and campaigns that quote an old interface on purpose | Web translation | — | — Context | — |
| kcc:layout-1 | Segmenting the surface into frames stands for the web the way a score display stands for game screens; Lialina calls frames even more recognisable than the classic table layout. | Documented · Source attached | — | Layout Context | A Vernacular Web: Frames |
| kcc:layout-2 | Professional web designs were produced in Photoshop and later adapted for the browser. | Documented · Source attached | — | Layout Context | A Vernacular Web: Free Collections of Web Elements |
| kcc:typography-1 | Susan Kare's first Macintosh letterforms were limited to vertical, horizontal or 45-degree lines, with nine-pixel capitals. | Documented · Source attached | — | Typography Context | How Susan Kare Designed User-Friendly Icons for the First Macintosh |
| kcc:typography-2 | Web source: HTML left rendering, including type, to the browser. | Documented · Source attached | — | Typography Context | A Vernacular Web: MIDI |
| kcc:typography-3 | Screen-specific TrueType faces (Verdana) were made for on-screen display. | Seen in the work | — | Typography Context | Verdana font family |
| kcc:imagery-1 | Desktop icons were monochrome bitmaps drawn on a 32 x 32 grid: trash can, disk, dog-eared document. | Documented · Source attached | — | Imagery Context | How Susan Kare Designed User-Friendly Icons for the First Macintosh |
| kcc:imagery-2 | The GIF format supports animation only in a limited way. | Documented · Source attached | — | Imagery Context | Graphics Interchange Format, Version 89a |
| kcc:imagery-3 | Free collections of web graphics (buttons, bullets, dividers, animations, 'Welcome' headers) were the vernacular web's image stock. | Documented · Source attached | — | Imagery Context | A Vernacular Web: Free Collections of Web Elements |
| kcc:imagery-4 | The contemporary revival is described through the same flashy, neon, blinking, clip-art imagery. | Documented · Source attached | — | Imagery Context | NeoCities Is Recreating the Garish, Web 1.0 Creativity of Geocities |
| kcc:interface-1 | Browser chrome of the period included icon buttons (back, forward, home) and bookmarks. Mosaic was the first published browser to show pictures inline with text. | Documented · Source attached | — | Interface Context | NCSA Mosaic |
| kcc:interface-2 | Amateur pages duplicated browser controls as their own back/forward buttons. | Documented · Source attached | — | Interface Context | A Vernacular Web: Free Collections of Web Elements |
| kcc:interface-3 | The early web's own interface furniture included 'Under Construction' signs, which became a common joke by around 1997. | Documented · Source attached | — | Interface Context | A Vernacular Web: Under Construction |
| kcc:surface-1 | Starry-night backgrounds (black, dark blue or purple, tiled with light static or blinking particles) were a vernacular-web surface; paper, glass, water and wood themes came later. | Documented · Source attached | — | Surface Context | A Vernacular Web: The Starry Night Background A Vernacular Web: Free Collections of Web Elements |
| kcc:surface-2 | An archived GeoCities homepage offers background images for reuse and previews them by number. | Seen in the work | — | Surface Context | Patriotic Graphics (GeoCities personal homepage, Heartland/Plains/4601) |
| kcc:motif-1 | The vernacular web had a shared ornament stock: rainbow dividers, the 'New!' sign, bullets, 'Under Construction' signs. | Documented · Source attached | — | Motif Context | A Vernacular Web: Free Collections of Web Elements A Vernacular Web: Under Construction |
| kcc:motif-2 | Lialina predicted that frames and construction signs would return as retro, stripped of their meaning and contexts. | Documented · Source attached | — | Motif Context | A Vernacular Web. The Indigenous and the Barbarians |
| kcc:technique-1 | Period constraints shaped the look: a starry background could be two colours and about half a kilobyte, MIDI was used because bandwidth was precious, and pages were built in hope of faster connections. | Documented · Source attached | — | Technique Context | A Vernacular Web: The Starry Night Background A Vernacular Web: MIDI A Vernacular Web. The Indigenous and the Barbarians |
| kcc:technique-2 | The amateur web preferred expression over structure. | Documented · Source attached | — | Technique Context | A Vernacular Web: Free Collections of Web Elements |
| kcc:technique-3 | The contemporary revival platform (Neocities) hosts static HTML. | Seen in the work | — | Technique Context | Making the Web Fun Again |
| kcc:hierarchy-1 | In the source language, expression was preferred over structure. | Documented · Source attached | — | Hierarchy Context | A Vernacular Web: Free Collections of Web Elements |
| kcc:density-1 | The early web is characterised as 'bright, rich, personal, slow and under construction'. | Documented · Source attached | — | Density Context | A Vernacular Web. The Indigenous and the Barbarians |
| kcc:w2-form-1 | Know Your Meme describes the aesthetic as using simplistic 3D elements and objects similar to early 3D video-game assets, alongside browser windows and simple colourful graphics. | Documented · Source attached | — | Form Context | Webcore / Internetcore |
| kcc:w2-interface-1 | Windows 95's interface inherited a desktop, a tray, context menus and a three-dimensional look and feel. | Documented · Source attached | — | Interface Context | The Windows 95 User Interface: A Case Study in Usability Engineering (CHI 96 design briefing) |
| kcc:w2-interface-2 | The Windows 95 taskbar carried a Start button, program entries and a clock, stayed on top of other windows, and gave every task its own entry. | Documented · Source attached | — | Interface Context | The Windows 95 User Interface: A Case Study in Usability Engineering (CHI 96 design briefing) |
| kcc:w2-interface-3 | System-provided Open and Save As dialogs were part of the Windows 95 furniture. | Documented · Source attached | — | Interface Context | The Windows 95 User Interface: A Case Study in Usability Engineering (CHI 96 design briefing) |
| kcc:w2-interface-4 | Early Netscape browser chrome had a title bar showing the page title, a location (URL) field, an animating status indicator and a progress bar. | Seen in the work | — | Interface Context | Netscape Handbook: Graphical Elements |
| kcc:w2-interface-5 | Links in the Netscape content area were marked by colour and/or underlining. | Seen in the work | — | Interface Context | Netscape Handbook: Graphical Elements |
| kcc:w2-motion-1 | Early Netscape signalled a transfer with an animating status indicator (the Mosaic Communications logo) and a progress bar that animated to show the progress of the current operation. | Seen in the work | — | Motion Context | Netscape Handbook: Graphical Elements |
| kcc:w2-motion-2 | The optional Netscape Looping Application Extension, the most commonly used GIF application extension, sets whether an animated GIF loops forever or a set number of times. | Documented · Source attached | — | Motion Context | Royal Frazier's Animated GIF Tech Sheet Long Live the Animated GIF: A Study on the Curation, Acquisition, and Preservation of Animated GIFs |
| kcc:w2-motion-3 | NN/g's original list of web-design mistakes advised: never include page elements that move incessantly. | Documented · Source attached | — | Motion Context | Original Top 10 Mistakes in Web Design |
| kcc:w2-motion-4 | The 2020s revival is described as featuring clunky animations. | Documented · Source attached | — | Motion Recognition test | Why are we all so obsessed with early web nostalgia? Webcore / Internetcore |
| kcc:w2-color-1 | The 216-colour browser-safe palette existed because in 1996 most users had 8-bit (256-colour) video. | Seen in the work | — | Color Context | The browser-safe web palette (lynda.com hex page, captured 2005-06-20) |
| kcc:w2-color-2 | By its publicist's own account the browser-safe palette is heavy on saturated colours and light on muted or tinted ones. | Seen in the work | — | Color Context | The browser-safe web palette (lynda.com hex page, captured 2005-06-20) |
| kcc:w2-color-3 | A GIF palette holds at most 256 colours. | Documented · Source attached | — | Color Context | Long Live the Animated GIF: A Study on the Curation, Acquisition, and Preservation of Animated GIFs |
| kcc:w2-imagery-1 | Two archived GeoCities Heartland homepages (captured 2001) carry visitor counters and guestbook links; one also lists web rings, awards the page has won, and membership of the Internet Link Exchange. | Documented · Source attached | — | Imagery Context | Personal family homepage, GeoCities Heartland/1512 (Wayback capture 2001-04-13) Personal genealogy homepage, GeoCities Heartland/1134 (Wayback capture 2001-04-04) |
| kcc:w2-imagery-2 | Cameron's World is a web collage of images and text from GeoCities pages made 1994-2009; Dazed cites it as drawing on GeoCities archives. | Documented · Source attached | — | Imagery Recognition test | Cameron's world · Excavating lost cities Cameron's World Why are we all so obsessed with early web nostalgia? |
| kcc:w2-imagery-3 | Artist Maria Vorobjova's Digital Folklore Tapestries are made from GeoCities GIFs. | Documented · Source attached | — | Imagery Recognition test | Why are we all so obsessed with early web nostalgia? |
| kcc:w2-imagery-4 | Revival accounts name harsh, loud website design, clunky animation and pixel art as the look being revived. | Documented · Source attached | — | Imagery Recognition test | Why are we all so obsessed with early web nostalgia? |
| kcc:definition | Internetcore (also Webcore) is a name, attested on the fan-edited Aesthetics Wiki, for a late-2010s–2020s internet aesthetic that uses the visual and audio language of the early internet (c. 1995–2005) to evoke nostalgia. Treating it as a design practice that deliberately quotes Web 1.0, browser and desktop conventions is Aesthetary's reading. | Documented · Source attached | — | — Definition | Aesthetics Wiki: Webcore (current wikitext) Aesthetics Wiki, first revision of the page created as 'Webcore' (now 'Old Web'), revid 146 |
| kcc:answers-D-homepage | Two archived GeoCities Heartland homepages (Wayback captures, April 2001) show visitor counters and guestbook links; one also has a web-ring list, an awards list and Internet Link Exchange membership. | Documented · Source attached | — | — Context | Personal family homepage, GeoCities Heartland/1512 (Wayback capture 2001-04-13) Personal genealogy homepage, GeoCities Heartland/1134 (Wayback capture 2001-04-04) |
| kcc:answers-D-desktop | Sullivan's CHI 96 case study documents Windows 95's desktop, tray, context menus, three-dimensional look and feel, taskbar with Start button and clock, and the Open/Save As dialogs. | Documented · Source attached | — | — Context | The Windows 95 User Interface: A Case Study in Usability Engineering (CHI 96 design briefing) |
| kcc:answers-D-browser | The Netscape Handbook documents the title bar, location (URL) field, animating status indicator (the Mosaic Communications logo), progress bar, and colour/underline link marking. | Seen in the work | — | — Context | Netscape Handbook: Graphical Elements |
| kcc:answers-D-graphics | Partly. GIF palettes were capped at 256 colours, the optional Netscape Looping Extension set whether GIFs looped, and the browser-safe palette limited choices to 216 colours. No quote here documents crude 3D or compression artefacts. | Documented · Source attached | — | — Context | Long Live the Animated GIF: A Study on the Curation, Acquisition, and Preservation of Animated GIFs Royal Frazier's Animated GIF Tech Sheet The browser-safe web palette (lynda.com hex page, captured 2005-06-20) |
| kcc:answers-D-revival | Dazed frames the revival as pandemic escapism, and reports that for artist Maria Vorobjova minimalism is tied to corporations that took over the net, so maximalist, lo-res Web 1 subverts it. That supports 'resistance to homogeneous UI' as a reading voiced by one practitioner. | Documented · Source attached | — | — Context | Why are we all so obsessed with early web nostalgia? |
| kcc:answers-D-work | Partly. Dazed names Cameron's World (a web collage of images and text from GeoCities pages made 1994-2009) and Vorobjova's Digital Folklore Tapestries (woven from GeoCities GIFs), both drawing on GeoCities. No quote here names a work labelled Webcore/Internetcore. | Documented · Source attached | — | — Context | Webcore / Internetcore Why are we all so obsessed with early web nostalgia? Cameron's world · Excavating lost cities |
| kcc:answers-D-constraints | Period constraints are documented: the browser-safe chart was published in 1996 when most users had 8-bit video; 10 seconds was the stated maximum response time; GIF palettes capped at 256 colours; frames were judged confusing because they break the web's page model. | Documented · Source attached | — | — Context | The browser-safe web palette (lynda.com hex page, captured 2005-06-20) Original Top 10 Mistakes in Web Design Long Live the Animated GIF: A Study on the Curation, Acquisition, and Preservation of Animated GIFs |
| kcc:w2-boundary-1 | Not Web 1.0 / Old Web (the period source language): Period documents (S3-S9) show the source language as a working medium shaped by real limits; Dazed (S1) and Know Your Meme (S2) describe Webcore/Internetcore as a 2020s revival that quotes it. The line between the two is date and intent: the revival is retrospective. Treating that as the boundary test is Aesthetary's reading. | Documented · Source attached | — | — Boundary | Webcore / Internetcore Why are we all so obsessed with early web nostalgia? Original Top 10 Mistakes in Web Design |
| kcc:w2-boundary-2 | vs Vaporwave / Weirdcore: Know Your Meme gives public recognition in 2020 as the aesthetic's only dated marker and records 'Internetcore', 'Webcore' and 'ENAcore' as its names. No source here states a visual test that separates it from Vaporwave or Weirdcore. | Documented · Source attached | — | — Boundary | Webcore / Internetcore |
| idr:boundary-ena | Not ENA-era Webcore: on the fan wiki that defines the name, Webcore (also Internetcore) now names a surrealist deconstruction that places old-web motifs in abstract, dreamlike voids, popularised by the animated series ENA (2020). This record is the design practice of quoting early-web and desktop interface; the ENA sense is outside it. | Documented · Source attached | — | — Boundary | Aesthetics Wiki: Webcore (current wikitext) |
What the research refused to canonicalise
| Claim | Verdict | Kind of claim |
|---|---|---|
| Internetcore requires a pixel font. | No. Typography must participate in the reference; no face is required. | Our reading |
| Internetcore has a canonical palette. | No. Colour inherits from the source language being quoted. | Our reading |
| Rounded corners are forbidden. | No. They become suspicious once the interface reads as contemporary SaaS. | Our reading |
| Internetcore is old web design. | No. Web 1.0 is the source; Internetcore is the later quotation. | Our reading |
Open questions
| Question | Status | What would settle it |
|---|---|---|
| Where the terms Internetcore and Webcore were first used | Open | the name, the alias, and the claim that this is a distinct aesthetic claims: definition |
| Grid, column count and spacing values. None are on the record. | Open | — |
| Specific typefaces, sizes and a type scale. | Open | — |
| Does Internetcore have a three-dimensional organisation? | Open | Looked for design-press, museum and scholarly treatments of Internetcore/Webcore that describe spatial or 3D organisation (Dazed, Know Your Meme, Wikipedia's list of internet aesthetics, Cameron's World and its museum listing). None describe a 3D organisation; the only 3D mentioned is depicted objects. Whether depicted early-3D assets belong under Imagery rather than Form is a classification call the evidence does not make. |
| D-work: contemporary design work (not animation) described as Internetcore | Open | The only work named under the term is ENA (2020), and only by the fan wiki (I15). No design-press or scholarly source using the term 'Internetcore' was found. |
| D-term: first use outside the Aesthetics Wiki | Open | Searches found the terms only on fan wikis, Neocities tags and SEO pages. The wiki revision dates (2019 Webcore, 2022 Internetcore) are the earliest dated uses found, not proven first uses. |
| D-revival counter-reading | Open | Lialina (2005) documents the retro turn, but Neocities' founder rejects nostalgia as the purpose (I13), and Vice frames it through 90s nostalgia (I12). Whether the revival is aesthetic quotation or platform politics is contested. |
| An archived personal homepage | Resolved | Answered: Two archived GeoCities Heartland homepages (Wayback captures, April 2001) show visitor counters and guestbook links; one also has a web-ring list, an awards list and Internet Link Exchange membership. claims: S-homepage, intent, evidence-interpretation |
| A desktop interface, captured | Resolved | Answered: Sullivan's CHI 96 case study documents Windows 95's desktop, tray, context menus, three-dimensional look and feel, taskbar with Start button and clock, and the Open/Save As dialogs. claims: S-desktop, UI-controls |
| Browser chrome of the period | Resolved | Answered: The Netscape Handbook documents the title bar, location (URL) field, animating status indicator (the Mosaic Communications logo), progress bar, and colour/underline link marking. claims: S-browser, A1 |
| Primitive digital graphics | Resolved | Answered: Partly. GIF palettes were capped at 256 colours, the optional Netscape Looping Extension set whether GIFs looped, and the browser-safe palette limited choices to 216 colours. No quote here documents crude 3D or compression artefacts. claims: S-graphics, I-types |
| Accounts of the contemporary revival | Resolved | Answered: Dazed frames the revival as pandemic escapism, and reports that for artist Maria Vorobjova minimalism is tied to corporations that took over the net, so maximalist, lo-res Web 1 subverts it. That supports 'resistance to homogeneous UI' as a reading voiced by one practitioner. claims: H5, retrospective |
| Contemporary work described as Internetcore | Resolved | Answered: Partly. Dazed names Cameron's World (a web collage of images and text from GeoCities pages made 1994-2009) and Vorobjova's Digital Folklore Tapestries (woven from GeoCities GIFs), both drawing on GeoCities. No quote here names a work labelled Webcore/Internetcore. claims: diagnostic, evidence-interpretation, coherence |
| Documentation of period technical constraints | Resolved | Answered: Period constraints are documented: the browser-safe chart was published in 1996 when most users had 8-bit video; 10 seconds was the stated maximum response time; GIF palettes capped at 256 colours; frames were judged confusing because they break the web's page model. claims: evidence-interpretation |
Sources
Visuals
Every visual on the page is an image slot with an evidence class. Only historical evidence and sourced contemporary evidence may stand as evidence for a claim; everything Aesthetary made may illustrate a claim, never evidence it.
| Slot | Evidence class | May be evidence | Illustrates |
|---|---|---|---|
| hero-morph | Aesthetary specimen | Never | intent, evidence-interpretation |
| guestbook-then | Aesthetary specimen | Never | intent |
| guestbook-now | Aesthetary specimen | Never | intent |
| source-windows | Aesthetary specimen | Never | S-homepage, S-desktop, S-browser, S-graphics |
| anatomy | Aesthetary diagram | Never | A1, A2, A3, A4, A5, A6 |
| timeline | Aesthetary diagram | Never | retrospective |
| counterexamples | Aesthetary specimen | Never | coherence |
| composition-wires | Aesthetary diagram | Never | L-metaphors |
| type-specimen | Aesthetary specimen | Never | T-families, T-costume |
| palette-preview | Aesthetary translation | Never | palette-source |
| shape-preview | Aesthetary translation | Never | radius |
| image-types | Aesthetary specimen | Never | lofi-reason, I-types |
| component-lab | Aesthetary translation | Never | UI-controls, UI-states |
| motion-demos | Aesthetary specimen | Never | M-vocab, M-reduced |
| challenge | Aesthetary specimen | Never | coherence |
| pixel-icons | Decorative | Never | — |