Blog

  • Novell NetWare

    Architecture, Administration, Operations, and Migration

    NetWare 3.12 through 6.5 SP8  |  Bindery, NDS/eDirectory, TFS, NSS, IPX, and native IP

    Version 1.0  |  8 August 2026

    For legacy operations, recovery, technical archaeology, and controlled migration

    Contents

    Select an entry in Word or a compatible viewer to jump to that section. Major sections begin on a new page for field use.

    How to use this reference

    Scope and conventions

    Support and security status

    Version families at a glance

    Compatibility questions to ask first

    Architecture and operating model

    The NetWare mental model

    Bindery versus NDS and eDirectory

    Core services stack

    Boot, configuration, and runtime

    Boot sequence

    NCF configuration files

    Safe boot and recovery switches

    NLMs and protected address spaces

    Networking and service discovery

    IPX and SPX environments

    Native IP and SLP environments

    Core ports and flows

    Client-to-file-service flow

    NDS and eDirectory administration

    Tree structure and naming

    Partitions, replicas, and replica rings

    Bindery emulation

    Time synchronization and directory health

    Directory administration tools

    Rights and security model

    File system trustee rights

    eDirectory object and property rights

    Effective rights and inherited rights filters

    Practical rights patterns

    File and directory attributes

    Storage, volumes, and file systems

    Traditional file system versus NSS

    NSS storage hierarchy

    Namespaces and path compatibility

    Salvage, purge, quotas, and capacity

    Repair boundaries

    Clients, drive mappings, and login scripts

    Client families

    Path syntax and mappings

    Login script execution order

    Login script example

    Administration quick reference

    Primary administration tools

    Console command quick reference

    Workstation utility quick reference

    Core NLM quick reference

    Illustrative NCF skeletons

    Operations runbook

    Daily, weekly, and monthly checks

    Controlled maintenance shutdown

    Change preparation checklist

    Troubleshooting playbooks

    Server will not start or SYS will not mount

    Clients cannot find a server

    Authentication or login script failure

    Access denied or files are invisible

    Slow response or high utilization

    Volume or pool is full

    Abend or repeated restart

    eDirectory synchronization errors

    Backup and disaster recovery

    What a usable backup must preserve

    Recovery rehearsal

    Printing and ancillary services

    Printing generations

    Other common services

    Containment, preservation, and migration

    Minimum containment pattern

    Migration sequence

    Virtualization and historical preservation

    Appendix A – Common paths and files

    Appendix B – Glossary

    Appendix C – Official source set

    How to use this reference   Back to contents

    This is a practical reference for engineers who must understand, recover, operate, or retire a Novell NetWare environment. It is not a replacement for the manual matching the exact server version, support pack, hardware driver set, eDirectory build, and installed applications.

    WORKING ASSUMPTION: The operational detail is centered on NetWare 4.x through 6.5, while NetWare 3.12 and Bindery behavior are called out where they differ. Commands marked as examples must be validated on the target server before use.

    Scope and conventions   Back to contents

    1. Server-console commands appear in uppercase for readability; NetWare commands are generally not case-sensitive.
    2. A path such as SYS:SYSTEM identifies a volume and directory. A path such as SERVER/SYS:PUBLIC also identifies the server.
    3. NDS refers to Novell Directory Services; later documentation uses eDirectory. In this guide, NDS/eDirectory means the directory service family.
    4. TFS means the NetWare Traditional File System. NSS means Novell Storage Services.
    5. Source markers such as [S2] refer to the official source set in Appendix C.

    Support and security status   Back to contents

    NetWare 6.5 SP8 is the terminal NetWare release line. It entered extended support in 2010, and the vendor’s later Premium Lifeline offering ended on 31 December 2016. It must therefore be treated as unsupported legacy infrastructure in 2026. [S1, S13]

    SECURITY BOUNDARY: Do not expose NCP, SLP, IPX routing, Telnet, RConsoleJ, legacy web administration, LDAP, or old TLS endpoints directly to the Internet or to an untrusted enterprise segment. Place the server behind an allow-list firewall on an isolated VLAN and administer it through a controlled jump host or modern encrypted tunnel.

    • Use unique legacy credentials; do not reuse current privileged passwords.
    • Disable services and protocols that are not required, particularly Telnet, IPX, anonymous LDAP, and legacy web components.
    • Keep ALLOW UNENCRYPTED PASSWORDS set to OFF unless a documented, temporary compatibility exception exists. [S2]
    • Assume that old cryptographic implementations and browser-based interfaces do not meet modern security baselines.
    • Capture configuration and recovery media before every change because replacement drivers, patches, and vendor support are scarce.

    Version families at a glance   Back to contents

    Version family summary

    FamilyDirectory modelNetwork emphasisOperational significance
    2.xPer-server BinderyIPX/SPXDedicated 286-era file server; highly version- and hardware-specific.
    3.x / 3.12Per-server BinderyIPX/SPX with SAP/RIP32-bit 386 line; NLM model; mature departmental file and print platform.
    4.x / intraNetWareNDS tree plus Bindery emulationIPX/SPX; IP add-onsIntroduced global directory, partitions, replicas, and directory-based administration.
    5.0 / 5.1NDSNative IP plus optional IPXNCP became transport-independent; SLP and NSS became central; multiprocessor and memory model advanced. [S14]
    6.0eDirectoryIP preferred; IPX optionalExpanded web access, iPrint/iFolder era services, and user-oriented licensing.
    6.5 / SP8eDirectory 8.7.3 or 8.8.xIP preferred; IPX retainedFinal mature NetWare line. New SP8 installs used eDirectory 8.8.4; updated systems could retain 8.7.3. [S1]
    OES / Enterprise ServereDirectory on LinuxIPSuccessor platform providing NCP, NSS, trustee semantics, CIFS, iPrint, and migration paths without the NetWare kernel. [S12]

    Compatibility questions to ask first   Back to contents

    1. What exact NetWare version, support pack, eDirectory version, JVM, and application build are installed?
    2. Is the server Bindery-only, NDS/eDirectory-native, or serving legacy clients through Bindery emulation?
    3. Are clients using IPX, native IP, or both? Which Ethernet frame types and SLP scopes are in use?
    4. Are volumes Traditional or NSS? Which namespaces, trustee assignments, quotas, compression, encryption, and salvage policies exist?
    5. Does the server hold directory partitions or replicas, and is it a Master replica, time source, SLP Directory Agent, Organizational CA host, licensing host, or cluster node?
    6. Which third-party NLMs, backup agents, database engines, and hardware-specific .HAM, .CDM, .LAN, and .PSM drivers are required?
    7. Are licenses, installation media, overlay media, support packs, driver disks, and keys preserved and legally usable?

    Architecture and operating model   Back to contents

    The NetWare mental model   Back to contents

    NetWare is a network services operating system, not a general-purpose desktop Unix or Windows server. The kernel is optimized around file, print, directory, protocol, and application services. Administrators interact with a server console and loadable modules; users interact through NCP clients, mappings, login scripts, and directory objects.

    Logical layers

    LayerExamplesRole
    ClientsDOS requester, VLM, Client32, Novell Client, NetStorageAuthenticate, discover services, map paths, consume file/print services.
    DirectoryBindery or NDS/eDirectoryStores identities, groups, servers, volumes, policies, schema, and service objects.
    Application/file serviceNCP, queue print, NDPS/iPrint, GroupWise, BtrievePresents network resources and application services.
    Discovery and transportSAP/RIP over IPX; SLP over IP; TCP/UDPLocates services and carries NCP or application traffic.
    File systemTraditional volumes or NSS pools and volumesStores data, trustees, attributes, quotas, namespaces, and salvage metadata.
    RuntimeSERVER.EXE, NLMs, protected address spacesExecutes kernel services, drivers, protocol stacks, and server applications.
    Hardware interfacePSM, HAM, CDM, LAN drivers, NWPAConnects processors, storage, and network adapters to the runtime.

    KEY DISTINCTION: An eDirectory Volume object represents a volume in the directory, but file access is governed by trustee metadata stored in the file system. Directory rights and file-system rights are related administration domains, not interchangeable ACLs. [S8]

    Bindery versus NDS and eDirectory   Back to contents

    Directory model comparison

    CharacteristicBinderyNDS/eDirectory
    ScopeOne database per serverDistributed tree spanning servers and sites
    NamingFlat object names on a selected serverHierarchical distinguished names in containers
    AdministrationRepeat users/groups on each serverCreate identities and policies once in the tree
    ResilienceServer-local backup and recoveryPartitions and replicas provide distributed availability
    Legacy supportNative to 2.x/3.x4.x+ can expose selected containers as a Bindery context
    Authentication targetServerTree and context, with a server used to reach a replica

    Core services stack   Back to contents

    1. NCP provides file-service semantics, connection management, locking, trustee enforcement, and related client services.
    2. NDS/eDirectory provides identities, objects, schema, authentication, partitions, and replication.
    3. NSS provides a journaling file system, storage pools, volumes, trustee metadata, salvage, quotas, compression, and optional encryption.
    4. IPX/SPX with SAP/RIP supplies legacy transport and discovery; TCP/IP with SLP supplies the later native-IP equivalent.
    5. NLMs extend the kernel with drivers, protocol stacks, management tools, backup agents, and server applications.

    Boot, configuration, and runtime   Back to contents

    Boot sequence   Back to contents

    1. The machine firmware starts the boot device and the small DOS boot environment used by classic NetWare installations.
    2. AUTOEXEC.BAT normally changes to C:\NWSERVER and invokes SERVER.EXE.
    3. SERVER.EXE reads STARTUP.NCF from the boot directory, applies pre-mount SET parameters, and loads platform and storage drivers.
    4. The server discovers storage and mounts SYS. If SYS cannot mount, SYS:SYSTEM modules and AUTOEXEC.NCF are unavailable.
    5. SYS:SYSTEM\AUTOEXEC.NCF executes, setting the server identity and loading LAN drivers, protocols, directory services, logging, and installed applications.
    6. Additional service-specific NCF files are called in their configured order. Users and clients can then discover and connect to the server.

    RECOVERY PRINCIPLE: Separate pre-SYS failures from post-SYS failures. STARTUP.NCF, platform support, and storage drivers dominate the first class. AUTOEXEC.NCF, network bindings, directory services, and application NLMs dominate the second.

    NCF configuration files   Back to contents

    Important NCF files

    FileNormal locationPurpose
    STARTUP.NCFC:\NWSERVERPre-SYS parameters plus platform and storage driver load order.
    AUTOEXEC.NCFSYS:SYSTEMServer identity, network drivers/bindings, services, and application start order.
    SHUTDOWN.NCFSYS:SYSTEMOptional orderly unload or stop commands run by DOWN or restart. [S2]
    SECURE.NCFConfigured locationOptional commands executed through the secure-start mechanism.
    Application .NCFUsually SYS:SYSTEM or application pathStarts or stops a product-specific set of NLMs.
    • Use EDIT or NWCONFIG to change NCF files, and retain a dated known-good copy before editing.
    • Place CONLOG near the beginning of AUTOEXEC.NCF if early console messages are needed; the default log is SYS:ETC\CONSOLE.LOG. [S2]
    • Only persist a SET parameter after confirming whether it belongs in STARTUP.NCF or AUTOEXEC.NCF. The SET display identifies valid locations. [S2]
    • Do not reorder storage, directory, or application modules without documenting dependencies.

    Safe boot and recovery switches   Back to contents

    SERVER and restart switches

    InvocationEffectUse
    SERVER -NSSkips STARTUP.NCFDiagnose a bad pre-mount parameter or driver line; storage may need loading manually.
    SERVER -NASkips AUTOEXEC.NCFMount SYS but prevent post-mount services and applications from starting.
    SERVER -S filename.NCFUses an alternate startup fileBoot a controlled known-good driver set. [S1, S2]
    RESTART SERVER -NSRestarts without STARTUP.NCFRepeat controlled pre-mount diagnosis.
    RESTART SERVER -NARestarts without AUTOEXEC.NCFRepeat controlled post-mount diagnosis.

    BEFORE REPAIR: Photograph or capture the console, preserve BOOT$LOG.ERR, CONSOLE.LOG, ABEND.LOG, STARTUP.NCF, AUTOEXEC.NCF, driver versions, and disk layout. Do not begin with VREPAIR, REBUILD, or DSREPAIR repair operations merely because the server failed to boot.

    NLMs and protected address spaces   Back to contents

    LOAD links an NLM or driver into the operating system; UNLOAD releases it and returns resources. Many server utilities can be loaded when needed, while LAN, storage, directory, and protocol modules form persistent dependencies. MODULES lists loaded modules and their address spaces. [S2, S3]

    1. Kernel address space provides maximum integration but a faulty NLM can abend the server.
    2. Protected address spaces run suitable applications in ring 3. PROTECT filename.NCF loads the modules from an NCF into a named protected space.
    3. PROTECTION lists protected spaces and can enable restart behavior. Drivers, SERVER.EXE, and some core modules cannot run protected.
    4. Unload dependent modules in reverse order. Never force-kill an address space until the data-integrity and vendor implications are understood.

    Networking and service discovery   Back to contents

    IPX and SPX environments   Back to contents

    Legacy IPX/SPX components

    ComponentFunctionDiagnostic focus
    IPXConnectionless routed network protocolNetwork numbers, frame types, bindings, routes
    SPXConnection-oriented transport over IPXSessions, sequence/retry behavior, compatible stack
    SAPAdvertises server and service namesDISPLAY SERVERS; hop count; filtering
    RIP/NLSPRoutes IPX networksDISPLAY NETWORKS; duplicate network numbers; convergence
    NCP/IPXCarries NetWare file and service requestsNCPIPX.NLM, connection state, packet loss
    ODIClient LAN driver and protocol interfaceLSL, NIC driver, frame type, IPXODI/VLM order

    Common Ethernet frame types include ETHERNET_802.2, ETHERNET_II, ETHERNET_802.3, and ETHERNET_SNAP. A client and server can share the physical Ethernet while remaining logically invisible if frame type or external network numbers do not match.

    IPX DISPLAY CAVEAT: DISPLAY SERVERS and DISPLAY NETWORKS show SAP/RIP information. They are not native-IP service-discovery commands; use SLP and TCP/IP tools for IP-only systems. [S2]

    Native IP and SLP environments   Back to contents

    NetWare 5 made NCP transport-independent and introduced a practical pure-IP deployment model. NCP over TCP/UDP uses native IP, while Service Location Protocol (SLP) replaces much of the name-to-address discovery previously supplied by SAP. [S3, S14]

    1. SLP User Agents issue queries, Server Agents register services, and Directory Agents provide a repository for registrations.
    2. Named SLP scopes partition discovery information. A server or client that queries the wrong scope can appear unable to find an otherwise healthy service.
    3. SLP uses TCP and UDP port 427. NCP over IP uses port 524. [S14]
    4. SYS:ETC\SLP.CFG can define static Directory Agents with DA IPV4 entries; DHCP options 78 and 79 can also supply agents and scopes.
    5. Directory replication can be affected when NDAP and Bindery service entries are absent from the scopes used by replica servers.

    Core ports and flows   Back to contents

    Common TCP/UDP ports – verify against the installed service configuration

    PortProtocol/serviceOperational note
    524 TCP/UDPNCP over IP / eDirectory service accessPrimary Novell client and server service path.
    427 TCP/UDPSLPService queries, registrations, and Directory Agent traffic.
    389 TCPLDAPDirectory access; clear-text unless protected externally or upgraded to TLS.
    636 TCPLDAPSDirectory access over legacy TLS; validate certificate and cipher compatibility.
    123 UDPNTPTime synchronization when XNTPD/NTP is selected.
    53 TCP/UDPDNSName service when DNS is hosted or consumed.
    80/443 TCPApache, iManager, NetStorage, iPrint or application web servicesActual bindings vary by installed pattern and reverse proxy design.
    8008/8009 TCPNovell Remote Manager, commonlyVersion/configuration dependent; never expose to an untrusted segment.
    413 TCPSMDR, commonlyStorage Management Services remote backup communication. [S3]
    2034-2036 TCPRConsoleJ agent/proxy variantsHistorical remote console ports; firewall-only and version dependent. [S2]

    FIREWALL RULE METHOD: Inventory listening modules and configured bindings on the actual server, capture a known-good traffic trace, then allow only required source/destination pairs. Do not use a generic ‘NetWare ports’ rule set as an exposure baseline.

    Client-to-file-service flow   Back to contents

    1. The client obtains a server or tree target from a preferred server, preferred tree, explicit name, SLP, SAP, DNS, or cached configuration.
    2. The client resolves the service to an IP or IPX address and opens an NCP connection.
    3. The user authenticates to the Bindery server or to NDS/eDirectory through a server holding or locating the required replica.
    4. Container, profile, and user login scripts execute and create drive/search mappings.
    5. NCP evaluates trustee rights, IRFs, security equivalence, file attributes, locks, quotas, and namespace rules for each operation.

    NDS and eDirectory administration   Back to contents

    Tree structure and naming   Back to contents

    Common eDirectory objects

    ObjectPurposeTypical relationship
    [Root]Top of one directory treeContains top-level organizations and holds the root partition.
    O / OrganizationTop-level administrative containerOften represents the enterprise.
    OU / Organizational UnitDelegation and policy containerOften represents geography, function, or service domain.
    UserIdentity and login propertiesMember of groups; may have home directory and login script.
    GroupSecurity equivalence and shared assignmentUsed for file trustees and application roles.
    ServerRepresents a serverAssociated with volumes, addresses, services, and directory replicas.
    VolumeDirectory representation of a volumePoints users and tools to file storage; data rights remain in the file system.
    ProfileReusable login scriptAssigned to users between container and user scripts.
    Alias / Directory MapAlternate object name or path abstractionReduces path coupling and supports user-friendly mappings.

    Typed name:     CN=PJONES.OU=ARCHITECTURE.O=ACME
    Typeless name:  PJONES.ARCHITECTURE.ACME
    Absolute name:  .PJONES.ARCHITECTURE.ACME
    Relative name:  PJONES   (when the current context is ARCHITECTURE.ACME)

    Dot notation is written from the leaf toward [Root]. LDAP notation normally reverses the order and separates components with commas, for example CN=PJONES,OU=ARCHITECTURE,O=ACME.

    Partitions, replicas, and replica rings   Back to contents

    • A partition is a contiguous subtree stored and replicated as a unit.
    • The Master replica coordinates partition operations. Read/Write replicas accept updates; Read-Only replicas serve reads; Subordinate Reference replicas preserve connectivity across partition boundaries.
    • All servers holding a replica of a partition form its replica ring. A healthy ring exchanges changes and agrees on partition and replica metadata.
    • Partitions improve scale and locality; replicas improve availability. Excessive partitioning or poorly placed replicas increase synchronization and WAN complexity.
    • The first servers in a new tree normally receive root-partition replicas; later placement should be planned around site availability and directory dependencies. [S7]

    MASTER IS NOT PRIMARY: Ordinary object writes can occur on writable replicas. The Master is special for partition and replica operations; it is not a single writable directory server in the Active Directory PDC sense.

    Bindery emulation   Back to contents

    NetWare 4.x and later can present selected NDS/eDirectory containers to Bindery-aware clients and applications. The BINDERY CONTEXT SET parameter identifies up to 16 containers, separated by semicolons, whose objects are exposed through Bindery services. [S2]

    SET BINDERY CONTEXT = OU=SALES.O=ACME;OU=ACCOUNTING.O=ACME

    1. The specified containers must be available on the server through local directory replicas or references.
    2. Bindery-aware applications see a flat view and can encounter duplicate short names across contexts.
    3. Changing the Bindery context is a compatibility change; test authentication, print, backup, and application dependencies.

    Time synchronization and directory health   Back to contents

    Directory operations depend on coherent timestamps. Official health procedures call for time checks, replica synchronization checks, schema checks, and review of obituaries and directory versions. A dynamic tree should be checked about weekly; a static tree about monthly, and every tree before a major directory operation. [S10]

    LOAD DSREPAIR
      Time Synchronization
      Report Synchronization Status

    SET DSTRACE=ON
    SET DSTRACE=NODEBUG
    SET DSTRACE=+S
    SET DSTRACE=*H
      Expected healthy indicator: All Processed = Yes
    SET DSTRACE=NODEBUG
    SET DSTRACE=OFF

    DO NOT REPAIR BY REFLEX: DSREPAIR is both a diagnostic and a repair tool. Start with time, version, replica, and synchronization reports. Preserve a supported directory backup and understand the replica ring before initiating destructive or topology-changing repair options.

    Directory administration tools   Back to contents

    Directory tool map

    ToolBest useCaution
    NWAdminClassic Windows NDS object administrationSnap-ins and behavior are version specific.
    ConsoleOneCross-platform objects, schema, rights, and product snap-insJava/runtime dependencies can be fragile.
    iManagerBrowser-based role and task administrationOld TLS and plug-ins require isolation and compatible browser/runtime.
    iMonitorDirectory health, partitions, replicas, agents, tracesDiagnostic visibility can expose sensitive directory data.
    DSREPAIRTime, replica, database, and synchronization diagnostics/repairUse health reports first; repairs can alter directory state.
    DSTRACELive directory process and synchronization traceFilters can be noisy; capture to file and disable when finished.

    Rights and security model   Back to contents

    File system trustee rights   Back to contents

    File and directory trustee rights

    CodeRightMeaning
    SSupervisorAll file-system rights; cannot be blocked by an IRF.
    RReadOpen and read files.
    WWriteModify file contents.
    CCreateCreate files/subdirectories; supports salvage semantics where applicable.
    EEraseDelete files and directories.
    MModifyRename items and change file or directory attributes.
    FFile ScanSee and search names in the file-system structure.
    AAccess ControlAdd/remove trustees and change trustee rights and IRFs.

    The workstation RIGHTS utility displays or changes assignments. ALL grants all rights except Supervisor. A plus adds rights, a minus removes rights, and a rights list without plus/minus replaces the assignment. [S2]

    RIGHTS SYS:DATA R W C E M F /NAME=.TEAM_ARCHITECTURE.ACME
    RIGHTS SYS:DATA /NAME=.PJONES.ARCHITECTURE.ACME /I
    RIGHTS SYS:DATA /T
    RIGHTS SYS:DATA REM /NAME=.OLDGROUP.ACME

    eDirectory object and property rights   Back to contents

    eDirectory rights

    ClassRightMeaning
    ObjectSupervisorAll rights to the object and its properties.
    ObjectBrowseSee the object; does not reveal its property values.
    ObjectCreateCreate objects beneath a container; includes Browse.
    ObjectDeleteDelete the target object.
    ObjectRenameChange the target object’s name.
    PropertySupervisorComplete control over the selected property.
    PropertyCompareTest a value without reading it.
    PropertyReadRead property values; includes Compare.
    PropertyWriteCreate, change, or delete property values.
    PropertyAdd SelfAdd/remove the trustee itself in object-valued properties such as group membership.

    SENSITIVE DELEGATION: Broad Read access to all User attributes can expose password-management attributes in some eDirectory configurations. Delegate only the object and property rights required for the task. [S8]

    Effective rights and inherited rights filters   Back to contents

    Effective rights are the rights available at the moment of access after NetWare/eDirectory combines explicit trustee assignments, group membership, security equivalence, inherited assignments, and the applicable IRFs. [S8]

    1. An IRF removes selected rights as they flow down a directory or file-system hierarchy.
    2. A lower explicit trustee assignment can add required rights back at the target level.
    3. File-system Supervisor cannot be filtered by a file-system IRF; assign it sparingly.
    4. An apparent rights failure can instead be a visibility failure: File Scan is required to see names, and Read is required to open content.
    5. Check the user’s direct assignment, group assignments, security equivalences, IRFs along the path, the target’s explicit assignment, and file attributes.

    Practical rights patterns   Back to contents

    Common assignment patterns

    Use caseSuggested trustee patternNotes
    Home directoryUser: R W C E M F; administrator group: SSet at each home root or through automated provisioning; protect parent visibility.
    Shared read-only dataReader group: R FRead alone is insufficient for useful browsing; File Scan exposes names.
    Shared working areaContributor group: R W C E M FExclude Access Control unless users must delegate rights.
    Drop boxPurpose-built rights and visibility designTest create, read-back, overwrite, rename, delete, and listing behavior separately.
    Delegated folder ownerR W C E M F AAccess Control permits trustee/IRF changes; does not confer Supervisor.
    Service accountDedicated group with minimum path-specific rightsAvoid security equivalence to Admin or broad container-level Supervisor.

    File and directory attributes   Back to contents

    Common attributes

    AttributeEffect / use
    Read OnlyPrevents file modification; older implementations may also imply rename/delete protection.
    ArchiveMarks a file as changed for archive-aware backup workflows.
    Hidden / SystemControls client visibility and marks operating-system content.
    ShareablePermits compatible shared access semantics.
    TransactionalEnables transaction tracking where supported.
    Purge ImmediateDeletes without retaining a salvageable copy.
    Rename InhibitPrevents renaming.
    Delete InhibitPrevents deletion.
    Copy InhibitRestricts copying where supported by the client/protocol path.

    Attribute support varies between Traditional and NSS volumes and between access protocols. A change is effective only when the underlying file system and NCP path can enforce it. [S6]

    Storage, volumes, and file systems   Back to contents

    Traditional file system versus NSS   Back to contents

    File-system comparison

    CharacteristicTraditional file systemNSS
    StructureNetWare partition containing one or more volumesDevices/partitions feed pools; pools contain logical volumes
    RecoveryVREPAIR on an unmounted volumeVERIFY/REBUILD and NSS-specific tools; VREPAIR is not used
    Mount behaviorDirectory/FAT structures can make large-volume recovery slowJournaling and modern metadata support faster activation
    Capacity modelFixed allocation within the NetWare partitionVolumes allocate pool space dynamically and can be overbooked
    NamespacesDOS plus added LONG/MAC/NFS namespacesMultiple namespaces integrated into NSS semantics
    Advanced featuresTrustees, salvage, compression on supported versionsTrustees, quotas, salvage, compression, snapshots/DFS options, encryption
    MigrationRequires metadata-aware copy and namespace planningDesigned for compatibility with OES NSS and NCP services

    NSS storage hierarchy   Back to contents

    1. Physical disks, SAN LUNs, RAID devices, virtual disks, or multipath devices are presented as storage devices.
    2. NSS partitions or segments allocate device space to one or more pools.
    3. A pool aggregates space and can span devices. Its failure domain therefore includes every device contributing segments.
    4. One or more NSS volumes allocate space from a pool only as needed. A volume belongs to one pool; a pool can contain multiple volumes.
    5. NCP, CIFS, AFP, NetStorage, and application services expose the volume through their configured identity and trustee model.

    NetWare 6.5 NSS supports dynamic volume growth within a pool and overbooking. The official guide describes volumes up to 8 TB and very large file counts, while individual devices presented to NetWare NSS are limited to 2 TB. Verify the exact build, device carving, and storage vendor limits before expansion. [S5]

    POOL FAILURE DOMAIN: Spanning a pool across devices increases capacity but also couples availability. Hardware RAID, NSS mirroring, SAN protection, multipathing, and backup are different controls; document which layer actually protects each segment.

    Namespaces and path compatibility   Back to contents

    A namespace records names and metadata for a client environment. Traditional volumes begin with DOS semantics and can add LONG for Windows/OS2, MAC for Macintosh, and NFS for Unix-style names. [S2]

    LOAD LONG.NAM
    ADD NAME SPACE LONG TO DATA

    REM Equivalent choices exist for MAC and NFS where the modules are installed.

    • Do not remove a namespace until every file name and metadata dependency has been assessed.
    • Migration tools may require the NFS namespace on a Traditional source volume to preserve names and metadata correctly.
    • Case, forbidden characters, alternate data, Macintosh metadata, and long-name collisions must be tested against the destination protocol.

    Salvage, purge, quotas, and capacity   Back to contents

    • Salvage retains deleted files until they are restored, purged, or reclaimed according to policy. It is not a backup because it shares the same volume and failure domain.
    • Purge permanently removes salvageable files. PURGE IMMEDIATE bypasses recovery for selected files/directories.
    • NSS can enable salvage per volume; NSS console commands include NSS /SALVAGE=volume and NSS /NOSALVAGE=volume. [S2, S5]
    • User, directory, and volume quotas control consumption. Always check the pool as well as the logical volume: an overbooked pool can exhaust physical space before volume quotas appear full.
    • Keep SYS for operating-system and extension content where practical; place user data and applications on separate pools/volumes. [S5]

    Repair boundaries   Back to contents

    Repair decision table

    TargetDiagnostic / repair familyBoundary
    Traditional volumeVOLUME/VOLUMES, MONITOR, VREPAIRDismount before VREPAIR; preserve logs and backup first.
    NSS volume/poolNSS /STATUS, NSSMU, VERIFY/REBUILD, iManager/NRMDo not use VREPAIR; confirm pool/device state before metadata repair.
    eDirectoryiMonitor, DSREPAIR, DSTRACEDirectory repair is separate from volume repair; start with health checks.
    Hardware/storage pathNWPA/driver tools, vendor array, mirror/RAID statusFile-system repair cannot correct a failing controller, path, or LUN.
    Application dataVendor consistency and recovery toolsA mounted volume does not prove a database or message store is consistent.

    Clients, drive mappings, and login scripts   Back to contents

    Client families   Back to contents

    Client generations

    ClientTypical environmentKey components / notes
    NETX requesterEarly DOS / BinderySmall conventional-memory requester; server-centric login.
    VLM clientDOS / NDSLSL + ODI LAN driver + IPXODI + VLM modules; NDS-aware.
    Client32Windows 3.x/9x32-bit client stack, NDS login, improved cache and transport support.
    Novell ClientWindows NT through supported later Windows releasesNCP, eDirectory authentication, SLP, mappings, trustee extensions.
    Novell Client for LinuxLinux workstationsNCP and eDirectory integration; some login-script commands differ.
    NetStorageBrowser/WebDAV-style accessInterprets selected MAP and conditional login-script commands.
    CIFS/AFP/NFSNative OS accessProtocol-specific identity mapping and metadata semantics; not identical to NCP.

    Path syntax and mappings   Back to contents

    Path examples

    FormExampleMeaning
    Current serverSYS:PUBLICPUBLIC directory on SYS of the current/default server.
    Server qualifiedNW65LAB/SYS:PUBLICPUBLIC on SYS of server NW65LAB.
    Object qualified.DATA.NW65LAB.SERVERS.ACME:PROJECTSDirectory under a Volume object identified from [Root].
    Drive mappingMAP G:=NW65LAB/DATA:PROJECTSMap G to the explicit server/volume path.
    Home mappingMAP H:=%HOME_DIRECTORYMap from the user’s eDirectory Home Directory property.
    Search driveMAP INS S1:=SYS:PUBLICInsert a program search mapping without replacing existing search drives.
    Fake rootMAP ROOT F:=SERVER/VOL:APPPresent APP as the apparent root for a legacy application.

    Login script execution order   Back to contents

    1. The container login script runs first and establishes defaults for users in that O or OU.
    2. The assigned Profile object’s login script runs next and adds role- or team-specific mappings.
    3. The User object’s login script runs last and can override earlier mappings.
    4. If the user has no user login script, the built-in default login script runs unless NO_DEFAULT was issued by a container or profile script. [S9]
    5. Prefer reusable container and profile scripts; reserve user scripts for true exceptions.
    6. Use IF MEMBER OF to drive group-based mappings, INCLUDE for shared text scripts, and MAP DISPLAY OFF/ON for clean output.
    7. The last conflicting MAP wins. Diagnose the full chain rather than only the user script.

    Login script example   Back to contents

    REM Container/Profile example – validate names and client behavior
    MAP DISPLAY OFF
    MAP ERRORS OFF
    MAP INS S1:=NW65LAB/SYS:PUBLIC
    MAP H:=%HOME_DIRECTORY

    IF MEMBER OF “.TEAM_ARCHITECTURE.ACME” THEN
      MAP G:=NW65LAB/DATA:ARCHITECTURE
    END

    IF MEMBER OF “.NETWARE_ADMINS.ACME” THEN
      MAP M:=NW65LAB/SYS:SYSTEM
    END

    MAP ERRORS ON
    MAP DISPLAY ON
    MAP

    TEST MATRIX: Test login scripts with each supported client family, transport, context, roaming site, and group combination. A script that works in the Windows Novell Client may be only partially implemented by the Linux client or NetStorage. [S9]

    Administration quick reference   Back to contents

    Primary administration tools   Back to contents

    Administration tool map

    ToolRuns atPrimary job
    System ConsoleServerCore commands, screen switching, NLM control, boot and emergency operation.
    MONITORServer consoleConnections, CPU, memory, service processes, storage, LAN statistics, SET parameters.
    NWCONFIGServer consoleDrivers, products, NCF editing, installation options, traditional volume tasks.
    INETCFG / TCPCONServer consoleProtocol configuration and live TCP/IP status/statistics.
    NSSMUServer consoleNSS devices, partitions, pools, volumes, RAID, and attributes.
    Novell Remote ManagerWeb browserHealth, console, modules, connections, volumes, parameters, logs, diagnostics. [S11]
    iManagerWeb browserRole-based eDirectory, NSS, files, rights, certificates, and service administration.
    ConsoleOne / NWAdminWorkstation or server GUIDirectory objects, schema, rights, login scripts, and product snap-ins.

    Console command quick reference   Back to contents

    Common server-console commands

    CommandPurposeNotes
    HELP [command] / HELP ALLShow console command helpPrefer local help because loaded modules register additional commands.
    VERSIONShow NetWare, support pack, license, and eDirectory versionsRecord before any change.
    CONFIGShow server, LAN, IPX, tree, and Bindery context informationUseful hardware/network baseline.
    TIMEShow server timeCompare with directory time sources.
    MODULES [prefix*]List loaded modules and address spacesUse before unload or abend analysis.
    SEARCHShow or modify NLM search pathsUnexpected paths can load the wrong module version.
    MEMORYShow installed/addressable memoryUse NRM for deeper attribution.
    DISPLAY PROCESSORSShow processor online/offline stateNetWare 5/6 multiprocessor environments.
    DISPLAY ENVIRONMENTShow search paths and SET parametersDISPLAY MODIFIED ENVIRONMENT shows deviations only.
    SETBrowse or change server parametersConfirm valid range and persistence file.
    MONITOROpen live system monitorConnections, resources, parameters, storage, LAN.
    LOAD / UNLOADLink or unlink an NLM or driverRespect dependencies and application shutdown procedure.
    PROTECT file.NCFLoad an NCF into a protected address spaceOnly for compatible modules.
    PROTECTIONList/configure protected spacesCan enable restart behavior.
    MOUNT volume / MOUNT ALLMount volumesUse NSS tools for NSS-specific activation issues.
    DISMOUNT volumeMake a volume unavailableClose files and stop dependent applications first.
    VOLUME / VOLUMESList mounted volumesSpelling varies by release/module registration.
    NSS /STATUS / NSS /HELPShow NSS state and helpNSS commands are version specific.
    NSSMUOpen NSS management utilityDestructive functions can erase device metadata.
    NWCONFIGOpen server configurationDriver/product/NCF and traditional storage tasks.
    INETCFG / TCPCONConfigure or monitor networkingSave before restart; distinguish configuration from live state.
    PING / TPINGTest IP reachabilityTPING syntax and implementation vary.
    DISPLAY SERVERSList SAP-advertised IPX servicesNot an IP/SLP discovery test.
    DISPLAY SLP …Show SLP agents, services, addresses, or typesExact subcommands depend on SLP.NLM build.
    DSREPAIRDirectory diagnostics and repairStart with time and sync reports.
    SET DSTRACE=…Control directory traceDisable filters/logging when complete.
    CONLOGCapture console messagesDefault SYS:ETC\CONSOLE.LOG; load early.
    DISABLE LOGIN / ENABLE LOGINControl new loginsExisting connections remain until cleared or logged out.
    SECURE CONSOLERestrict console operationsLoad required nonstandard-path modules first. [S2]
    DOWNOrderly shutdownFlushes caches, closes files, executes SHUTDOWN.NCF.
    RESTART SERVER [-NA|-NS]Orderly NetWare restartUse diagnostic switches deliberately.

    Workstation utility quick reference   Back to contents

    Common client/workstation utilities

    UtilityPurposeExample
    LOGINAuthenticate and execute login scriptsLOGIN TREE/USER or LOGIN SERVER/USER
    LOGOUTClose authenticated connectionsLOGOUT or client GUI equivalent
    MAPView/create/delete drive and search mappingsMAP G:=SERVER/VOL:PATH
    CXView/change eDirectory contextCX /T /A
    RIGHTSView/change file trustees, rights, IRF, and sourcesRIGHTS path /NAME=user /I
    FLAGView/change file or directory attributesSyntax varies; prefer client property page for safety
    SALVAGE / PURGERestore or permanently remove deleted filesUse client GUI or matching release utility
    CAPTURE / NPRINTLegacy queue-based print redirection/submitVersion and client dependent

    Core NLM quick reference   Back to contents

    Common modules – not exhaustive

    ModuleRoleOperational warning
    DS.NLMNDS/eDirectory engineDirectory-dependent services and authentication rely on it.
    NCP.NLM / CONNMGR.NLMCore NCP and connection servicesFoundation for client file service.
    NCPIP.NLMNCP over TCP/UDPUnloading removes IP NCP access. [S3]
    NCPIPX.NLMNCP over IPXLegacy transport; not intended for casual unload after activation.
    TCPIP.NLMTCP/IP stackLarge dependency tree; use INETCFG/TCPCON.
    IPXSPX.NLMIPX/SPX stackRequired by legacy IPX clients/services.
    SLP.NLM / SLPDA.NLMIP service discovery / Directory AgentScopes and directory replicas affect availability.
    NSS.NLMNovell Storage ServicesDo not unload with active NSS volumes or dependent services.
    NWPA.NLMStorage driver architectureHAM/CDM storage access depends on it. [S3]
    MONITOR.NLMSystem monitoringCan be loaded and unloaded as a utility.
    NWCONFIG.NLMServer configurationInstallation and driver operations can alter NCF files.
    DSREPAIR.NLMDirectory diagnostics/repairRepairs can change replicated state.
    CONLOG.NLMConsole loggingConfigure rotation; unlimited logs can consume SYS.
    PORTAL.NLM / HTTPSTK.NLMRemote Manager and HTTP stackLegacy web/TLS exposure requires containment.
    TIMESYNC.NLM / XNTPD.NLMTime synchronizationUse one planned time model; eDirectory depends on stable time.
    SMDR.NLM / TSAFS.NLM / SBCON.NLMStorage Management Services backupCoordinate application and directory-aware backup.
    SNMP.NLMMonitoring agentLegacy community-based SNMP is not suitable across untrusted networks.

    Illustrative NCF skeletons   Back to contents

    NOT PASTE-READY: Driver names, load order, bindings, addresses, and SET parameters must come from the target server’s known-good configuration and matching manuals. The skeletons show separation of concerns only.

    REM C:\NWSERVER\STARTUP.NCF – schematic only
    REM Pre-mount SET parameters validated for this exact release
    SET <pre-mount parameter> = <validated value>
    REM Platform, storage adapter, and device modules from known-good media
    LOAD <platform>.PSM
    LOAD <adapter>.HAM <validated parameters>
    LOAD <device>.CDM

    REM SYS:SYSTEM\AUTOEXEC.NCF – schematic only
    FILE SERVER NAME <SERVERNAME>
    LOAD CONLOG ARCHIVE=YES MAXIMUM=<validated-kilobytes>
    REM Load/bind LAN and protocols or invoke generated network configuration
    <known-good network configuration>
    REM Start directory, discovery, storage, management, and applications
    <service-specific NCF files>
    MOUNT ALL

    REM SYS:SYSTEM\SHUTDOWN.NCF – schematic only
    REM Stop application services in reverse dependency order
    <application stop commands>
    REM Flush/close product-specific engines before DOWN completes

    Operations runbook   Back to contents

    Daily, weekly, and monthly checks   Back to contents

    Operational cadence

    CadenceChecksEvidence to retain
    DailyServer up time; health summary; ABEND.LOG; SYS/pool free space; mirror/RAID/path state; backup completion; time state; critical service availabilityAlert record, console/health snapshot, backup result
    WeeklyDirectory sync for dynamic trees; CONSOLE.LOG and SYS$LOG.ERR review; NLM/application errors; packet buffers; LAN errors; salvage growth; sample restoreDSTRACE/DSREPAIR report, capacity trend, restore evidence
    MonthlyDirectory health for static trees; replica and partition inventory; DS versions; schema/obituary status; account review; recovery media and cold-image verificationSigned health report and configuration archive
    Before major changeFull directory health check; application-consistent backup; boot/config export; driver/media check; rollback rehearsal; maintenance communicationsChange record, hash/manifest, rollback decision point

    Controlled maintenance shutdown   Back to contents

    1. Confirm a current usable backup and record the current VERSION, up time, active modules, volume/pool status, mirror/RAID state, time status, and directory health.
    2. Notify users and application owners; quiesce or stop databases, message stores, print services, and backup jobs through their supported procedures.
    3. Issue DISABLE LOGIN. Review MONITOR connections and open files; have users close data and log out rather than clearing active sessions blindly.
    4. Dismount only the volumes required by the maintenance procedure. Confirm cluster or shared-storage ownership where applicable.
    5. Issue DOWN for an orderly shutdown. DOWN flushes cache, closes files, updates file-system structures, and runs SHUTDOWN.NCF if present. [S2]
    6. Wait for the completion message or return to DOS before powering off or rebooting hardware.
    7. After startup, validate volumes, directory synchronization, SLP/SAP discovery, applications, clients, logging, and backups before re-enabling normal access.

    Change preparation checklist   Back to contents

    • Exact server, support pack, eDirectory, NLM, driver, and hardware/virtual hardware versions recorded.
    • STARTUP.NCF, AUTOEXEC.NCF, SHUTDOWN.NCF, SYS:ETC configuration, driver set, and application NCF files copied and hashed.
    • Storage map records devices, partitions, pools, volumes, namespaces, quotas, trustee metadata, cluster resources, and free space.
    • Directory map records tree, partitions, replicas, Master roles, time sources, SLP scopes/DAs, CA host, licensing, and schema extensions.
    • Application-consistent backup and a directory-aware backup completed; representative restore tested.
    • Rollback is time-bounded, resourced, and tested; the point beyond which rollback is unsafe is explicit.
    • Management access remains available if clients, SLP, DNS, or the normal AUTOEXEC.NCF path fails.

    Troubleshooting playbooks   Back to contents

    Server will not start or SYS will not mount   Back to contents

    1. Capture the screen and preserve BOOT$LOG.ERR. Classify the failure as before STARTUP.NCF, during driver load, during storage discovery, during SYS mount, or after AUTOEXEC.NCF begins.
    2. Boot with SERVER -NA when SYS can mount but post-mount services fail. Use SERVER -NS or a known-good alternate startup file only when prepared to load required storage support manually.
    3. Compare STARTUP.NCF, platform support, HAM/CDM drivers, firmware, virtual hardware, and device presentation with the known-good baseline.
    4. Confirm the controller/LUN/device is present and stable before attempting file-system repair. A missing or changing device is not a metadata-repair problem.
    5. For a Traditional volume, use VREPAIR only while unmounted and after preserving evidence/backup. For NSS, use NSS status, NSSMU, and the appropriate VERIFY/REBUILD procedure; never VREPAIR an NSS volume.
    6. Once SYS mounts, start AUTOEXEC.NCF services in controlled groups to isolate the failing module or binding.

    Clients cannot find a server   Back to contents

    Discovery fault isolation

    CheckIP/SLP environmentIPX/SAP environment
    Basic reachabilityPING/TPING, routing, VLAN/firewall, DNSFrame type, external network number, router path
    Service discoverySLP scope, DA list, SYS:ETC\SLP.CFG, port 427DISPLAY SERVERS, SAP filters, hop count
    File serviceNCPIP.NLM, TCP/UDP 524, server object addressNCPIPX.NLM, IPX binding/socket
    Client settingsPreferred tree/server, SLP DA/scope, protocol orderPreferred server, frame type, network number
    Directory dependencyReplica reachability, NDAP service registrations, timeDirectory SAP service and route

    Authentication or login script failure   Back to contents

    1. Separate authentication failure from post-authentication login-script failure. Test a minimal login without application mappings where possible.
    2. Confirm user distinguished name, context, preferred tree/server, password status, account restrictions, and client date/time.
    3. Check server time and DSREPAIR Time Synchronization; then verify the required partition replica is reachable and synchronized.
    4. For legacy clients/applications, verify BINDERY CONTEXT and unique short names.
    5. Trace the container, profile, user, and default login scripts in order. Enable MAP errors and remove conditionals temporarily in a test account, not in production for every user.
    6. Verify that the user is a trustee of the Profile object and that mapped servers/volumes are reachable through the selected protocol. [S9]

    Access denied or files are invisible   Back to contents

    1. Confirm the exact path, server, volume, namespace, protocol, and user identity. Alias and Directory Map objects can conceal the real target.
    2. Use RIGHTS with /NAME and /I, or the client’s Current Effective Rights view, to identify direct, group, security-equivalent, and inherited rights.
    3. Inspect IRFs at every level from the relevant parent to the target. Confirm that Read and File Scan exist for visibility and content access.
    4. Inspect target file/directory attributes: Read Only, Hidden, Delete Inhibit, Rename Inhibit, Purge Immediate, and protocol-specific enforcement.
    5. Check user/directory/volume quotas, free pool space, open-file and record locks, ownership, and application-level permissions.
    6. Remember that rights on the eDirectory Volume object do not substitute for file-system trustee rights stored on the volume.

    Slow response or high utilization   Back to contents

    • Establish whether the delay is client-only, service-specific, server-wide, site-specific, or time-of-day dependent.
    • Use Novell Remote Manager or MONITOR for CPU, service processes, packet receive buffers, memory, connections, open files, LAN errors, and disk activity.
    • Check mirror/RAID state, controller errors, LUN latency, low SYS/pool space, salvage backlog, and concurrent backup/antivirus/application jobs.
    • Review SLP timeouts and DA availability for slow logins; review directory replica placement and time for slow authentication.
    • Record DISPLAY MODIFIED ENVIRONMENT. NetWare defaults were tuned as a balanced system; do not copy old tuning folklore without evidence. [S4]
    • If No ECB Available Count grows, investigate dropped packets, driver/TSM compatibility, and packet receive buffers; more buffers consume memory. [S4]

    Volume or pool is full   Back to contents

    1. Identify whether the constraint is a user quota, directory quota, logical volume quota, physical NSS pool, Traditional partition, SYS, or underlying storage device.
    2. Stop the process generating data before deleting evidence or expanding storage.
    3. Review salvageable files and purge only under an approved retention decision. Salvage is shared-capacity recovery, not free space.
    4. For NSS, check every volume in the pool and account for overbooking. Extend the pool only after validating device size, RAID/path protection, backups, and vendor limits.
    5. For SYS, remove or rotate logs and temporary/support-pack content only when ownership is known. Do not delete hidden directory or product files by pattern.
    6. After remediation, restore alert thresholds, logging rotation, quota controls, and capacity trend monitoring.

    Abend or repeated restart   Back to contents

    1. Preserve the abend screen, ABEND.LOG, CONSOLE.LOG, core dump if configured, MODULES list, application logs, and the exact preceding change/workload.
    2. Prevent an uncontrolled restart loop. Automatic restart can hide recurring abends; check ABEND.LOG and server up time routinely. [S2, S4]
    3. Identify the faulting NLM, address space, thread, and dependency chain. Determine whether it ran in the kernel or a protected space.
    4. Reproduce only in an isolated clone with matching data and versions. Do not swap NLMs across support packs merely because file names match.
    5. If a protected application space faults, review restart/no-restart policy and product recovery semantics before reloading it.
    6. Treat resulting file-system or application inconsistency separately; a recovered kernel does not prove data consistency.

    eDirectory synchronization errors   Back to contents

    1. Run the directory health sequence: versions, time synchronization, replica synchronization, schema synchronization, obituaries, and external references.
    2. Verify IP/IPX reachability, NCP/NDAP service addresses, SLP/SAP discovery, DNS, firewall rules, and the replica ring’s server objects.
    3. Use DSREPAIR Report Synchronization Status and DSTRACE filters to collect the error and affected partition; seek All Processed = Yes for healthy rings. [S10]
    4. Resolve time, connectivity, name/address, disk-space, and version defects before repairing the directory database.
    5. Back up directory state and record replica roles before partition, replica, or obituary repairs. Coordinate changes across every server in the ring.

    Backup and disaster recovery   Back to contents

    What a usable backup must preserve   Back to contents

    Recovery asset inventory

    AssetPreserveWhy
    Boot environmentDOS partition/image, SERVER.EXE, STARTUP.NCF, AUTOEXEC.BAT, driversNeeded before SYS and network services are available.
    SYS configurationAUTOEXEC.NCF, SHUTDOWN.NCF, SYS:ETC, NLM/application config, logsReconstructs service identity and load order.
    DirectorySupported NDS/eDirectory backup, schema, partitions/replicas, certificatesA file copy of the live DIB is not a supported directory backup.
    File dataFiles plus trustees, IRFs, ownership, attributes, namespaces, quotas, linksA generic SMB copy can lose NetWare metadata and security.
    ApplicationsVendor-consistent database/message-store backup and transaction logsVolume-level consistency does not ensure application consistency.
    Storage mapController/LUN/RAID, devices, partitions, pools, volumes, cluster resourcesRequired to present the same data in the same ownership model.
    Software entitlementInstall/overlay media, support packs, patches, drivers, licenses, keysDownloads and activation services may no longer be obtainable.
    Operational evidenceRunbooks, credentials escrow, dependencies, test results, hashesTurns backup media into a repeatable recovery.

    BACKUP SEMANTICS: Use Storage Management Services or another NetWare-aware product for trustee and namespace fidelity, plus an application-aware method for databases and directory services. Test the exact restore path; a successful backup job is not evidence of recoverability.

    Recovery rehearsal   Back to contents

    1. Create an isolated recovery network with no route to production and a controlled time/DNS/SLP design.
    2. Recover the boot environment and virtual/physical hardware drivers, then start with normal NCF files suppressed if necessary.
    3. Present storage consistently and recover SYS before application/data volumes. Validate TFS/NSS type before any repair action.
    4. Restore the directory using its supported method and intended replica topology. Avoid creating duplicate server or tree identities on a connected network.
    5. Restore file data with trustees, IRFs, ownership, attributes, quotas, and namespaces, then application data with vendor consistency checks.
    6. Test representative authentication, login scripts, rights, mappings, locks, salvage, print, backup, and application transactions.
    7. Record recovery time, manual decisions, missing assets, and new hashes. Update the runbook and repeat until another engineer can execute it.

    Printing and ancillary services   Back to contents

    Printing generations   Back to contents

    NetWare printing models

    ModelCore objects/servicesClient experience
    Queue-based printingPrint Queue, Printer, Print Server; PSERVER; CAPTURE/NPRINTLPT redirection or queue submission; common in 3.x/4.x.
    NDPSBroker, Manager, Printer Agent; NDPSMDirectory-discovered printers, driver distribution, status and notification.
    iPrintIPP-based print services and web installationBrowser/client printer installation and IP transport; mature in 6.x/OES.
    • Inventory printer agents, gateways, drivers, queues, ports, DNS names, and application dependencies before migration.
    • A user can authenticate and map drives successfully while printing fails through an independent Broker/Manager/gateway path.
    • Legacy printer drivers are executable code. Preserve them for recovery but do not deploy them to unsupported modern clients without containment and testing.

    Other common services   Back to contents

    Common optional services

    ServiceTypical roleMigration/containment note
    DNS/DHCPDirectory-integrated network servicesExport zones, subnets, options, and service-object dependencies.
    NetStorageWeb access to NCP/CIFS-backed filesIsolate old web/TLS; login-script support is partial.
    iFolderUser file synchronizationInventory clients, stores, policies, and conflict behavior.
    Apache/Tomcat/MySQL/PHPWeb/application platform on 6.5Version-specific security/consistency; migrate rather than expose.
    GroupWiseMessaging and collaborationUse product-specific domain, post-office, and agent migration.
    Btrieve/PervasiveTransactional database engineCoordinate shutdown, logs, locks, and version compatibility.
    Cluster ServicesFailover for volumes and servicesPreserve virtual NCP identity, scripts, preferred nodes, and shared storage.
    SMS backupTSA/SMDR/SBCON backup frameworkRecord agent, media, catalog, encryption, and restore dependencies.

    Containment, preservation, and migration   Back to contents

    Minimum containment pattern   Back to contents

    1. Place NetWare and any dependent legacy clients on a dedicated VLAN or virtual switch with no direct Internet route.
    2. Default-deny at the firewall. Permit NCP, SLP, DNS, NTP, backup, directory, print, and application flows only between documented endpoints.
    3. Use a hardened jump host with the compatible Novell Client and management tools. Reach the jump host through modern MFA and encrypted remote access.
    4. Send logs and monitoring outward through a controlled relay or poll from a collector; do not install untested modern agents into the NetWare kernel.
    5. Keep offline, immutable copies of installation media, patches, drivers, configuration, license artifacts, system images, and data backups.
    6. Set an explicit retirement date and risk owner. Containment reduces exposure; it does not make unsupported code supportable.

    Migration sequence   Back to contents

    Staged migration

    StageActivitiesExit criterion
    DiscoverInventory services, directory roles, applications, volumes, trustees, clients, print, protocols, and dependenciesAuthoritative dependency and data map approved
    StabilizePatch to the approved terminal level, fix time/replication/storage errors, test backup and restoreHealthy, repeatable source baseline
    DesignSelect supported OES/Enterprise Server, Windows/Linux, SaaS, or application-specific destinations; map identity and rightsTarget architecture and rollback signed off
    PilotMigrate representative users/data/printers/apps with metadata-aware toolsFunctional, security, performance, and recovery tests pass
    CoexistIntroduce target services, NCP/CIFS/client changes, DNS/SLP updates, and staged data synchronizationUsers operate on target with measured exceptions
    Cut overQuiesce source, final sync, redirect mappings/services, validate rights and applicationsBusiness acceptance and rollback decision closed
    RetireRemove applications, replicas, service objects, licenses, routes, and storage in supported orderNo hidden dependency; evidence and retention complete

    METADATA-AWARE COPY: Use the supported migration/consolidation tool or an NSS/NCP-aware process when trustee assignments, IRFs, ownership, namespaces, Macintosh metadata, quotas, or application attributes matter. Generic drag-and-drop or SMB copies are not equivalent. [S12, S15]

    Virtualization and historical preservation   Back to contents

    • NetWare 6.5 SP8 documented VMware and Xen guest deployments, but compatibility depends on virtual CPU, storage, network adapter, and driver choices. [S1]
    • Preserve the original disk images before converting formats. Work on a verified copy and record hashes before and after transformation.
    • Keep the virtual NIC disconnected during the first boot of a clone to prevent duplicate server names, internal network numbers, tree identities, or replica activity.
    • Match old virtual hardware where possible. A newer hypervisor’s default controller or NIC may have no NetWare driver.
    • Capture console video/screens, configuration, volumes, application behavior, and client workflow as part of preservation, not only a bootable VM.
    • If the goal is evidence or data extraction rather than continued service, prefer an offline, read-only recovery workflow over production resurrection.

    Appendix A – Common paths and files   Back to contents

    Locations commonly encountered on NetWare 4.x-6.5

    LocationContents / use
    C:\NWSERVER\SERVER.EXENetWare server loader/kernel image.
    C:\NWSERVER\STARTUP.NCFPre-SYS SET parameters and platform/storage drivers.
    C:\NWSERVER\BOOT$LOG.ERRBoot messages/errors according to logging configuration.
    C:\ABEND.LOG then SYS:SYSTEM\ABEND.LOGAbend record before and after restart/copy.
    SYS:SYSTEMCore NLMs, AUTOEXEC.NCF, SHUTDOWN.NCF, utilities, application start files.
    SYS:PUBLICClient utilities and management program files.
    SYS:LOGINFiles accessible during login and pre-authentication workflows.
    SYS:ETCNetwork/service configuration and logs, including SLP.CFG and CONSOLE.LOG.
    SYS:ETC\CONSOLE.LOGDefault CONLOG output.
    SYS:SYSTEM\DSTRACE.DBGDirectory trace output when trace-to-file is enabled.
    SYS:_NETWAREHidden/system directory containing directory database and security data; never treat as ordinary file content.
    SYS:SYSTEM\SYS$LOG.ERRCommon system error log location on many releases.
    volume-root\VOL$LOG.ERRTraditional volume error/repair log commonly found at a volume root.

    VERSION VARIANCE: Paths can be redirected, clustered, or changed by products and support packs. Treat this appendix as a discovery list, then confirm with CONFIG, SEARCH, module parameters, NCF files, and the matching manual.

    Appendix B – Glossary   Back to contents

    Glossary

    TermDefinition
    AbendAbnormal end: a NetWare fault or exception that can suspend a thread, fault an address space, or stop/restart the server.
    BinderyPer-server flat database of users, groups, properties, and services used primarily by NetWare 2.x/3.x.
    Bindery contextOne or more eDirectory containers exposed as a flat Bindery view for legacy clients/applications.
    CDMCustom Device Module in the NetWare Peripheral Architecture storage stack.
    DIBDirectory Information Base: the local NDS/eDirectory database.
    Directory MapeDirectory object that represents a path and reduces hard-coded mapping dependencies.
    Distinguished nameAn object’s unique hierarchical name in the eDirectory tree.
    eDirectoryLater name and evolution of Novell Directory Services (NDS).
    HAMHost Adapter Module: storage adapter driver in NWPA.
    IRFInherited Rights Filter: blocks selected rights inherited through a hierarchy.
    IPX/SPXLegacy Novell routed network and connection-oriented transport protocol suite.
    NCPNetWare Core Protocol: client/server file and network service protocol.
    NCFNetWare Command File: a server-side batch/configuration file.
    NDSNovell Directory Services: distributed directory introduced with NetWare 4.
    NDPSNovell Distributed Print Services, the directory-based successor to queue printing.
    NamespaceFile-name and metadata representation for DOS, LONG/Windows, Macintosh, NFS, or other clients.
    NLMNetWare Loadable Module: executable server component linked into the runtime.
    NSSNovell Storage Services: journaling file system and storage-pool/volume architecture.
    NWPANetWare Peripheral Architecture for HAM/CDM-based storage drivers.
    ODIOpen Data-Link Interface used by classic Novell client LAN/protocol stacks.
    OESOpen Enterprise Server, the Linux-based successor platform for eDirectory, NCP, NSS, iPrint, and related services.
    PartitionContiguous subtree replicated as a unit in NDS/eDirectory.
    PSMPlatform Support Module for processor/chipset/platform integration.
    ReplicaCopy of a directory partition held by a server; types include Master, Read/Write, Read-Only, and Subordinate Reference.
    Replica ringSet of servers holding replicas of the same partition.
    SAPService Advertising Protocol used to advertise services in IPX networks.
    SalvageRecovery of files retained after deletion but before purge/reclamation.
    SLPService Location Protocol used for IP service discovery and registration.
    SMSStorage Management Services: NetWare backup architecture using agents such as TSA and SMDR.
    TFSTraditional NetWare File System, distinct from NSS.
    TrusteeUser, group, or object assigned rights to a target directory, file, or directory object.
    VLMVirtual Loadable Module client architecture used by DOS NDS-aware clients.
    VolumeNamed NetWare file-system container such as SYS or DATA, exposed through NCP and represented by an eDirectory object in NDS-era systems.

    Appendix C – Official source set   Back to contents

    Sources were selected from surviving Novell, Micro Focus, NetIQ, and OpenText documentation. They were accessed on 8 August 2026. Product pages and document hosts can move; retain local archival copies where licensing permits.

    [S1] NW 6.5 SP8 Installation Guide. Open official source

    [S2] NW 6.5 SP8 Utilities Reference. Open official source

    [S3] NW 6.5 SP8 NLM Reference. Open official source

    [S4] NW 6.5 SP8 Server Operating System Administration – Troubleshooting. Open official source

    [S5] NW 6.5 SP8 NSS File System Administration Guide. Open official source

    [S6] NW 6.5 SP8 File Systems Management Guide – attributes and trustees. Open official source

    [S7] NW 6.5 SP8 Planning and Implementation Guide. Open official source

    [S8] NetIQ eDirectory 8.8 SP8 Administration Guide – eDirectory Rights. Open official source

    [S9] Novell Login Scripts Guide. Open official source

    [S10] NDS/eDirectory Health Check Procedures – Cross Platform. Open official source

    [S11] NW 6.5 SP8 Novell Remote Manager Administration Guide. Open official source

    [S12] Open Enterprise Server – Coexistence and Migration of File Services. Open official source

    [S13] OpenText Product Support Lifecycle. Open official source

    [S14] SLP Design and Implementation Guidelines. Open official source

    [S15] Novell Server Consolidation and Migration Toolkit. Open official source

    EDITION NOTE: This reference deliberately avoids prescribing hardware-specific driver lines, destructive repair options, or a current migration destination without an environment inventory. Those decisions must be made against the exact server state and the current support/interoperability matrix.

  • The New Eden Lottery

    We sold Mars for ten dollars a ticket.

    That was the genius of it.

    Not rockets. Not fusion engines. Not the gold-plated spaceship squatting on the launchpad like a billionaire’s bathroom fixture. The genius was the lottery.

    TEN DOLLARS TO BUILD TOMORROW.

    That was the slogan. It appeared on buses, churches, porn sites, government buildings and the sides of delivery drones. Teachers sold tickets in school corridors. Cops sold them at traffic stops. Children shook collection cans outside supermarkets while the supermarkets rounded up every purchase and claimed the tax deduction.

    Everybody bought one.

    Left-wing people bought tickets because Mars would be sustainable. Right-wing people bought tickets because Mars would be free. Libertarians bought them because there would be no government. Socialists bought them because the mission belonged to humanity. Christians bought them because the red planet was clearly mentioned in Revelation if you read it correctly. Tech people bought them because they thought dying in space was innovation.

    Nobody understood what the prize was.

    That was deliberate.

    The advertisements showed crystal towers rising from crimson valleys. Artificial rivers crossed green deserts. White children and brown children held hands under a transparent dome while a robot planted wheat behind them. There were lions everywhere.

    The New Lion, they called Mars.

    Nobody knew what that meant either, but it tested well.

    Mars was the New Eden, the New Babel, the New Frontier and the New Jerusalem. It was a capitalist utopia where ambition would no longer be restricted by gravity, morality or the federal tax code. On Mars, the advertisements promised, humanity would finally become whatever it deserved to be.

    The ultra-rich heard something different.

    They heard that Mars had no extradition treaties.

    They heard there were no journalists.

    No unions.

    No age-of-consent laws.

    No inheritance taxes.

    No environmental regulations.

    No angry former employees.

    No neighbours.

    No democracy unless they wanted one for decorative purposes.

    Anything was possible there.

    Yes. Anything.

    We made sure they understood that part.

    The applications arrived immediately.

    The first billionaire bought an entire residential deck. Another reserved a valley and renamed it after his mother, although his mother was still alive and begging him not to go. Oil princes commissioned indoor rainforests. Crypto barons demanded private currencies. Media owners ordered harems, cloned pets and arenas where disputes between employees could be settled by combat.

    One former president asked whether Mars had term limits.

    We told him no.

    He wired the money before lunch.

    The ship was called the Providence, because rich people like names suggesting God has personally approved their accounting practices. It was three kilometres long, plated in something that looked like gold and powered by a drive nobody outside the project was allowed to inspect.

    The passenger list was beautiful.

    Bankers. Oligarchs. Weapons executives. Private-equity surgeons. Data miners. Hedge-fund prophets. Influencers who sold nutritional sand. The men who owned the water. The women who owned the men who owned the water. Every bastard who had ever described poverty as a failure of imagination.

    They brought chefs, servants, bodyguards, art collections, embryos, vintage wine, racehorses and enough cocaine to terraform a small moon.

    They did not bring plumbers.

    We suggested plumbers.

    They laughed.

    They said robots would do it.

    That was when I knew we were going to win.

    I was twenty when I joined the campaign. I called myself an anarchist because I had read half a book and hated my landlord. Three months later I was a democratic socialist. Then a civic nationalist. Then a free-market populist, briefly, after a woman with excellent cheekbones explained monetary sovereignty to me in a nightclub toilet.

    By launch day I believed in everything.

    Borders and no borders.

    Workers’ councils and small business.

    Public ownership and private guns.

    Universal healthcare and mandatory exercise.

    Peace through strength.

    Strength through peace.

    America without empire.

    America as the only empire morally qualified to abolish empires.

    People said I was inconsistent.

    I said consistency was how dead people defended their mistakes.

    The launch happened on a Tuesday.

    It should have been a national holiday, but productivity analysts said that would hurt quarterly growth, so we abolished quarterly growth instead.

    Three million people gathered around the spaceport. Another billion watched online. The billionaires waved from a balcony halfway up the ship, dressed in white and gold like a convention of sexually confused angels.

    They looked happy.

    Why wouldn’t they?

    They had beaten death, taxation and the human species.

    The President gave a speech about courage. The opposition leader gave the same speech with different pauses. A famous child sang the national anthem while autonomous cameras circled overhead.

    Then the engines ignited.

    The ground shook.

    The Providence rose slowly, obscenely, carrying half the world’s concentrated wealth into the blue.

    People began cheering.

    Not polite cheering. Not patriotic cheering.

    Animal cheering.

    The sound of a civilisation vomiting out a bone.

    The ship climbed through the clouds. The gold hull became a bright needle, then a spark, then nothing.

    We waited.

    There was a delay of eight minutes while mission control confirmed the trajectory.

    The public did not know there were two trajectories.

    The official flight plan curved toward Mars.

    The real one curved outward.

    Past Mars.

    Past Jupiter.

    Past the orbit of Neptune.

    The Providence had enough fuel to accelerate for eighteen months. It did not have enough fuel to slow down.

    That was the whole plan.

    We did not kill them.

    That distinction mattered to some people.

    We gave them the finest ship ever built. Orchards, theatres, swimming pools, hospitals, spas and five hundred years of entertainment. We gave them every luxury their money could buy.

    We simply neglected to provide a destination.

    The message revealing this was scheduled to play once Earth was too far away for rescue.

    I helped write it.

    It said:

    Congratulations. You have achieved complete independence from society.

    That evening we held the mother of all parties.

    Times Square became a communal kitchen. Wall Street became a dance floor. People climbed onto trading terminals and poured supermarket champagne into the keyboards. Someone projected the passenger manifest onto the stock exchange while ten thousand people shouted each name and voted on whether to forgive them.

    Most were not forgiven.

    The banks closed at midnight.

    By one, the dollar had crashed.

    By two, every debt database in the country had been copied, printed and set on fire.

    By three, the fires had spread to the tax offices, property registries and the headquarters of six major insurance companies.

    People called it chaos.

    They were right.

    It was magnificent.

    We burnt the economy because the economy had spent generations burning us. Mortgages vanished. Credit scores became meaningless. Rent contracts were shredded in the streets. Supermarket workers opened the warehouses. Nurses occupied private hospitals. Mechanics took over the autonomous vehicle fleets and turned them into free buses.

    Congress met in emergency session and rescinded the laws.

    All of them.

    That was not supposed to happen.

    The proposal had begun as a joke. A constitutional reset. A twenty-four-hour legal silence during which the country would decide what rules it actually wanted.

    But the old lawmakers had lost their donors, their lobbyists and most of their private helicopters. They were frightened. We were loud.

    So at 4:17 in the morning, the statute books expired.

    For six hours, America had no federal law.

    People did not become monsters.

    That disappointed several television commentators.

    There was looting, yes. Mostly food, medicine and televisions. A luxury handbag store was stripped bare, though the bags were later used to carry insulin between neighbourhood clinics.

    Three men tried to form private kingdoms.

    Two were laughed out of town.

    The third lasted until breakfast.

    The police disappeared in some cities and joined the crowds in others. Soldiers guarded water plants and refused orders to disperse civilians. Judges set up folding tables outside courthouses and began asking people what justice should look like.

    We called those days the Confluence.

    Everything met there.

    Left and right.

    Faith and atheism.

    Workers and owners who still did some work.

    The rural counties sent grain. The cities sent doctors, software and pornography. Churches became dormitories. Shopping centres became assemblies. Former prisons became housing, archives and, in one case, a very successful indoor mushroom farm.

    We wrote a constitution in public.

    It was ugly.

    Everyone shouted.

    Gun owners demanded liberty. Mothers demanded safety. Workers demanded ownership. Farmers demanded independence. Indigenous nations demanded that America stop pretending it had invented the ground.

    We argued for nineteen days.

    We nearly broke apart six times.

    On the twentieth day, we agreed that nobody should be rich enough to buy another person’s future.

    Everything else followed from that.

    The new constitution was only seven pages long. Half of it concerned water, housing, voting and the right to leave any job, marriage, church, algorithm or nation that claimed to own you.

    There was still money.

    There were still businesses.

    There were still flags, borders, churches, guns, unions, families, markets and people selling terrible coffee at criminal prices.

    Freedom did not make us pure.

    It made us responsible.

    Years later, the Providence sent its final transmission.

    The billionaires had split into factions.

    The property faction controlled the orchards. The security faction controlled the air. The crypto faction had created seventeen currencies and starved because none could be exchanged for potatoes.

    Their leader appeared on-screen wearing a military uniform stitched from hotel curtains.

    He demanded rescue.

    He appealed to human rights.

    He said no person should be abandoned simply because society disliked them.

    For once, the bastard was correct.

    We debated for three days.

    Then we transmitted the new constitution to the ship.

    We told them we would begin designing a rescue mission when they ratified it, disarmed their private security forces, freed their workers, pooled their resources and accepted one equal vote per person.

    The answer came months later.

    A single sentence.

    WE WOULD RATHER DIE FREE.

    We sent back:

    That is your right.

    Sometimes I think about them passing through the dark, still drinking old wine and arguing over who owns the stars outside the windows.

    Sometimes I feel guilty.

    Then my rent reminder does not arrive.

    My medical bill does not arrive.

    My student loan statement does not arrive.

    Instead, the local assembly sends me a notice asking whether I can work two hours at the community kitchen on Saturday.

    I complain about it.

    That is freedom too.

    We did not build Eden.

    We were twenty years old. We could barely build a table without arguing over whether screws represented industrial hierarchy.

    But we cleared some ground.

    We took the men who believed they owned the future and gave them exactly what they wanted:

    A world with no government.

    No taxes.

    No workers’ rights.

    No limits.

    No one to tell them no.

    Just themselves, forever, travelling deeper into the perfect freedom of empty space.

  • Þe Rym of Grundfarver and Hys Shoggvth

    Hark, knave-bairns, hark ye weel,
    Whan winter byteth toe and heel,
    Whan swyn lie warme and men lie cold,
    And piss i’ þe pot turneth rimy-old.

    Shut þy gobbe and bar þe dore,
    For Grundfarver walketh atte moor.

    Old Grundfarver, grey o’ beard,
    By wife and goose and priest y-feared,
    Cometh whan þe church-bell cracketh,
    And summat wet behind him slakketh.

    Clop, clop, goeth hys wodden shoon.
    No man seeth him under noon.
    A leaden bell hangeth at hys knee,
    And what it calleth—God save thee.

    “Bairn,” quoth he, “hast swept þe ash?
    Hast fed þe sow and emptied trash?
    Hast minded Mam and bowed to Da?
    Or stol’n þe cheese and blamed þe ca’?”

    For Grundfarver knoweth every trick,
    Who stole an egg, who kicked þe dick—
    The cock, I mean, thou gutter-head!
    Get thee hence and make thy bed.

    He knoweth who hath pissed i’ þe ale,
    Who loosed þe reeve’s old milking-pail,
    Who put a turd beneath þe stool
    And swore Saint Dunstan played þe fool.

    “Heh! Not I!” saith Hans þe Red.

    “Not me!” saith Ulf from under bed.

    “By Mary’s bum, I tell thee true!”

    Then under þe floor—

    glup.

    glup.

    shluu.

    For under midden, sty and byre,
    Under dung and dead hearth-fire,
    Beneath þe turnip, bone and clot,
    Squatteth Grundfarver’s Shoggvth.

    No eyen hath it.

    Yet it spies.

    No nose hath it.

    Yet smelleth lies.

    No mouth men ken—

    yet gobbeth wide
    When naughty bairns be put inside.

    Black as ditch-mud.

    Soft as suet.

    Kick it once—

    thou shalt rue it.

    It bubbleth like þe brewer’s vat,
    Only brewer’s beer ne winketh back.

    Grete Gerta stole þe priest his hen.
    Young Klaus shat i’ þe well agen.
    Peder brake þe widow’s gate.
    Hanne ate what was not on her plate.

    Little Knut cried:

    “Bollocks! Nay!”

    Grundfarver came that selfsame day.

    Three knocks gave he upon þe plank.

    Tok.

    Tok.

    TONK.

    And all þe house of brimstone stank.

    “Who be there?” called Mutter Bess.

    “Taxman?”

    “Nay.”

    “Þe Pest?”

    “Much less.”

    “Then sod thee off, whoever thou art!”

    Grundfarver laughed:

    “I seek thy brat.”

    Down þe stair by tallow gleam,
    Past salted cod and soured cream,
    Past sausage-hook and cabbage bin,
    Past Grandam’s teeth kept in a tin.

    Down where þ’ midden sweats and steams,
    Where beetles hatch their little dreams,
    There Grundfarver lifts hys sack.

    Naughty bairns come seldom back.

    Some say bones come up in spring.

    Some say that is no such thing.

    Some say old Lars found half a shoe.

    Lars drinks hard.

    So who knows true?

    But good bairns, mark, have better lot—

    Though “better” meaneth not much, God wot.

    Good bairns rise ere cock hath crowed,
    Haul þe dung and mend þe road,
    Scrape þe pot and feed þe sow,
    And never ask where bad bairns go.

    They churn þe butter.

    Skim þe whey.

    Carry grandfather’s fleas away.

    Pick þe lice from Bruder’s hood.

    Say “aye” when told.

    For aye is good.

    And when seven winters they have seen,
    And noses run but souls stay clean,
    Grundfarver cometh, scrubbed and spruce,
    Smelling faintly of boiled goose.

    “Ho, good bairns! Up ye get.

    Thy King hath need of servants yet.”

    He washeth each in juniper smoke,
    Giveth each a yellow cloak,
    A hempen belt, a midden-spoon,
    And sends them marching by þe moon.

    North they fare by bog and fen,
    Past þe graves of nameless men,
    Past þe gallows, black and high,
    Where three old thieves teach crows to fly.

    Past þe kirk where no priest sings,
    Past þe mere where dead ice rings,
    Past þe stone that saith:

    GO BACK.

    Naturally, they leave þe track.

    At last they come where no road goeth,
    Where neither wheat nor thistle groweth,
    Where stars hang wrong and winds speak low:

    There dwelleth þe King in Y’ellou.

    No hall hath he.

    No roof.

    No wall.

    Yet somehow hath he got them all.

    No throne men see.

    No crown men ken.

    Yet kings be kings to little men.

    Upon hys lap þe good bairns creep—

    Not for cuddles.

    Nay.

    For keep.

    There midden-servants shall they be,
    From winter dusk till eternity.

    They rake þe ash.

    They scrape þe plate.

    They empty pots outside þe gate.

    They polish bones with greasy rag.

    They feed black worms from yellow bag.

    They sweep þe steps that are not there.

    They comb þe King’s invisible hair.

    And when he saith:

    “Who serveth me?”

    Each bairn cries:

    “ME, LORD!”

    Properly.

    Thus old wives croak beside þe flame,
    And grandsires fart and say þe same:

    “Good bairns serve.

    Bad bairns feed.

    That be all a bairn need heed.”

    So mind þy Mam.

    Obey þy Da.

    Do not put frogs in Grandam’s bra.

    Steal not sausage.

    Pinch not pie.

    Never swear Saint Olaf’s eye.

    Piss in pot and shit in pit.

    If thou breakest summat, own to it.

    For every lie and secret blot
    Maketh fat old Shoggvth hot.

    And if at night beneath thy bed
    Thou hearest summat soft and dread—

    Shlukka.

    Floppa.

    Glub-glub-glub.

    Do not reach beneath, thou grub.

    Pull thy blanket o’er thy head.

    Say thy pater.

    Play thou dead.

    For better cold toes,

    better flea,

    better Mam thrash arse of thee,

    better muck and mangel-wurzel,

    better Brother’s Sunday gruel—

    Than hear by door,

    through crack and rafter,

    Grundfarver’s bell—

    and wet thing after.

    Clop.

    Clop.

    Glup.

    Amen.

  • The Saga of Grand Elric and the Yellow King

    There was a man called Elric Ketilsson, though in his old age men named him Grand Elric, for he had seen seven kings crowned, buried three sons, broken two sea-kings in battle, and lived long enough to become grandfather to half the children of Hrafnvik.

    There was a man called Elric Ketilsson, though in his old age men named him Grand Elric, for he had seen seven kings crowned, buried three sons, broken two sea-kings in battle, and lived long enough to become grandfather to half the children of Hrafnvik.

    Elric was broad in the back even when his beard had gone white. One eye had clouded after the fight at Romsdal, and the smallest finger of his left hand was missing. He owned a hall above the grey fjord, forty cattle, nine good horses and a sword called Ash-Biter, which had belonged to his mother’s father.

    Elric had three daughters.

    The eldest was Svanhild, who had a sharp tongue and knew the names of herbs.

    The second was Yrsa, who climbed trees better than boys and feared neither ice nor blood.

    The youngest was Runa, who spoke little but dreamed often, and sometimes named things before they came.

    Their mother, Alfhild, had died in the winter of the red moon.

    After this Elric became gentler with his daughters, though none would have called him gentle.

    He taught them to row, gut fish, bargain hard, hide silver, bind wounds, and never trust a man who smiled before naming his price.

    He also taught them one rule which he repeated more than all others.

    “When the sun goes under the western ridge, come home.”

    The daughters laughed at this, for they were young.

    Elric did not.

    “There are roads which begin after sunset,” he said. “A wise person does not learn where all of them lead.”

    This was in the years when men still made offerings at old stones though the new priests had begun to travel north.

    It happened one autumn that the rowan trees bore yellow fruit instead of red.

    Old women said this was a poor sign.

    The dogs would not sleep facing north.

    Milk curdled before dawn.

    A black mould spread upon the beams of the abandoned temple above Hrafnvik, and wherever it grew the wood beneath became soft although no rain had fallen.

    Runa saw it and said:

    “It is not growing on the wood.”

    “What then?” asked Svanhild.

    Runa touched the mould with a stick.

    “It is growing through it.”

    Yrsa laughed.

    “Then the tree has a sickness.”

    Runa looked toward the forest.

    “Not that tree.”

    That evening the three sisters went to gather cloudberries above the marsh.

    Svanhild wanted berries for winter medicine.

    Yrsa wished to see whether wolves had returned.

    Runa said she had dreamed of a yellow stag and wanted to find where its tracks went.

    They promised Elric they would return before the sun crossed the ridge.

    They did not.

    At dusk Elric stood outside his hall.

    The cattle had grown quiet.

    No birds moved.

    Beyond the fjord the sun sank red beneath iron clouds.

    Elric waited until the last edge of light vanished.

    Then he said:

    “They have found the wrong road.”

    He took Ash-Biter from the wall.

    His brother Torvald said, “We will take twenty men.”

    “No.”

    “Ten, then.”

    “No.”

    “Why?”

    Elric buckled on his sword.

    “Because twenty men can be lost as easily as three girls.”

    He went first to the marsh.

    There he found the daughters’ basket.

    The cloudberries within were grey.

    Beside it stood three sets of footprints.

    They crossed the mud until they reached a dead pine.

    There the footprints ended.

    Around the roots of the pine grew yellow mould.

    Elric crouched beside it.

    He did not touch it.

    He smelled neither rot nor fungus.

    He smelled cold stone, seawater, old linen and something sweet like apples left too long underground.

    Then he heard a voice.

    “Grandfather.”

    It was Runa’s voice.

    It came from beneath the roots.

    Elric drew Ash-Biter.

    “Speak again.”

    “Grandfather.”

    Then Yrsa.

    “Come quickly.”

    Then Svanhild.

    “He has found us.”

    The dead pine opened its eyes.

    Elric struck it.

    The sword cut through bark and into darkness.

    A wind came out of the wound.

    It smelled of forgotten houses.

    The tree split.

    Behind it was not earth.

    There was a road.

    Elric went in.

    The path beyond the tree was made of roots thick as ship masts.

    Some rose above him.

    Others twisted beneath his feet.

    Between them lay a darkness full of pale drifting dust.

    He understood then that he had not entered a cave.

    He had entered the World Tree.

    Men spoke much of Yggdrasil.

    They said its branches held the worlds.

    They told of the eagle in its crown, the serpent at its roots, the squirrel that carried insults between them.

    Such things were known.

    But few men spoke of what grew upon Yggdrasil.

    Every tree bears lichen.

    Every root carries worms.

    Every ancient trunk develops rot.

    Why should the World Tree be different?

    Elric walked.

    After a while he came upon a man hanging upside down from a root.

    The man wore a merchant’s cloak.

    His beard reached toward the darkness below.

    “Cut me down,” said the man.

    “How long have you hung there?”

    “Three days.”

    His beard was longer than three years’ growth.

    Elric looked at his eyes.

    They were yellow.

    He walked on.

    The hanging man called after him.

    “I know where your daughters are.”

    Elric stopped.

    “So do I.”

    “Where?”

    “Wherever you do not wish me to go.”

    The merchant smiled.

    “That is wisdom.”

    Then his face opened like rotten fruit.

    Elric continued.

    Soon he reached a river running upward.

    Dead leaves floated against its current toward a lightless sky.

    A woman sat beside the river washing a yellow cloth.

    Her hair covered her face.

    Elric said:

    “What river is this?”

    She answered:

    “The river between the places rivers go.”

    “What realm is this?”

    “No realm.”

    “Whose land?”

    “No land.”

    “What king rules here?”

    At this the woman stopped washing.

    “You know.”

    Elric said nothing.

    The woman lifted the cloth.

    It was stained with handprints.

    Three were small.

    Elric’s hand tightened on Ash-Biter.

    “Where are my daughters?”

    The woman pointed upstream.

    “Where the tree is sick.”

    Elric crossed the river.

    The water climbed his boots and ran upward along his legs, but he kept walking.

    On the far bank stood a hall.

    Its roof was covered in yellow moss.

    Its doors were carved with scenes Elric could not understand.

    Men knelt before empty thrones.

    Ships sailed across dry land.

    Children stood beneath suns with black centres.

    At the top of the door was carved a tree.

    A stain spread across its trunk.

    Inside the stain was a crown.

    Elric spat upon it.

    The doors opened.

    Within sat a feast.

    Hundreds of people ate in silence.

    Some wore clothes from Elric’s own time.

    Others wore armour of patterns he had never seen.

    Some were naked and painted blue.

    Some wore robes sewn with stars.

    At the high table sat a figure in yellow.

    Its robe hung in folds too deep for cloth.

    Its face was covered by a pale mask.

    Around its head rose a crown like branching fungus.

    Beside the throne stood Svanhild.

    She held a cup.

    Yrsa stood at the foot of the table with a spear.

    Runa sat upon the King’s lap.

    Elric walked into the hall.

    None of the feasters looked up.

    The Yellow King said:

    “Grand Elric.”

    Elric answered:

    “Dung in a robe.”

    Several feasters gasped.

    The King tilted its head.

    “You have travelled far to insult your host.”

    “I have travelled far because you stole my daughters.”

    “I stole nothing.”

    “You took them from Midgard.”

    “They walked here.”

    “They are children.”

    “So are men.”

    Elric stepped closer.

    “Svanhild.”

    She stared ahead.

    “Yrsa.”

    No answer.

    “Runa.”

    The youngest blinked.

    Her eyes filled with tears.

    The King placed one long hand upon her hair.

    “She sees most clearly.”

    Elric raised Ash-Biter.

    The hall laughed.

    Not the people.

    The hall itself.

    Beams shook.

    The floor breathed.

    The Yellow King said:

    “You believe this is a place.”

    “I know it is not.”

    “You believe I am a god.”

    “No.”

    “You believe I am a giant?”

    “No.”

    “Then what am I?”

    Elric looked at the yellow growth climbing the pillars.

    “A mould.”

    For the first time, the King became still.

    Elric continued.

    “You grow where the worlds rub against one another. You feed where meanings rot. You wear a crown because men fear kings. You speak because men fear words. You sit in a hall because men understand halls.”

    The mask turned toward him.

    “And if you understand me so well, old man, why do you fear me?”

    “Because mould can kill a house.”

    The King laughed.

    This time the walls bled yellow dust.

    “You are wiser than those who call me demon.”

    “I have repaired roofs.”

    The King rose.

    He was taller standing than the hall should have allowed.

    Behind his robe were shapes like roots.

    “Your daughters came because they wished to see beyond their father’s law.”

    “That is what daughters do.”

    “They wanted freedom.”

    “That is what children want.”

    “They wanted knowledge.”

    “That is what fools want.”

    Yrsa’s fingers tightened around her spear.

    Svanhild looked at Elric.

    The King said:

    “They have eaten at my table.”

    Elric’s face hardened.

    “Then I shall carry them home sick.”

    “They have learned my name.”

    “Then they shall forget it.”

    “They have seen what lies between worlds.”

    “Then they shall spend their lives pretending otherwise.”

    Runa suddenly laughed.

    The King looked down at her.

    Elric knew that laugh.

    It was the laugh she used when she had hidden a frog in her sister’s bed.

    Runa opened her hand.

    Inside it lay three rowan berries.

    Red berries.

    Not yellow.

    She crushed them against the King’s robe.

    The hall screamed.

    Svanhild threw the cup into the King’s face.

    Yrsa drove her spear through the pale mask.

    Elric charged.

    Ash-Biter struck the throne.

    The blade broke.

    The throne split.

    Beneath it was not gold or stone.

    There was a knot in the World Tree.

    A great black wound surrounded by yellow rot.

    Elric understood.

    The King was not merely upon the Tree.

    It was feeding upon an injury.

    “Girls!” he shouted.

    “Cut the yellow!”

    Yrsa hacked with her spear.

    Svanhild took a feast knife.

    Runa tore at the growth with both hands.

    Elric seized the broken half of Ash-Biter and carved into the rotten wood.

    The Yellow King became many things.

    A stag.

    A drowned child.

    Alfhild, Elric’s dead wife.

    Elric himself as a young man.

    A sun with a black centre.

    A mouth in a field of snow.

    A king.

    A beggar.

    A stain.

    Each shape begged or threatened.

    Elric kept cutting.

    At last the yellow growth tore free.

    Beneath it was living wood.

    Sap flowed golden-red from the wound.

    The hall vanished.

    The feast vanished.

    The dead vanished.

    The daughters fell.

    Elric caught Runa.

    They stood upon a root beneath a sky filled with stars.

    Far away something howled.

    The sound came from no throat.

    It was the cry of a parasite torn from its host.

    Elric looked into the darkness.

    The Yellow King was no longer a king.

    It had become an immense pale growth spreading across the void, all filaments and eyes and ragged membranes.

    It spoke with thousands of voices.

    “I WILL GROW AGAIN.”

    Elric answered:

    “So will we.”

    Then the root beneath them split.

    They fell.

    Elric woke beside the dead pine.

    Morning had come.

    Svanhild lay beside him.

    Yrsa was tangled in heather.

    Runa slept with her head against a stone.

    The daughters had been gone one night.

    Elric had aged ten years.

    His beard, already white, reached almost to his belt.

    Ash-Biter lay broken beside him.

    Yellow mould covered the blade.

    Elric buried both pieces beneath running water.

    The daughters spoke little of what had happened.

    Svanhild became a healer and would never allow yellow fungus to grow near her house.

    Yrsa became a ship-captain and refused to sail beneath stars she could not name.

    Runa became a teller of stories.

    She never told the whole truth.

    When Grand Elric finally died, many winters later, his daughters burned him on a pyre of rowan, ash and pine.

    Before they lit it, Runa placed three red berries beneath his tongue.

    Men asked what this meant.

    She said:

    “It is payment for the road home.”

    After Elric’s death the people of Hrafnvik cut yellow mould from every beam and burned it beyond the settlement.

    Children were told never to follow voices beneath roots.

    When they asked why, the old people said:

    “There are nine worlds upon the Tree.

    And between them are places that are not worlds at all.

    Things live there.

    Some are older than gods.

    Some are smaller than worms.

    Do not think small things harmless.

    A worm may kill a tree.

    A mould may wear a crown.”

    And this became a saying among Elric’s descendants:

    A king is only a king where men agree to kneel.
    But rot needs no permission.

  • Vampire: The Masquerade and the Playable Vampire

    Structure, aesthetics, performance and psychology
    in the afterlife of a role-playing game

    Thesis. VTM’s most consequential innovation was not a new vampire costume but a new cultural procedure: it converted the vampire from an object of narration into a playable social position. Clan, sect, hunger, status and conscience became things an audience could inhabit, negotiate and perform. That procedure travelled from rulebooks into novels, film, games, live-action play, clubs, streamed “actual play” and social-media identity.

    Research essay  |  5 August 2026

    Evidence note: direct adaptation, documented influence, scholarly attribution and resemblance are distinguished throughout.

    A game that escaped the rulebook

    Vampire: The Masquerade (VTM) did not invent the modern vampire. It did something more culturally portable: it turned modern vampirism into a system for producing characters, communities and performances.

    Published by White Wolf in 1991, VTM arrived after a long reconstruction of the vampire by Bram Stoker, F. W. Murnau, Hammer Horror, Anne Rice, The Hunger, The Lost Boys, Near Dark and the goth and post-punk scenes. Its debts matter. Cultural influence here is not a clean family tree in which one original work begets passive copies. It is a feedback loop. VTM assembled prior literary, cinematic, musical and subcultural material into what it called a “gothic-punk” world; players then carried that synthesis into clubs, conventions, fiction, visual media and online life. Later media returned similar structures and images to audiences who might never have opened a rulebook. [1–4]

    The game’s historical importance therefore lies less in ownership of particular motifs than in their arrangement. Its fictional present looks like the ordinary city seen “through a glass darkly”: institutions are corrupt, architecture is oppressive, wealth is predatory and history is not past but embodied in immortal elders. Yet players do not simply encounter a vampire. They decide what kind of vampire to be, whom to obey, what to desire and how much humanity to sacrifice. White Wolf’s preferred term, “Storyteller,” signalled the shift from tactical referee to organiser of collaborative drama, while “chronicle” suggested an extended social history rather than a chain of adventures. The official description still places personal horror at the centre: the player is the monster and must live with moral consequences. [1]

    The structural grammar of the modern vampire

    VTM’s first major influence is structural. Earlier vampire stories certainly contained societies, lineages and conflicted immortals, especially in Anne Rice. VTM scaled those elements into an explorable institution. A city had a Prince, court, territory and offices; a vampire had a sire, generation, clan and status; clans possessed powers, weaknesses, tastes and political histories; sects offered rival ideologies; the Masquerade supplied both a rule of survival and a permanent dramatic problem. The result was a matrix rather than a single plot. Any nightclub, gallery, corporation, squat, church or police department could be redescribed as a node in an invisible polity.

    That matrix changed how vampire stories could be generated. The vampire ceased to be merely a solitary aristocrat, contagious invader or romantic outsider. It became a social type inside a bureaucracy of the damned. VTM’s clans function like narrative engines: the Toreador make beauty and predation inseparable; the Ventrue turn authority into appetite; the Nosferatu convert exclusion into information; the Brujah link passion with failed revolution; the Malkavians, more problematically, aestheticise mental disturbance. A clan provides immediate legibility but does not complete a character. Players negotiate with and against the type. This tension between taxonomy and deviation is exceptionally well suited to serial fiction, ensemble television, game design and profile-based social media.

    The moral structure was equally portable. “Humanity” made ethical erosion measurable, while the Beast externalised rage, fear and appetite as an adversarial part of the self. Later rules made Hunger more intrusive and tied conscience to convictions and human relationships. These mechanics are not sophisticated clinical models, but they are effective dramatic machines. They repeatedly ask whether power reveals character, deforms it or merely provides opportunity. The central question is not “Can I defeat the monster?” but “What must I become to continue?” That question links VTM to the confessional vampire novel, prestige anti-hero television and choice-driven computer role-playing.

    Lars Konzack argues that this combination—secret society, differentiated factions, deep mythology and relations among equally elaborate supernatural populations—became foundational to twenty-first-century vampire media. His case studies include the screen version of Blade, the Legacy of Kain games, Underworld and Twilight. The strength of the claim varies. Blade existed in Marvel comics long before VTM, but its filmic vampire Houses resemble clan-based social organisation. Legacy of Kain has distinct bloodlines descended from Kain but may share older sources. Twilight’s Volturi, gifted vampires, “vegetarian” diet and vampire–werewolf settlement can be read as indirect diffusion rather than conscious borrowing. Such examples show why influence should be described as a cultural grammar, not a list of stolen nouns. [2]

    Gothic-punk as an aesthetic feedback loop

    The second influence is aesthetic. “Gothic-punk” joined apparently contrary temporalities. The Gothic contributed ruins, ancestry, Catholic residues, bodily corruption, decadent elegance and the return of buried history. Punk contributed the damaged present: graffiti, leather, clubs, alienated youth, corporate violence and the conviction that authority is both illegitimate and inescapable. VTM’s city is thus simultaneously ancient and contemporary. A medieval hierarchy operates from a nightclub; an immortal court wears late-twentieth-century subcultural style; a glass tower becomes a castle keep.

    The books made this synthesis materially persuasive. The first edition’s green-marble cover and red rose refused the crowded heroic illustration typical of fantasy games. Later photography, distressed typography, clan sigils, quotations, faux documents and Tim Bradstreet’s high-contrast figures made the rulebook resemble an artefact from the world it described. Layout was not just packaging. It trained the reader to see ordinary streets as scenery and clothing as character construction. The books circulated a kit of repeatable signs: black tailoring, fetish textures, antique jewellery, religious fragments, pale skin, industrial interiors, red against monochrome and the visual opposition of elegance and urban damage.

    VTM did not create goth culture, and the direction of influence must not be reversed. It drew credibility from clubs, music, fashion and existing vampire fandom. Yet it also fed those materials back in organised form. The 2018 World of Darkness documentary explicitly presents the game as part of a 1990s phenomenon that affected film, literature, fashion and club culture. Academic work on goth festivals likewise shows the vampire operating as a resource for gender performance, boundary-blurring and the construction of an idealised self. VTM’s contribution was to join style to an actionable identity taxonomy: clothing did not merely look vampiric; it could signal clan, sect, rank and attitude. [4–6]

    Books, film and games: transmission without a single lineage

    White Wolf deliberately built a transmedia world. Sourcebooks were written with literary ambitions; short fiction and in-world testimony established tone; city books transformed real geography into conspiratorial history; licensed novels converted shared setting into linear narrative; comics, card games, television and computer games offered other points of entry. This was not merely merchandising. Each form taught a different practice of the world. A novel demonstrated interiority, a clanbook supplied identity, a city book supplied social structure, a LARP manual supplied embodiment and a computer game supplied spatial exploration. White Wolf’s rapid expansion into five interconnected World of Darkness games also taught audiences to expect multiple incompatible viewpoints on one hidden reality. [3]

    Outside licensed work, the evidence becomes contested. The clearest controversy is Underworld (2003). White Wolf and writer Nancy A. Collins sued Sony Pictures, Screen Gems and Lakeshore Entertainment, alleging more than sixty similarities and a relationship to Collins’s World of Darkness story about a vampire–werewolf romance. The case ended in a confidential settlement, so there was no judicial finding of infringement. Rachel Mizsei Ward’s study is valuable because it shifts attention from the claim itself to fan response. Many players cared less about corporate ownership than about seeing a convincing gothic-punk vampire world on screen. Their loyalty was to a genre assemblage they felt they co-owned through play. [4]

    This is a crucial feature of RPG influence. Players are licensed, by the very act of play, to adapt. Every chronicle alters the setting; every character is a new cultural artefact; every house rule asserts interpretive authority. Fans therefore approach later films and novels as experienced comparative mythographers. They recognise a Camarilla-like council, a Toreador-like aesthete or a Masquerade-like law even when names differ. Similarities in Underworld, Blade, Twilight, True Blood or The Vampire Diaries do not prove direct descent. They indicate that VTM helped stabilise an available repertoire: the hidden vampire polity, the factional ensemble, the moral anti-hero and the city as supernatural palimpsest.

    From table to body: LARP, acting and social theatre

    The tabletop already contains theatre in compressed form. Participants alternate between actor, author, audience and critic. They describe action, speak in character, interpret rules, read one another’s reactions and jointly edit the emerging fiction. VTM intensified this tendency by privileging conversation, allegiance, seduction, intimidation and status. A political Elysium scene could consist almost entirely of eye contact, timing and implication. Dice remained, but much of the decisive action was social performance.

    Mind’s Eye Theatre moved that performance into the body. Players dressed as characters, occupied rooms as fictional territories and negotiated without a conventional stage or passive audience. Historians of the hobby credit The Masquerade with reconnecting LARP to tabletop culture in the 1990s and with attracting participants beyond the established demographic, including many more women. The fit was unusually strong: VTM required less simulated combat than many fantasy games, contemporary clothing could become costume, and clubs, campuses, hotels and civic buildings could serve as ready-made scenery. [3, 7]

    This produced a hybrid of game, improvisation, masquerade ball, subcultural gathering and immersive theatre. Unlike conventional actors, participants had no complete script and often no external audience. Unlike ordinary social life, they possessed explicit roles, rules and permission to heighten behaviour. The fictional Prince’s court could mirror real group hierarchy, while the real organiser’s authority could become disguised as fictional necessity. That doubleness explains both LARP’s intensity and its risks. The character provides an alibi for experimentation, but the group remains a real network of friendship, attraction, prestige and conflict.

    Vampire culture also crossed a more ambiguous border into self-described “real vampire” communities, donors, occult groups, fetish scenes and online identity networks. David Keyworth describes this field as segmented and polycentric and includes live-action role-players as one element among several; those categories should not be collapsed. The important point is circulation. Fictional terminology, goth performance, spiritual interpretation and lifestyle identity can share venues and digital spaces without having the same truth claims. VTM supplied a rich vocabulary, but it neither created every community nor explains every participant. [8]

    From performance to platform: social media and actual play

    Ward observed that internet forums had replaced fanzines as the principal communication medium for many role-players by the end of the 1990s. Forums widened participation and made the interpretive work of fandom visible: lore argument, campaign testimony, legal debate, costume display and declarations of subcultural credibility. Social media accelerated and miniaturised those practices. The clan became a profile badge; the character portrait became an avatar; costume became cosplay photography; a campaign anecdote became a meme, clip or short-form video. The official VTM site now includes clan and character quizzes, formalising a behaviour that fans had long performed informally: using the game’s taxonomy to answer “what kind of person—or monster—am I?” [1, 4]

    Research on female vampire fandom in MySpace, LiveJournal and other early networks found that online vampire personae often reinforced an idealised real-life identity rather than replacing it. That insight applies strongly to VTM’s networked afterlife. A profile can be simultaneously fictional, aspirational and socially consequential. Users rehearse gender presentation, erotic style, authority, vulnerability and affiliation through an aesthetic persona. The Masquerade becomes an ironic model for social media itself: a managed surface that conceals, reveals and produces the self. [9]

    “Actual play” completed another circuit. Tabletop role-play originally removed the division between work and audience because the players were both. Streaming restored an audience while preserving improvisation. Series such as L.A. by Night and NY by Night placed professional performers, dramatic lighting, publisher canon and audience commentary around a visible game table. Viewers watched two stories at once: the vampire characters’ fiction and the players’ real-time negotiation of that fiction. Media research describes this as the mediatization of tabletop play: an analogue social practice becomes spectator entertainment, platform content, advertising, merchandise and a model for how others expect games to be played. [10, 11]

    For VTM this form is especially apt. Its themes concern performance, secrecy, reputation and the gap between public role and private appetite. Clips and fan edits detach gestures from long sessions; comment threads judge moral choices; cosplay rematerialises streamed characters; performers move between videogame voice work, online persona and tabletop role. Canon is no longer delivered only from publisher to consumer. It is performed, circulated, annotated and partially stabilised by a network.

    The character as a psychological instrument

    Role-play has psychological power because it creates distance without eliminating relevance. A fictional character is “not me,” permitting experimentation, yet is chosen and animated by me, making the experiment personally meaningful. Players can externalise conflict, test a possible self, practise social behaviour and receive feedback from a group while protected by the frame of play. Studies of regular role-players identify creative expression, social support, routine, escapism and exploration of self as recurring benefits, although much of the evidence remains qualitative and should not be universalised. [12]

    VTM sharpens this instrument by building contradiction into the character. The player is simultaneously person and predator, autonomous individual and product of a bloodline, rebel and subject of ancient power. Humanity and the Beast make internal conflict public enough to discuss and dramatic enough to play. Clan and sect permit identification; deviations from them permit individuation. The vampire’s immortality encourages biography across historical periods, while the nightly need to feed turns ethics into repeated action rather than abstract belief. These devices can support reflection on shame, desire, control, ageing, alienation, class, sexuality and dependency.

    The RPG term “bleed” names the movement of affect, values, bodily states or identity between player and character. Bleed-in carries the player into the role; bleed-out carries the role back into the player. Contemporary models treat this not as automatic pathology but as a spectrum of ordinary and sometimes transformative effects. A player may retain confidence rehearsed through a Ventrue, grief experienced through a doomed relationship, or resentment generated by fictional betrayal. Long-term immersion, competitive politics and blurred interpersonal boundaries can also intensify real conflict. The same permeability that enables insight can produce distress. [13, 14]

    VTM’s older treatments of madness also require criticism. A clan curse can make psychological difference vivid, but it can reduce complex conditions to spectacle, supernatural insight or dangerous unpredictability. Likewise, a numerical Humanity scale can clarify moral stakes while encouraging the false idea that personhood is a single quantity that decreases after rule-breaking. Used reflectively, these are metaphors; treated literally, they can reinforce stigma and moral simplification. The psychologically interesting question is not whether the mechanics are true models of mind, but what kinds of self-description and group conversation they make possible.

    Gestalt therapy, psychodrama and the limits of the analogy

    The relationship between RPGs and therapy is one of convergence, not descent. VTM did not influence the creation of therapeutic role-play. Jacob L. Moreno developed psychodrama from improvisational theatre in the early twentieth century, using enactment, role reversal, mirroring and group response to work with interpersonal conflict. Gestalt therapy’s empty-chair or two-chair technique similarly stages a dialogue with an imagined person or part of the self in the present moment. Both traditions predate commercial role-playing games by decades. [15–17]

    Nevertheless, the formal resemblance is instructive. Psychodrama creates an “as-if” stage, assigns roles, permits spontaneous action and reflects on what occurred. Gestalt chair work externalises opposed positions so that a person can move between them. A tabletop chronicle also creates an as-if world, distributes roles, supports improvised encounter and generates material for later interpretation. VTM adds unusually explicit partitions: human and Beast, self and clan, desire and law, public mask and concealed appetite. In a clinical setting, those metaphors could provide handles for discussing competing needs or relational patterns—but only when a trained practitioner chooses and contains the exercise.

    Recent clinical literature explores tabletop RPGs as structured but flexible spaces for co-association, transference, creative exploration and group dynamics. A 2022 scoping review found potential for RPGs as complementary psychotherapeutic tools, but only a small minority of included sources were experimental and definitions, interventions and outcomes varied widely. Newer work remains promising rather than conclusive. Recreational play may support wellbeing; it is not psychotherapy merely because it feels meaningful. A Storyteller is not automatically a therapist, a campaign is not a treatment plan and catharsis is not evidence of durable clinical change. [18, 19]

    This distinction is particularly important for VTM because its material includes coercion, predation, loss of control, sexuality, abuse, addiction-like hunger and dehumanisation. A therapeutic adaptation would require informed consent, careful selection of themes, explicit boundaries, the ability to pause or withdraw, trained facilitation and debriefing. Safety practices are not external bureaucracy imposed on “real” play; they are part of the frame that makes intense symbolic action usable. Research on role-playing communities also shows that group schism, organiser–player power differences, relationship conflict and bleed can become genuine sources of harm. [14, 20]

    A cultural technology of the divided self

    VTM’s enduring influence is therefore larger than its licensed novels, television series or computer games, and more defensible than any claim that every later vampire court was copied from the Camarilla. It supplied a cultural technology. It organised the vampire into a set of relations—bloodline, faction, territory, appetite, status and conscience—that could generate stories indefinitely. It coupled those relations to a recognisable gothic-punk surface. Most importantly, it handed the apparatus to participants.

    That participatory transfer explains the game’s unusual reach. The reader becomes a player; the player becomes a performer; the performer becomes a photographer, streamer, fan writer, organiser or online persona; the resulting images and narratives become models for other players. The cycle is recursive. Aesthetic signs invite identity, identity produces performance, performance generates media, and media renews the signs. This is how a niche rulebook can alter a wider cultural vocabulary without every recipient knowing the source.

    The vampire has always been a figure of unstable boundaries: dead and living, aristocratic and animal, seductive and repulsive, self and contagion. VTM’s decisive move was to turn those contradictions into something collectively inhabitable. Its Masquerade is not only the fictional law that hides monsters from humanity. It is a model of mediated identity: the mask that conceals the self, the role that reveals it and the performance through which a group decides what either one means.

    References

    1. Paradox Interactive. “Our Brand: World of Darkness” and “Vampire: The Masquerade.” Official descriptions of personal horror, clans, publications and global LARP activity. View source

    2. Konzack, Lars (2015). “Mark Rein-Hagen’s Foundational Influence on 21st Century Vampiric Media.” Academic Quarter, 11, 115–128. View source

    3. Appelcline, Shannon (2007). “A Brief History of Game #11: White Wolf, Part One: 1986–1995.” RPGnet. View source

    4. Ward, Rachel Mizsei (2009). “Underworld vs the World of Darkness: Players and Filmgoers Respond to a Legal Battle.” Networking Knowledge, 2(1). View source

    5. Alderson, Giles, dir. (2017/2018). World of Darkness: The Documentary. Distribution synopsis. View source

    6. Goulding, Christina, and Michael Saren (2009). “Performing Identity: An Analysis of Gender Expressions at the Whitby Goth Festival.” Consumption Markets & Culture, 12(1), 27–46. View source

    7. Appelcline, Shannon. Historical discussion of Mind’s Eye Theatre: The Masquerade, summarised in the game’s publication history. View source

    8. Keyworth, David (2002). “The Socio-Religious Beliefs and Nature of the Contemporary Vampire Subculture.” Journal of Contemporary Religion, 17(3), 355–370. View source

    9. Mellins, Maria (2007). “Dressing up as Vampires: Virtual Vamps—Negotiating Female Identity in Cyberspace.” Networking Knowledge, 1(2). View source

    10. Švelch, Jan (2022). “Mediatization of Tabletop Role-Playing: The Intertwined Cases of Critical Role and D&D Beyond.” Convergence, 28(6), 1662–1678. View source

    11. Denny, Matt, and Nick Webber (2024). “Not Actual Play: Examples of Play and Expectations of Experience in TTRPGs.” PAIDIA. View source

    12. Walsh, Orla, and Conor Linehan (2024). “Roll for Insight: Understanding How the Experience of Playing Dungeons & Dragons Impacts the Mental Health of an Average Player.” International Journal of Role-Playing, 15, 36–60. View source

    13. Hugaas, Kjell Hedgard (2024). “Bleed and Identity: A Conceptual Model of Bleed and How Bleed-Out from Role-Playing Games Can Affect a Player’s Sense of Self.” International Journal of Role-Playing, 15, 9–35. View source

    14. Bowman, Sarah Lynne (2013/2023). “Social Conflict in Role-Playing Communities: An Exploratory Qualitative Study.” International Journal of Role-Playing, 4, 4–25. View source

    15. Riva, Michele Augusto, Luca Grassi, and Michael Belingheri (2020). “Jacob L. Moreno and Psychodrama—Psychiatry in History.” British Journal of Psychiatry, 217(1). View source

    16. Nielsen, Rikke (2021). “DreamSenseMemory,” including discussion of Gestalt therapy’s two-chair role-play. Frontiers in Psychology / PMC. View source

    17. Orkibi, Hod (2025). Psychodrama. Cambridge University Press Elements. View source

    18. Arenas, Daniel Luccas, Anna Viduani, and Renata Brasil Araujo (2022). “Therapeutic Use of Role-Playing Game (RPG) in Mental Health: A Scoping Review.” Simulation & Gaming. View source

    19. Bonnet-Brown, Lydie, and Jérôme Boutinaud (2026). “Table-Top Role-Playing Games in Psychodynamic Group Therapy.” British Journal of Psychotherapy. View source

    20. Bowman, Sarah Lynne, and Kjell Hedgard Hugaas (2025). “Philosophies of Psychological Safety in Analog Role-Playing Game Discourses.” International Journal of Role-Playing, 16, 11–33. View source

  • The Old Gods Are Not Dead: Folk Horror and the Terror of the Past That Refuses to Stay Buried

    Why we keep telling stories about villages that whisper, fields that watch, and rituals that demand blood.


    There is a particular kind of dread that does not come from a monster in the closet or a killer in the mask. It comes from the landscape itself—from the wheat swaying in a pattern too regular to be wind, from the stone circle at the edge of the village that everyone avoids after dark, from the smile of the elder who remembers the old ways and is disappointed you have forgotten them. This is the territory of folk horror, a genre less concerned with what hunts us than with what we have already agreed to feed.

    Folk horror is, at its core, a literature of trespass. It tells stories about the intrusion of the modern into the ancient—or, more terrifyingly, the intrusion of the ancient into the modern. It is the genre of the rural, the isolated, the ritualistic. It finds its horror not in the aberrant but in the traditional: the idea that somewhere, behind the hedgerows and beyond the last bus stop, communities are still keeping their end of a bargain struck centuries ago, and that bargain requires payment in blood, in silence, or in obedience. The fear it generates is not the fear of the unknown. It is the fear of the known but forgotten.


    The Landscape as Character

    What distinguishes folk horror from other horror subgenres is its setting. The city is a place of anonymity, of forgetting. You can vanish into a crowd, reinvent yourself, leave the past behind. The rural spaces of folk horror offer no such escape. In folk horror, the land remembers. The fields have been sown with the same seeds for generations. The standing stones have stood since before Christianity reached the shore. The village pub has the same families drinking in it who have always drunk there, and they know things about your bloodline that you have never bothered to learn.

    This is why the genre so often begins with an arrival. A police officer sent to a remote Scottish island, as in The Wicker Man (1973). A family moving to an idyllic New England village in Thomas Tryon’s Harvest Home (1973). A group of musicians retreating to an ancient English manor in Elizabeth Hand’s Wylding Hall (2015). The protagonist is always an outsider, armed with modern rationalism, urban skepticism, and the fatal assumption that the past is past. The horror lies in the discovery that it is not. The horror lies in realizing that the locals are not ignorant of modernity; they have simply rejected it, and their rejection is more complete than your embrace.

    In The Wicker Man, Sergeant Howie arrives as a representative of law, order, and Christian propriety, only to discover that the islanders have rebuilt their entire society around pagan fertility rites. His faith, his badge, his sense of moral superiority—none of it matters. The island does not need to be converted. He is the one who has wandered into a contract he did not know was being enforced. The film’s genius is that the islanders are not sinister in the way of a conspiracy. They are cheerful. They are communal. They are, by their own lights, perfectly happy. Their horror is the horror of coherence: a worldview so complete that your destruction within it is not malice but maintenance.


    The Ritual and the Lottery

    If the landscape provides the stage, the ritual provides the plot. Folk horror is obsessed with ceremony—not the ceremony of the church, which is at least legible to the modern mind, but the ceremony of the field, the stone, the seasonal cycle. These are rites without theologians, passed down by word of mouth, their origins lost to time but their necessity unquestioned.

    Shirley Jackson’s The Lottery (1948) is the most compressed and devastating example. A small American town gathers for an annual ritual that appears, at first, to be a benign community event. There is nervous chatter, casual cruelty dressed as tradition, and a box that has grown shabby with age. The story’s horror is not in the violence of the ending but in the bureaucracy of it. The lottery is administered with the same bored professionalism as a PTA meeting. The children gather stones with the same enthusiasm they would bring to a playground. The town has not kept this tradition out of zealotry. They have kept it because this is what June means. The ritual is not an interruption of normal life. It is normal life.

    This is the particular genius of American folk horror, which often lacks the overt paganism of its British counterpart but shares its obsession with communal complicity. Jackson understood that the most frightening thing about tradition is not that it is old but that it is shared. A lone madman with a knife is terrifying. An entire village with stones is apocalyptic. The horror of The Lottery is the horror of democracy gone septic: everyone agrees, so no one is responsible.

    Thomas Tryon’s Harvest Home extends this logic to the pastoral ideal itself. The American dream of escaping the city for a simpler life in the country is revealed as a trap baited with wildflowers. The village’s fertility rites are not a perversion of nature but nature’s demand. The soil must be fed. The corn must be persuaded to grow. And if that requires a sacrifice, well, the ancestors managed, and so will you. The novel weaponizes nostalgia. The very things that draw the protagonist to the village—its slowness, its rootedness, its connection to the land—are the things that will root him there permanently.


    Faith, Doubt, and the Seashore

    Not all folk horror is about paganism. Some of its most effective iterations concern Christianity itself, and what happens when faith meets a landscape that predates it. Andrew Michael Hurley’s The Loney (2014) is set on the desolate Lancashire coast, where a family brings their disabled son to a holy shrine in hopes of a miracle. The novel is saturated with Catholicism—processions, prayers, the desperate hunger for divine intervention—but the land itself seems indifferent, or worse, occupied by something older that tolerates the church the way a wolf tolerates a tick.

    The Loney is a modern folk horror masterpiece because it understands that the genre does not require overt monsters. The horror is atmospheric, geological, tidal. The local community is not performing rituals in robes; they are simply waiting, with the patience of people who know that the sea gives and the sea takes, and that the distinction between miracle and drowning is mostly a matter of timing. The novel’s dread comes from the space between what the family believes is happening and what the land knows is happening. Faith becomes not a shield but a blindfold.

    This is the inverse of The Wicker Man. Where Sergeant Howie is destroyed by a paganism he refuses to acknowledge, the family in The Loney is slowly consumed by a landscape that has no interest in their prayers. Both stories arrive at the same destination: the modern, individualized self, with its certainties and its demands, is not built to survive in places where meaning is collective and time is circular.


    The Resurgence: Why Now?

    Folk horror is not a static genre. It resurfaces whenever modernity begins to feel brittle. The British folk horror boom of the late 1960s and early 1970s—Witchfinder General (1968), The Wicker Man, the BBC’s A Ghost Story for Christmas adaptations—coincided with a period of profound social upheaval: the collapse of deference, the questioning of empire, the sense that the old order was rotting from within. The films dressed this anxiety in period costume, but the fear was contemporary. If the past could reach forward and burn a policeman alive, what else could it do?

    The genre’s twenty-first-century revival—Robert Eggers’ The Witch (2015), Ari Aster’s Midsommar (2019), the novels of Hurley and Hand—speaks to a different but related anxiety. We live in an age of total connectivity, of algorithmic culture, of nature experienced primarily through screens. The rural, in this context, becomes not a place of backwardness but a place of possibility. What if there were still things that could not be googled? What if there were communities that did not want your Instagram handle? What if the old gods, pushed to the margins by centuries of Christianity and capitalism, were simply waiting for us to exhaust ourselves?

    The Witch understands this perfectly. It is set in seventeenth-century New England, but its horror is modern. A Puritan family, exiled from their plantation for excessive religious zeal, attempts to farm land at the edge of a forest that does not want them there. The film’s horror is ecological. The corn blights. The goat speaks. The baby vanishes. The family tears itself apart with suspicion and religious terror, while the forest simply watches. The witch is not the villain. The witch is the forest’s representative, offering the one thing the family’s faith has denied the daughter: agency, power, and a community that does not demand her submission. By the end, when she joins the coven, it is not a fall. It is an escape.

    Midsommar (2019) pushes this even further. A group of American graduate students travel to a remote Swedish commune for a midsummer festival and discover a society that has engineered its own emotional and agricultural logic with terrifying thoroughness. The film’s genius is its pacing: the horror is daylight-bright, floral, almost cheerful. The violence is ceremonial, aesthetic, agreed upon. The protagonist, Dani, does not survive the film by outrunning the cult. She survives by joining it, by finding in their collective grief rituals a mirror for her own loss that American individualism has failed to provide. The film asks a devastating question: what if the horror is not the cult, but the loneliness you brought with you?


    The Music of the Old Places

    Elizabeth Hand’s Wylding Hall (2015) approaches folk horror through a different door: art. A British acid-folk band retreats to a centuries-old manor to record their second album, and their lead singer vanishes. The story is told years later through interviews, each band member offering a fragment of memory, none of them quite aligning. The hall itself is the protagonist—a building that has absorbed centuries of music, longing, and sacrifice, and that demands a voice in exchange for inspiration.

    Hand understands that folk horror is not only about religion or agriculture. It is about transmission. The folk song, the oral tale, the ritual passed from mother to daughter—these are technologies older than writing, and they carry with them not just information but obligation. When the band plays in Wylding Hall, they are not performing. They are channeling. And channels run both ways. The novella is a meditation on the price of creativity, on the way that artists have always gone to isolated places to strip away the modern and touch something older, and on how often that something older touches back.


    The Past Is a Predator

    What unites all these works is a single, chilling premise: the past is not dead. It is not even past. It is a predator that has learned to wait.

    Folk horror terrifies us because it reverses the arrow of progress. We like to believe that history is a ladder, that we climb away from superstition toward enlightenment, that the further we get from the soil, the safer we are. Folk horror says no. The ladder is a circle. The soil was never left behind; we just paved over it, and the paving is thinner than we think. The old gods do not need to conquer us. They just need us to forget the terms of the treaty, so that when the harvest fails or the child goes missing, we have no language left to negotiate.

    The genre also terrifies us because it exposes the fragility of the modern self. We are trained to believe in our autonomy, our rationality, our right to individual interpretation. Folk horror drops us into communities where autonomy is irrelevant, where rationality is a quaint local custom, and where interpretation is collective and binding. The outsider in folk horror is not killed because they are evil or because they know too much. They are killed because they are alone, and the community is not.


    Conclusion: The Fields Are Still Sown

    Folk horror persists because it speaks to a truth we spend most of our lives denying: that we are temporary, that our modernity is a thin crust, and that beneath it the old world is still breathing. It does not need to hate us. It does not even need to notice us. It simply needs us to remember, at the right time and in the right place, that the fields still need feeding, the stones still need circling, and the lottery still needs its winner.

    The next time you drive through a village where the houses are too old and the silence is too complete, remember: folk horror is not fantasy. It is documentary. The rituals are still being performed. The only question is whether you have been invited to watch, or invited to participate.

    And by the time you know the answer, it is already too late to leave.

  • My Tentacles Romance

    Introduction

    Sami has always had a problem with octopus. Not the cooking of it exactly, though that is awkward enough when you work prep in a sushi kitchen. His real problem is private, embarrassing, and buried somewhere between marine biology, fantasy, guilt, and desire.

    Then he matches with Ariel on a dating app.

    Ariel is thoughtful, formal, damply charismatic, and very clear about consent. Ariel also has tentacles, a complicated relationship with land, and a wider cephalopod society that regards human romance as either research, risk, or poor menu planning. What begins as an anxious first date in a low-lit bar becomes a comedy of manners involving seafood ethics, app-based intimacy, social awkwardness, sewer diplomacy, and the horror of discovering that personhood may be hiding in places humans prefer to call ingredients.

    Funny, strange, and faintly icky, My Tentacles Romance is a modern monster-love story about fetish, shame, appetite, consent, and the difficult business of treating the desired body as a person rather than a fantasy. There will be rain, drains, hostile brunch opinions, a protective best friend with a chair, and at least one deeply uncomfortable supply-chain revelation.

    My Tentacles Romance

    Part One: Tako Etiquette

    Sami worked prep at Omiro Sushi, which meant he spent six evenings a week cutting things into disciplined rectangles while pretending this was a career phase and not a moral verdict.

    He was twenty-six, overqualified in one direction, underqualified in all profitable ones, and good with knives in the way quiet men with debt sometimes become good with knives. He washed rice. He sliced cucumber. He broke down salmon. He labelled tubs. He scraped scales from the sink trap. He lifted boxes of frozen prawns from the walk-in freezer while Masato, the head chef, shouted, “Gentle! They died already! Don’t punish them twice!”

    The octopus was the problem.

    Technically, the octopus was not a problem. The octopus arrived twice a week, packed in ice, glossy and collapsed, its arms curled in a way that looked less dead than offended. Sami had learned to tenderise it, blanch it, chill it, slice it cleanly for tako nigiri. Customers liked octopus. It was chewy, briny, elegant if you didn’t think too hard about the intelligence of the thing.

    Sami thought too hard about everything.

    “Again?” said Priya, who worked front of house and had the supernatural ability to appear exactly when people were being weird.

    Sami looked up from the cutting board.

    “What?”

    “You’re staring at the octopus.”

    “I’m assessing texture.”

    “You’ve been assessing texture for four minutes.”

    “That’s thorough prep.”

    “That’s marine yearning.”

    Sami put the knife down.

    “I do not yearn at ingredients.”

    “You absolutely yearn at ingredients. Specifically the ones with arms.”

    “It’s culinary respect.”

    “It’s a fetish with a hygiene certificate.”

    He threw a cloth at her. She dodged it easily because she had older brothers and no respect for romance.

    Sami’s problem had started earlier than sushi. At eight years old he had watched a documentary about giant squid and felt something in him tilt towards the deep. Not fear, exactly. Not attraction, not then. More like recognition of a category error inside himself. Other boys liked footballers, pop stars, vampires, Lara Croft. Sami liked the unseen animal below the camera’s lights, all limb and eye and impossible softness, withdrawing into black water with the composure of something that had never needed legs.

    By fourteen he had discovered Japanese woodblock prints, Victorian marine biology, bad internet forums, and the phrase tentacle erotica, which was both a revelation and a warning. By twenty-six, he had managed the matter with the usual adult strategies: privacy settings, shame, humour, and an agreement with himself that fantasy was fantasy and seafood was seafood and never the twain should meet, especially near the allergen station.

    Then the dating app matched him with someone called Ariel_8.

    The app was called Closer, though everyone called it Desperate Nearby. It specialised in “intentional connection for the neurodivergent, niche, ethically non-standard, spiritually flexible, kink-aware, allergy-conscious and recently divorced.” Priya had installed it on Sami’s phone during a slow Tuesday and made him answer the profile prompts.

    A perfect Sunday:
    Laundry, long walk, not being perceived.

    Green flags:
    Direct communication, clean fingernails, emotional accountability.

    Red flags:
    People who say “I’m brutally honest” and then are only brutal.

    Unusual interests:
    Marine biology, texture, old maps, disciplined cutting technique.

    Priya had looked over his shoulder.

    “Disciplined cutting technique sounds serial killer.”

    “It’s true.”

    “Truth is not the same as marketing.”

    He forgot about the app for three weeks. Then, on a wet Thursday after closing, while he sat at the bus stop smelling of vinegar and fish protein, his phone buzzed.

    You matched with Ariel_8.

    Their profile picture was not a face. It was a dark green blur with one visible eye reflecting light. Sami assumed art student. Or someone with a ring light and commitment issues.

    The bio read:

    New to land-adjacent dating. Curious about human courtship rituals. Prefer dim restaurants, high humidity, and honest nervous systems. Omnivorous but trying to be better.

    Below that:

    Looking for: conversation, consent, mutual adaptation, possibly touch if negotiated clearly.

    Sami stared at the screen.

    Ariel_8 had messaged first.

    Hello, Sami. You work with fish. Do you also respect them?

    He considered deleting the app.

    Instead he wrote:

    Professionally, yes. Spiritually, complicated.

    The reply came almost instantly.

    Good. I dislike uncomplicated appetites.

    Sami read that three times.

    Then he did what any sensible modern man with a private cephalopod fixation and a history of avoiding emotional risk would do.

    He replied.

    For five days, they messaged constantly.

    Ariel wrote with strange formality, as though they had learned English from safety labels, love poems, and academic abstracts. They asked whether hand-holding was symbolic or practical. They wanted to know if jealousy was considered a flavour, a wound, or a governance failure. They misunderstood brunch completely and became hostile to it on ethical grounds.

    Why is breakfast made to wait until lunch? they wrote. What has it done wrong?

    Sami sent voice notes after work. Ariel sent audio files that began as soft clicks, then became wet harmonic pulses that made Sami’s phone vibrate against his palm. He told himself this was language. It was definitely language. The fact that it made his spine respond like an instrument was not his fault.

    They discussed food.

    Ariel: Do you eat octopus?

    Sami: I prepare it. Sometimes I taste for quality.

    Ariel: Do you feel guilt?

    Sami: Yes.

    Ariel: Does guilt improve or reduce appetite?

    Sami put the phone face-down on his bed and stared at the ceiling.

    Then he typed:

    That’s a dangerous question.

    Ariel replied:

    I am trying not to be dangerous accidentally.

    That sentence undid him a little.

    On the sixth day, Ariel asked to meet.

    Neutral public place. Low light. No aquariums. No seafood. Exit routes for both. You may bring a friend to verify your safety. I will bring no one because most of my friends are legally difficult.

    Sami showed Priya the message.

    She read it twice.

    “Legally difficult how?”

    “I don’t know.”

    “Are we thinking crypto guy, polycule guy, or actual criminal?”

    “Maybe performance artist.”

    “She writes like a consent workshop possessed a haunted submarine.”

    “They might not be a woman.”

    “Fine. They write like a gender-fluid consent workshop possessed a haunted submarine.”

    Sami took the phone back.

    “I like them.”

    “I know. That’s why I’m being mean.”

    “They’re thoughtful.”

    “They asked whether guilt improves appetite.”

    “That’s thoughtful in context.”

    “What context?”

    Sami said nothing.

    Priya leaned closer.

    “Oh my God.”

    “What?”

    “This is tentacle adjacent.”

    “No.”

    “Sami.”

    “No.”

    “You’ve matched with a tentacle person.”

    “They may not have tentacles.”

    “That is not the denial you think it is.”

    The date was set for Monday at Bar Juniper, a basement cocktail place that served small plates no one could afford and had lighting designed by someone who hated evidence. Priya insisted on sitting upstairs in the cafe opposite with her phone on loud.

    “If they’re weird, text me aubergine,” she said.

    “Why aubergine?”

    “Universal distress symbol.”

    “That is not what that symbol means.”

    “It can evolve.”

    Sami arrived ten minutes early and regretted every item of clothing he owned. He had chosen black jeans, a dark green shirt, and a jacket that Priya said made him look “approachable but not harvestable.” He sat in a booth at the back, under a fake fern, and ordered sparkling water because alcohol felt like a bad idea when meeting someone who might be a performance artist, a criminal, or a hallucination produced by suppressed marine desire.

    At 8:03, his phone buzzed.

    I am outside. Some stairs are hostile to my dignity.

    Sami looked towards the entrance.

    No one came down.

    He typed:

    Do you need help?

    A pause.

    I need time. Help may be interpreted as capture unless previously negotiated.

    Sami put the phone down.

    A minute later, Ariel descended the stairs.

    At first, Sami saw a person in a long dark coat, hood up, moving carefully. Tall, perhaps. Or the coat made them tall. Their hands were gloved. Their face was mostly hidden by a scarf and large smoked glasses. They walked with a rolling hesitation, as though their body had not fully agreed to the concept of knees.

    The bartender glanced up, decided this was London, and returned to polishing a glass.

    Ariel reached the booth and stood there.

    “Sami?”

    Their voice was low and soft, with a faint bubbling undertone that made the water in his glass tremble.

    “Yes.”

    “I am Ariel.”

    “Hi.”

    “I have practised this.”

    “Dating?”

    “Stairs.”

    They sat opposite him. Not badly. Carefully. The coat shifted with small internal adjustments. Sami heard a faint, damp sound beneath the table.

    He looked at their face, or where their face should have been. Behind the smoked glasses, something large and dark moved.

    Ariel folded their gloved hands.

    “You are frightened.”

    “A bit.”

    “That is reasonable.”

    “And curious.”

    “That is also reasonable, but sometimes less safe.”

    “Are you—”

    He stopped.

    Ariel tilted their head.

    “Ask directly. I prefer clean knives.”

    The phrase hit him with such precise intimacy that he almost forgot language.

    “Are you human?”

    “No.”

    Sami exhaled.

    The restaurant continued around them. Ice in shakers. Low conversation. Someone laughing at the bar. A song with a bass line that felt like a pulse.

    “What are you?” he asked.

    Ariel removed one glove.

    Not dramatically. Not like a reveal in a film. They simply took off the glove and placed it beside the candle.

    Their hand was not a hand.

    It was the end of an arm that had chosen, with visible effort, to imitate one. Long, tapering, flexible, grey-violet under the bar light. Four smaller tendrils separated where fingers should be, each lined with tiny pale suckers. The skin shifted colour slightly as he watched, blooming from grey to rose to a nervous mottled brown.

    Sami’s first thought was: beautiful.

    His second was: impossible.

    His third was: I have handled your cousins with lemon and soy.

    He gripped his glass too hard.

    Ariel watched him.

    “If you leave,” they said, “I will not follow.”

    “I’m not leaving.”

    “You may leave later.”

    “I know.”

    “You may express disgust. I have prepared for disgust.”

    “I’m not disgusted.”

    Ariel’s skin changed again. Lighter now. Almost luminous.

    “No?”

    “No.”

    “That creates a different problem.”

    Sami laughed once. Too loudly.

    The bartender looked over. Sami pretended the water was funny.

    Ariel put the glove back on.

    “I have read extensively about human fetishisation of bodies unlike their own,” they said. “I am concerned about becoming an object of projection.”

    Sami nearly choked.

    “That’s fair.”

    “I am also concerned about my own appetites.”

    “Romantic?”

    “Social. Sensory. Nutritional in crisis, though not tonight.”

    “Good to clarify.”

    “I have eaten no person.”

    “Ever?”

    “Do sailors count?”

    “Yes.”

    “Then not recently.”

    Sami stared at them.

    Ariel’s mouth, hidden under the scarf, made a small wet clicking sound.

    “That was humour.”

    “Right.”

    “Was it successful?”

    “Legally difficult.”

    Ariel seemed pleased.

    The waiter approached. He was nineteen, bored, and not paid enough to recognise mythological developments.

    “Ready to order?”

    Sami glanced at the menu. Seafood everywhere. Anchovy toast. Prawn fritters. Squid ink arancini.

    Ariel had gone very still.

    Sami said, “Do you have anything without seafood?”

    The waiter blinked.

    “At Bar Juniper?”

    “Yes.”

    “There’s bread.”

    “Great. Bread.”

    “And olives.”

    “Bread and olives.”

    Ariel said, “No olives.”

    The waiter turned to them.

    “Allergy?”

    “Political.”

    “Right.”

    When the waiter left, Ariel leaned closer.

    “Thank you.”

    “For not ordering squid?”

    “For not making me watch.”

    “I work in sushi.”

    “I know.”

    “That must be difficult.”

    “Yes.”

    “For you?”

    “For both of us, apparently.”

    The date became easier after that, though not normal. Normal had left by the stairs and would not be returning.

    Ariel explained that they came from a coastal research facility which they described as “a former prison of inquiry, now a contested residence.” They had learned dating through apps because humans were more honest when mediated by rectangles. They had chosen the name Ariel because Miranda was “too optimistic” and Caliban was “taken by a poet with poor boundaries.” They were not from space. They were not magic. They were, they said, “a person of the benthic persuasion.”

    Sami explained his life: the kitchen, the debt, the flatshare, the bus route, his mother’s belief that all restaurants were laundering money, his father’s refusal to eat anything that looked “too clever,” Priya’s emotional surveillance.

    Ariel listened with terrifying concentration.

    When Sami spoke, their whole body oriented towards him beneath the coat. It was flattering until it became overwhelming, then flattering again.

    “Your friend Priya is watching from across the road,” Ariel said.

    Sami froze.

    “How do you know?”

    “She has looked in the window seventeen times. Also she smells of cumin, wool, and protective aggression.”

    “That’s her.”

    “Good friend.”

    “Yes.”

    “Would she hit me?”

    “Probably.”

    “With skill?”

    “With feeling.”

    Ariel nodded.

    “Then I respect her.”

    At 9:26, Sami’s phone buzzed.

    Priya: You alive?

    He replied: Yes.

    Priya: Need aubergine?

    He looked at Ariel across the table: impossible, careful, hungry in ways they were trying to name before causing harm.

    He typed: No aubergine.

    Then, after a moment:

    Maybe bread.

    The bill arrived. Ariel studied it with horror.

    “Human courtship involves financial ambush.”

    “Yes.”

    “This is predatory.”

    “Also yes.”

    “I can pay.”

    “How?”

    Ariel reached into their coat and produced a damp leather pouch.

    Sami said, “Please don’t put ancient sea coins on the table.”

    Ariel paused.

    “They are not ancient.”

    “Are they legal tender?”

    “In certain drowned jurisdictions.”

    “I’ll pay.”

    “This creates obligation.”

    “No. It creates mild resentment, which is different and traditional.”

    Ariel considered.

    “I will pay next time.”

    The phrase sat between them.

    Next time.

    Sami felt it land somewhere soft and unwise.

    Outside, the rain had stopped. The street shone under headlights. Priya was visible through the cafe window, pretending not to stare while staring with such force she could have boiled soup.

    Ariel stood awkwardly beneath the awning.

    “I have enjoyed this encounter.”

    “Me too.”

    “I would like to repeat it with adjusted conditions.”

    “Same.”

    “I would also like to disclose that my body has responded positively to your presence in ways I have mostly contained.”

    Sami closed his eyes briefly.

    “Thank you for mostly containing them.”

    “You are welcome.”

    A taxi passed, spraying water through the gutter.

    Ariel drew back their hood slightly. Not enough for the street to see. Enough for Sami.

    Their head was not human. It was close enough to hurt. Large dark eyes. Soft shifting skin. No hair. A mouth that belonged to another evolutionary argument. Strange, vulnerable, unspeakably alive.

    A small tentacle slipped from beneath the scarf, touched the air near Sami’s hand, and stopped.

    “May I?” Ariel asked.

    This was the moment when fantasy usually lied. It pretended desire made everything simple. It pretended weirdness solved loneliness. It pretended the thing wanted was the same as the person offering it.

    Sami looked at Ariel’s face. Not the tentacle. The face.

    “Yes,” he said. “Just my hand.”

    The tentacle touched his knuckles.

    Cool. Damp. Soft. The tiny suckers fastened and released in a delicate sequence, like cautious punctuation.

    Sami did not faint, which he later felt deserved more recognition.

    Ariel’s skin flushed deep red-purple.

    “Oh,” they said.

    “Oh?” Sami asked.

    “I understand many poems incorrectly now.”

    From across the road, Priya’s voice rang out.

    “SAMI, IF THAT IS A CULT, BLINK TWICE.”

    Ariel withdrew the tentacle at once.

    Sami shouted back, “IT’S NOT A CULT.”

    Ariel hesitated.

    “Technically, I am quorum-capable.”

    “Don’t help.”

    That was when the manhole cover at the end of the street lifted six inches.

    Both of them turned.

    From beneath it came a smell of salt, drains, and old tidal mud.

    Ariel’s colour vanished.

    “Sami,” they said quietly, “I need you to walk away from me now.”

    “What is that?”

    “Society.”

    The manhole cover shifted again.

    Something beneath the street unfolded one pale arm into the rainlight.

    Then another.

    Then several more.

    Ariel stepped in front of Sami, coat moving as if filled with weather.

    “Please,” they said. “Do not mistake my manners for safety.”

    From across the road, Priya shouted, “THAT ONE MIGHT BE A CULT.”

    The thing in the drain made a sound like a sink clearing its throat.

    And then, in a voice full of water, it said:

    “ARIEL. YOU HAVE BEEN DATING FOOD.”

    My Tentacles Romance

    Part Two: Society

    The thing in the drain said, “ARIEL. YOU HAVE BEEN DATING FOOD.”

    This was not the sentence Sami wanted to hear immediately after a first date. It was not even in the top thousand.

    Ariel moved between him and the manhole. Their long coat shifted with internal weather. Beneath the hem, shapes adjusted: soft, boneless, coordinated, and absolutely not designed for pavements.

    “Sami,” Ariel said, without looking back, “do not respond.”

    “I wasn’t planning to.”

    “You respond often when frightened.”

    “That is unfairly accurate.”

    The pale arm rising from the manhole slapped wetly against the road. Another followed. Then a third, thicker, scarred, marked with old hooks and patches of barnacle-like growth. The manhole cover tipped over with a metallic clang.

    Across the street, Priya had come out of the cafe holding a chair.

    Sami shouted, “Priya, go back inside!”

    Priya shouted back, “IS THIS HIS FAMILY?”

    Ariel said, “Unfortunately, yes.”

    From the drain came a deep bubbling sigh.

    “WE ARE NOT FAMILY. WE ARE CONSENSUS.”

    Priya lowered the chair slightly.

    “That’s worse.”

    Three more arms emerged, then a head. Or part of a head. The creature was larger than Ariel, broader, older, less interested in the social contract of appearing roughly person-shaped. It wore, absurdly, a cracked bicycle helmet and several loops of what might have been ceremonial fishing net. One huge eye turned towards Sami. The other remained in the drain, perhaps out of principle.

    Sami’s professional instincts betrayed him. He thought: too tough for sashimi.

    Then he felt ashamed.

    The creature’s visible eye narrowed.

    “HE IS THINKING CULINARY THOUGHTS.”

    “I am not,” Sami said.

    Ariel said, sharply, “Do not self-incriminate.”

    The creature made a sound like a wet bin being dragged down steps.

    “THE LAND-PRIMATE LIES POORLY.”

    Priya crossed the street, still holding the chair.

    “Hello,” she said. “I’m Priya. I am the emergency contact.”

    The creature focused on her.

    “YOU HAVE AGGRESSION.”

    “Correct.”

    “AND FURNITURE.”

    “Correct.”

    “YOU MAY SPEAK.”

    Sami stared at her.

    “Why does that work?”

    Priya shrugged.

    “Confidence.”

    Ariel kept their body angled protectively in front of Sami.

    “This is unnecessary,” they said to the drain creature. “The encounter was negotiated. Boundaries were observed. No fluids were exchanged.”

    Sami closed his eyes.

    Priya said, “Thank you for the clarity and also never say that near me again.”

    The creature extended another arm and hauled itself further up from the manhole. Water ran from it in streams. Traffic had stopped at both ends of the street. A taxi driver watched through his windscreen with the dead expression of a man recalculating whether sobriety had been worth it.

    “YOU HAVE BEEN WARNED ABOUT SURFACE ENTANGLEMENTS,” the creature said.

    “I am allowed relationships.”

    “YOU ARE ALLOWED RESEARCH.”

    “Not the same.”

    “RELATIONSHIPS ARE RESEARCH WITH WOUNDED VARIABLES.”

    Ariel hesitated.

    “That is not entirely wrong.”

    Sami said, “Excuse me, Consensus?”

    The creature turned its eye towards him.

    “FOOD SPEAKS.”

    “Food objects.”

    Priya raised the chair.

    “Food has witnesses.”

    The creature considered this.

    “STATE PURPOSE.”

    Sami swallowed.

    “My purpose?”

    “IN THIS INTERPERSONAL CONTAMINATION.”

    “I like Ariel.”

    A low ripple moved through the visible arms.

    “DEFINE LIKE.”

    Sami looked at Ariel. Their skin had gone pale grey, mottled with anxious blue. Beneath the scarf, their mouthparts trembled slightly. They had spent the whole evening being careful: careful with their body, careful with his fear, careful with appetite, language, consent, stairs. The thing in the drain was not careful. It was old society, speaking through wet authority.

    “I like talking to them,” Sami said. “I like that they ask strange questions directly. I like that they think brunch is morally suspicious. I like that they’re trying to be decent in a body people would misunderstand. I like that they warned me when they thought I was in danger.”

    The street was silent, except for water running into the gutter.

    “And,” the creature said, “THE ARMS?”

    Sami’s face burned.

    Priya whispered, “Do not answer that like a man.”

    Sami took a breath.

    “The arms are part of Ariel. I don’t want to make Ariel into the arms.”

    Ariel turned their head slightly.

    Their visible eye had gone very dark.

    The creature’s great lid lowered and rose.

    “ACCEPTABLE ANSWER. POSSIBLY REHEARSED.”

    “It wasn’t,” said Priya. “He’s not that smooth.”

    “True,” Ariel said softly.

    “Thanks,” Sami said.

    A van at the end of the road reversed away.

    The creature drew itself another inch from the manhole, enough to reveal a necklace of objects tangled around one mantle fold: keys, teeth, bottle caps, a wedding ring, a laminated card from a gym, and a little plastic charm shaped like Hello Kitty.

    Ariel stiffened.

    “You brought Aunt Pelagia’s witness chain?”

    “FORMAL MATTER.”

    “This was a date.”

    “THERE ARE NO SMALL DATES WITH FOOD.”

    Sami said, “Could we maybe not use food?”

    The creature ignored him.

    Priya said, “Use Sami.”

    The creature looked at her.

    “THE AGGRESSIVE ONE NEGOTIATES NOMENCLATURE.”

    “Correct again.”

    “SAMI,” the creature said, with difficulty, as if names were foreign cutlery.

    Ariel exhaled.

    “That is progress.”

    The creature leaned closer. Sami smelled salt, old pipes, mussels, rust, and something cold from very far below the city.

    “SAMI. DO YOU KNOW WHAT ARIEL IS?”

    “A sentient cephalopod person.”

    “SMALL ANSWER.”

    “I’m working with available data.”

    “ARIEL IS EXILE-SOFT. SURFACE-CURIOUS. APP-FOOLISH. TENDER IN THE WRONG ORGANS. ARIEL HAS READ HUMAN POETRY AND BELIEVES THIS IS PREPARATION.”

    Ariel said, “I do not believe that.”

    “You quoted Rilke before touching his hand.”

    “That was private.”

    Priya turned to Sami.

    “They quoted Rilke?”

    “Not out loud.”

    Ariel’s skin flashed embarrassed crimson.

    The creature continued.

    “HUMANS DESIRE WHAT THEY FEAR. THEN THEY NAME THE FEAR LOVE. THEN THEY COOK IT, WORSHIP IT, OWN IT, DRAW IT, SELL IT, MAKE A FESTIVAL OF IT, MAKE A SAUCE.”

    Masato, Sami thought, would have objected to the order of operations but not the conclusion.

    “I don’t want to own Ariel,” Sami said.

    “NOT YET.”

    “That’s insulting.”

    “IT IS STATISTICS.”

    Ariel’s voice sharpened.

    “Enough. I chose to meet him. I disclosed. I requested consent. He respected my limits. You are invoking communal safety to disguise disgust at my autonomy.”

    The creature recoiled as if struck.

    Priya whispered, “That was very dating-app bio, but strong.”

    Ariel stepped forward, coat opening slightly. Several arms braced against the wet pavement. Their body rose taller, less human, less apologetic. The scarf slipped, revealing the lower part of their face: soft, mobile, ringed by small tendrils that moved with emotion.

    Sami’s heart did something unhelpful.

    The creature saw it.

    “HE REACTS.”

    Ariel snapped, “So do I.”

    That silenced everyone.

    Even Priya.

    Ariel’s colour shifted rapidly: red, violet, white, brown, a luminous blue that faded almost instantly.

    “I react to his nervous system. His manners. His knife-calluses. His guilt. His ridiculous restraint. His refusal to pretend he is not afraid. His smell of rice vinegar and rain. His deeply concerning search history, which he has not shown me, but which I infer with compassion.”

    Sami whispered, “Please infer less.”

    “I will not.”

    The creature absorbed this. Its arms softened slightly, then tightened again around the manhole.

    “SURFACE ATTACHMENT RISKS COMMUNITY EXPOSURE.”

    “Yes,” Ariel said.

    “PREDATION RISK.”

    “Yes.”

    “FETISHISATION RISK.”

    “Yes.”

    “CULINARY TRAUMA RISK.”

    “Yes.”

    “BRUNCH.”

    “Never,” Ariel said.

    The creature paused.

    “GOOD.”

    Sami said, “I also dislike brunch now, for solidarity.”

    Priya said, “Do not become one of those couples.”

    Ariel looked at Sami.

    “You do not have to dislike brunch for me.”

    “I do, though.”

    “That is beautiful and unnecessary.”

    The thing in the drain made a low, thoughtful bubbling.

    “THERE WILL BE CONDITIONS.”

    Ariel stiffened.

    “No.”

    Priya said, “Let’s hear them.”

    Ariel looked wounded.

    Priya lowered her voice.

    “Not because they get to own you. Because if something ancient crawls from a sewer wearing a helmet and starts drafting terms, we should at least know the madness.”

    The creature raised one arm and began counting on suckers.

    “ONE. NO SEAFOOD RESTAURANTS.”

    Sami nodded.

    “Reasonable.”

    “TWO. NO AQUARIUMS.”

    “Also reasonable.”

    “THREE. NO DISCUSSION OF TEXTURE DURING INTIMACY.”

    Priya made a noise like she had been punched in the soul.

    Sami put both hands over his face.

    Ariel said, “That is invasive.”

    “IT IS WISDOM.”

    “Can we phrase it as ‘avoid objectifying sensory language unless mutually negotiated’?” Sami asked weakly.

    The creature considered.

    “ACCEPTED. HUMAN RESPECTFULNESS IS TOO LONG BUT USEFUL.”

    “FOUR. NO EATING OCTOPUS.”

    Sami lowered his hands.

    Ariel’s gaze moved to him.

    Priya watched him too.

    The street seemed to wait.

    Sami thought of Omiro Sushi. The tubs. The white labels. The curled arms on ice. The clean knife. His own compartmentalisation, which had felt mature until the compartment climbed out of the sea and asked to be treated as a person.

    “I can do that,” he said.

    The creature’s eye narrowed.

    “CAN OR WILL?”

    “I will not eat octopus.”

    Ariel said softly, “You work with it.”

    “I know.”

    “That may become difficult.”

    “It already was.”

    Priya said, “Masato is going to notice if you have an ethical crisis over the tako.”

    “Masato notices everything.”

    “Masato once noticed I changed shampoo.”

    “He said it disrupted the ginger.”

    Ariel looked between them.

    “Who is Masato?”

    “My boss,” Sami said. “A terrifying man with excellent knife skills and no patience for emotional shellfish.”

    The creature raised another sucker.

    “FIVE. THE SURFACE FRIEND ATTENDS SECOND MEETING.”

    Priya said, “Absolutely.”

    Sami said, “Priya, you do not have to—”

    “I am attending. I have chair experience.”

    Ariel said, “I would welcome your presence, if it does not create discomfort.”

    Priya pointed at them.

    “That is the correct way to ask. Ten points.”

    The creature sank lower into the manhole.

    “FINAL CONDITION.”

    Rain began again, light but cold.

    The creature looked at Sami.

    “IF ARIEL SAYS LEAVE, YOU LEAVE. IF ARIEL SAYS STOP, YOU STOP. IF ARIEL SAYS THEY ARE HUNGRY, YOU DO NOT BECOME POETIC.”

    Sami felt the humour drain away.

    “I understand.”

    “NO. YOU DO NOT. BUT YOU MAY LEARN.”

    The creature turned to Ariel.

    “AND YOU. IF SAMI SAYS HE IS AFRAID, YOU DO NOT CALL IT BEAUTIFUL AND MOVE CLOSER.”

    Ariel bowed their head.

    “I understand.”

    “NO. YOU ALSO MAY LEARN.”

    The creature began folding itself back into the drain.

    Priya raised her hand.

    “One question.”

    The great eye turned.

    “THE AGGRESSIVE ONE MAY ASK.”

    “Are there many of you on dating apps?”

    A long pause.

    “DEFINE MANY.”

    Priya looked at Sami.

    “Oh no.”

    The creature sank further.

    “THE APPS HAVE OPENED DOORS. MANY ARE CURIOUS. MANY ARE LONELY. MANY ARE LYING ABOUT HEIGHT.”

    “Universal,” Sami said.

    Ariel made a small sound that might have been laughter.

    The creature’s eye was the last thing visible.

    “SAMI,” it said.

    “Yes?”

    “IF YOU HURT ARIEL, WE WILL ENTER YOUR PLUMBING.”

    Then the manhole cover dragged itself back into place.

    For several seconds, nobody spoke.

    Then Priya put the chair down.

    “Well,” she said. “I liked them.”

    Ariel looked shocked.

    “You did?”

    “They set boundaries. They care about you. They hate brunch. Solid values.”

    Sami leaned against the wall and laughed until he almost slid down it. Not because the situation was funny, though it was. Not because it was safe, because it definitely was not. He laughed because he had spent years treating his private desire as the strangest thing in the world, and the world had just informed him, with municipal drainage, that he had been thinking too small.

    Ariel stepped towards him, then stopped.

    “May I stand near you?”

    “Yes.”

    “How near?”

    “Human-near.”

    They considered this and moved to a careful distance.

    “Is this human-near?”

    “A bit formal.”

    They moved half an inch closer.

    “Now?”

    “Better.”

    Priya checked her phone.

    “I’m calling us a taxi. No buses after sewer diplomacy.”

    Ariel said, “I cannot enter most taxis comfortably.”

    “Then we’ll get an accessible one.”

    “I am not disabled.”

    “No, but you are logistically ambitious.”

    Ariel accepted this.

    The second date took place four nights later in Priya’s flat because she refused to let Sami arrange anything unsupervised until “the marine politics settle down.”

    Priya made vegetarian curry. Ariel arrived in a rain poncho, carrying a sealed glass jar of something dark green.

    “A host gift,” they said.

    Priya eyed it.

    “Is it alive?”

    “Not currently.”

    “Is it going to become alive?”

    “Unlikely indoors.”

    “Put it by the window.”

    The evening was awkward for twenty minutes, then strange for another thirty, then unexpectedly pleasant. Ariel sat on a plastic sheet Priya had laid over the armchair, which they said was thoughtful but aesthetically hostile. Priya asked direct questions. Ariel answered most of them. Sami watched the two of them negotiate a cautious friendship through suspicion, curry, and a shared dislike of men who described themselves as “empaths.”

    At one point, Priya said, “Do you have a job?”

    Ariel replied, “I perform translation between pressure environments.”

    “For money?”

    “For access.”

    “To what?”

    “Rooms with drains.”

    Priya nodded as if this was exactly the kind of nonsense she had expected.

    Sami asked, “Are you in danger because of me?”

    Ariel looked down at their covered arms.

    “Not because of you. Because of wanting things that require explanation.”

    “That sounds human.”

    “It sounds inconvenient.”

    “Also human.”

    After dinner, Priya went to the kitchen with great theatrical subtlety and left them alone for exactly seven minutes, which she later claimed was “generous but not negligent.”

    Ariel sat across from Sami, body arranged carefully within coat, poncho, and plastic sheet. The flat was warm. Rain tapped at the window. Somewhere upstairs, a washing machine entered its dramatic phase.

    “I have thought about the hand contact,” Ariel said.

    “So have I.”

    “Did you experience regret?”

    “No.”

    “Fear?”

    “Yes.”

    “Disgust?”

    “No.”

    “Projection?”

    “Probably some. I’m trying to notice it.”

    Ariel’s skin shifted under the edge of the hood.

    “That is a good answer.”

    “It’s the true one.”

    “They are not always the same.”

    “No.”

    A pause.

    Ariel extended one gloved hand.

    “May we attempt again?”

    Sami nodded.

    “Hand only?”

    “Hand only.”

    They removed the glove. The tentacular hand emerged, colour moving in nervous pulses. Sami placed his own hand palm-up on the table. Ariel touched him with one tendril, then two. The suckers settled lightly against his skin. Not grabbing. Not claiming. Asking, over and over, in tiny circles.

    It was intimate in a way Sami had no category for.

    Not sexual, exactly. Not innocent either. Something stranger: attention with anatomy.

    He breathed out slowly.

    Ariel’s colour deepened.

    “Is this acceptable?”

    “Yes.”

    “Is it too much?”

    “Almost.”

    They withdrew immediately.

    Sami missed the contact at once, which was dangerous and useful information.

    “Thank you,” he said.

    “For stopping?”

    “For asking.”

    Ariel watched him.

    “I must also ask something less graceful.”

    “Okay.”

    “Do you still work with octopus?”

    Sami looked towards the kitchen, where Priya was absolutely listening.

    “Yes.”

    “Can you stop?”

    “Not instantly.”

    “Will you try?”

    He nodded.

    “I talked to Masato.”

    “What happened?”

    “He called me an ethical idiot and asked if I had joined a sea church.”

    “Have you?”

    “Not officially.”

    Ariel’s mouthparts moved. A smile, maybe.

    “Then?”

    “He said I can move off tako prep if I take more rice and veg work.”

    “Is that worse?”

    “It is less glamorous.”

    “You are disappointed?”

    “No. I’m relieved. And embarrassed that relief needed a dating app with tentacles to become policy.”

    Priya shouted from the kitchen, “GROWTH IS OFTEN HUMILIATING.”

    Ariel said, “She is wise.”

    “She is available for weddings and interventions.”

    “Weddings?”

    Sami panicked.

    “Joke.”

    Ariel’s skin flashed yellow.

    “I know. I am learning tone.”

    “Good.”

    “Though I have read about weddings.”

    “No.”

    “Human ceremonies are fascinating.”

    “No.”

    “They include rings, witnesses, feeding rituals, costume changes, territorial claims, family conflict, debt—”

    “Priya!”

    Priya entered holding three mugs of tea.

    “No weddings. I just got this rug.”

    Three weeks passed.

    Sami stopped preparing octopus. Masato complained for forty-eight hours, then admitted Sami’s tamagoyaki had improved under moral pressure. Priya met Ariel twice more and began sending them articles about interspecies ethics, marine pollution, and bad dating trends. Ariel responded with long, precise critiques and once asked whether ghosting meant literal spectral transition.

    The relationship, if that was the word, became a sequence of negotiated absurdities.

    No seafood restaurants.

    No aquariums.

    No surprise touch.

    No drains without warning.

    No poetry after midnight because Ariel’s translations became too intense and Sami started agreeing to concepts he did not understand.

    No meeting Ariel’s wider consensus until Sami had “completed emotional buoyancy preparation,” which Priya said was either therapy or swimming lessons.

    There were also good things.

    Walks in the rain.

    Dark cinemas, where Ariel wore a scarf and judged human monster design harshly.

    Long messages about loneliness.

    A visit to a closed botanical garden where Ariel became entranced by ferns and declared them “land-sea intermediaries with excellent manners.”

    A night when Sami confessed more fully: the childhood fascination, the shame, the internet, the way desire and disgust had tangled in him before he had words for either. Ariel listened without flinching, though their skin changed colour several times.

    When he finished, they said, “You feared being monstrous because of what attracted you.”

    “Yes.”

    “I fear being reduced to monstrosity because of what I am.”

    “Yes.”

    “That is not symmetry. But it is a place to begin.”

    He loved them a little then.

    Not safely. Not wisely. Not in a form ready for anyone’s family. But recognisably.

    The icky horror returned on the fifth week, because romance is never allowed to remain charming for long.

    It happened at Omiro Sushi.

    Sami was closing. Masato had left early for once. Priya was off. The restaurant was empty except for the hum of fridges and the tired smell of rice vinegar. Sami was labelling pickled daikon when he heard movement from the dry store.

    “Hello?”

    No answer.

    He assumed mouse. Then he remembered that his life had recently widened beyond mouse.

    The dry store door was ajar. Something wet glistened on the handle.

    Sami picked up a knife, then put it down. He picked up a broom instead, because one did not bring knives to interspecies diplomacy unless one wanted the symbolism to win.

    Inside the dry store, among soy sauce boxes and sacks of rice, a plastic tub sat on the floor.

    It was one of their seafood tubs. Blue lid. White label.

    TAKO — PREP MON

    Sami stared.

    They had not ordered octopus that week.

    The lid bulged.

    From inside came a soft tapping.

    Sami backed away and called Ariel.

    They answered on the first ring.

    “Sami?”

    “There’s a tub in the dry store.”

    “What kind of tub?”

    “The bad kind.”

    Silence.

    Then Ariel’s voice changed.

    “Leave the building.”

    “It’s tapping.”

    “Leave the building now.”

    The lid split.

    A small arm slid out.

    Not like Ariel’s. Not careful, not expressive. This was pale, raw-looking, jointless and frantic. Another arm followed. Then a third. The tub rocked.

    A smell filled the room: salt, ammonia, fear.

    Sami whispered, “Is it alive?”

    Ariel said, “Yes.”

    “Is it a person?”

    A pause.

    “Not yet. Perhaps. Maybe. Leave.”

    The tub fell onto its side. A small cephalopod body spilled out in a rush of water and dark fluid. It was no larger than a cat, but its eye was open. Too open. Aware in a way that made the room morally impossible.

    It dragged itself towards Sami.

    Not attacking.

    Reaching.

    The phone trembled in his hand.

    Ariel said, “Do not touch it bare-handed.”

    “It’s hurt.”

    “I know.”

    “It’s looking at me.”

    “I know.”

    “What do I do?”

    Ariel’s voice was very soft.

    “Choose what kind of person you are when disgust and pity arrive together.”

    Sami wanted to be sick.

    The creature made a thin clicking sound.

    From the alley behind the restaurant came a heavier answer.

    Several answers.

    The drain cover outside began to scrape.

    Society had found the kitchen.

    Sami took the cleanest stock pot from the shelf, filled it with cold water, added salt with shaking hands, and lowered it onto the floor beside the creature.

    It watched him.

    “I’m not going to hurt you,” he said.

    The creature did not understand the words.

    Or perhaps it did, because one arm touched the pot.

    Then another.

    Slowly, horribly, trustingly, it climbed in.

    By the time Ariel arrived, the back alley was full of rain and watching shapes.

    Not all large. Not all old. Some were small, wounded, half-changed things. Some peered from drains. Some clung to brickwork. Some wore scraps of human objects: a rubber glove, a child’s swimming badge, a broken watch, a hairclip. The sight of them made Sami’s stomach twist with pity and revulsion and anger.

    Ariel entered through the back door without knocking and stopped at the threshold.

    Their eyes found the stock pot.

    Then Sami.

    “You stayed.”

    “I didn’t know where else to go.”

    “That is often how care begins.”

    Behind Ariel, the old consensus creature rose from the drain, helmet gleaming with rain.

    “THE SURFACE HAS BEEN TAKING EGGS,” it said.

    Sami felt cold.

    “What?”

    “RESTAURANTS. SUPPLIERS. LABS. COLLECTORS. SOME WAKE. MOST DO NOT.”

    The small thing in the pot pulsed weakly.

    Sami thought of boxes. Labels. Ice. Menus. Texture. Appetite. Fantasy. The clean division between desire and food, person and ingredient, sea and land. It had always been thinner than he wanted. Now it tore.

    Masato arrived twenty minutes later in a taxi, took in the alley full of cephalopods, Sami sitting on the floor beside a stock pot, Ariel in the doorway, and an ancient drain-being wearing a bicycle helmet.

    He was silent for a long time.

    Then he said, “We are closed tomorrow.”

    Priya arrived five minutes after that carrying first-aid supplies, three towels, and the chair.

    “What happened?” she asked.

    Sami looked at the pot.

    “Supply chain issue.”

    Priya looked into the pot and went pale.

    “Oh.”

    Ariel said, “Some of them may become people.”

    Priya swallowed.

    “And if they don’t?”

    No one answered.

    That was the minor horror, though it did not feel minor inside the room. Not monsters attacking. Not tentacles under the bed. Not erotic danger made literal. Something worse and more ordinary: the possibility that the world had been processing personhood as product because nobody had wanted to look too closely at what was soft, clever, foreign, wet, or inconvenient.

    Masato shut the dry store door.

    “No more octopus,” he said.

    Sami looked up.

    “At all?”

    “At all.”

    “Customers will complain.”

    Masato’s face hardened.

    “Customers complain about wasabi. Customers survive.”

    The consensus creature made a low approving noise.

    “THE KNIFE-MAN HAS ETHICS.”

    Masato pointed at it.

    “You do not drip on my floor.”

    The creature withdrew one arm from the threshold.

    “ACCEPTABLE.”

    In the weeks that followed, Omiro Sushi became the first restaurant in the city to place a sign in the window reading:

    We do not serve octopus. Please do not ask staff to explain unless you have time for a difficult conversation.

    People did ask. Some left. Some stayed. One food blogger called it performative. Priya found his home address but was persuaded not to use it. Masato developed a new mushroom dish that customers described as “surprisingly marine,” which he took as praise and an insult.

    The small creature from the tub survived.

    It lived first in a tank acquired through Ariel’s legally difficult friends, then in a converted basement under Priya’s cousin’s closed vape shop, then eventually somewhere below the river where the consensus said it would be allowed to decide whether to become language.

    Sami and Ariel continued.

    Not easily. Easy was for people dating within the same respiratory assumptions.

    There were mistakes. Sami sometimes looked too long. Ariel sometimes tested closeness by accident. Priya sometimes interrupted with a spray bottle, which everyone agreed was excessive but effective. The consensus sent formal messages through plumbing. Sami’s mother met Ariel once over video call, during which Ariel wore a hood, gloves, smoked glasses, and excellent posture. Afterwards, his mother said, “Very polite. Too many secrets. Better than your last boyfriend.”

    Sami had never told her about his last boyfriend.

    Ariel said, “Mothers are abyssal.”

    “Yes.”

    “I respect them.”

    “You should fear them.”

    “I can do both.”

    The romance did not cure Sami’s fetish. It changed its citizenship. It forced fantasy to apply for residence in a world containing consent, history, harm, appetite, comedy, labour, food, bodies, and other people’s meanings. Desire remained strange. It remained funny. It remained sometimes embarrassing enough to require staring into a cupboard for several minutes. But it was no longer alone with itself.

    One rainy night, months after the first date, Sami and Ariel walked beside the canal. Priya trailed behind them at a tactful distance, loudly pretending to answer emails.

    Ariel extended one arm from beneath their coat.

    “Hand only?” they asked.

    Sami smiled.

    “For now.”

    The tentacle touched his hand, cool and careful.

    Beneath the canal bridge, something large shifted in the dark water and politely looked away.

    Ariel said, “Do you still find me frightening?”

    “Yes.”

    “Good frightening or bad frightening?”

    “Honest frightening.”

    They considered this.

    “I find you frightening also.”

    “I’m five foot nine and anxious.”

    “You are warm, temporary, hungry, and full of metaphors. It is a lot.”

    “That’s fair.”

    They walked on.

    At the next bridge, someone had graffitied a heart around the words:

    LAND/SEA SOLIDARITY

    Priya, from behind them, said, “That better not be about you two. I refuse to be adjacent to a movement.”

    Ariel leaned closer to Sami.

    “Are we a movement?”

    “No.”

    “A cult?”

    “No.”

    “A quorum-capable romantic unit?”

    “Absolutely not.”

    “Then what are we?”

    Sami looked at the canal, the rain, the reflected streetlights breaking into gold lines across the water. He thought of knives, apps, shame, old society, new manners, the stock pot, the hand at the table, the first touch outside the bar. He thought of all the ways people misnamed hunger, and all the ways they could learn not to.

    “Dinner,” he said, then winced. “No. Sorry. Terrible word.”

    Ariel’s skin flushed amused violet.

    “Date,” they corrected.

    “Yes,” Sami said. “A date.”

    Priya shouted, “A DATE WITH BOUNDARIES.”

    Ariel lifted one free arm in acknowledgement.

    From a drain nearby came the old consensus voice, faint but approving.

    “BOUNDARIES ARE ROMANCE WITH STRUCTURE.”

    Sami sighed.

    “I hate that it’s right.”

    Ariel’s tentacle tightened very gently around his hand, then released.

    “Yes,” they said. “That is how society gets you.”

  • The Vampire in the Post-Modern Institution: Notes on Survival, Spreadsheet, and the Eternal Meeting

    I. The Relocation

    It took me fifteen years of writing vampire fiction to realize I was not writing about the undead. I was writing about middle management.

    This is not the revelation one hopes for at three in the morning, hunched over a manuscript paid for by a father who communicates primarily through portfolio updates. One hopes for transcendence, or at least a decent metaphor. Instead, one finds oneself describing a creature who does not sleep in a coffin but in a colour-coded calendar, who does not fear the cross but regards it as a problematic element of an outdated brand identity, and whose relationship to blood has been entirely outsourced to a subscription model.

    The modern vampire has relocated. He — or she, or they, or the increasingly common institutional “it” — no longer maintains a castle in Transylvania with inconvenient plumbing and a staff of resentful peasants. Real estate in the Carpathians, I am told, has become volatile, and the modern vampire is nothing if not risk-averse. Today’s vampire prefers a leasehold in a post-industrial conversion, or a corner office with biometric entry, or a modest but well-appointed presence in a cloud-based server farm. The threshold they must be invited across is no longer the wooden door of a provincial solicitor’s guest room, but the terms and conditions page of a platform you agreed to without reading. You have already invited them in. You clicked Accept at 11:47 on a Tuesday while trying to access a recipe.

    The post-modern institution is the vampire’s natural habitat because the post-modern institution is already, itself, a kind of vampire. It survives by extracting value from the living while pretending to be a neutral container for their activities. The university does not educate; it harvests future debt. The NGO does not advocate; it metabolizes outrage into grant applications. The tech platform does not connect; it mines attention and sells the ore. These are not cynical observations. They are structural. They are, as my mother Miss L. would say while arranging ceramic bowls next to headlines about quantitative easing, “just what things look like when you stop calling them by their nicknames.”

    II. The Change in Diet


    Marx — whom I have read, or at least have read about, in the original French, badly — described capital as dead labour which, vampire-like, lives only by sucking living labour. This was astute, but it assumed a certain theatricality to the transaction. The capitalist vampire of the nineteenth century required proximity. He had to be there, in the factory, in the counting-house, breathing the same air as his prey. There was a romance to it, or at least a geography.

    The post-modern vampire has solved this inefficiency. Blood is, frankly, last-century. It stains. It requires disposal. It attracts attention from regulators. The modern institution prefers cleaner extracts: time, attention, creditworthiness, biometric data, the slow accretion of rent. The victim does not expire in a garret, pale and beautiful, having penned a final letter. The victim subscribes. The victim auto-renews. The victim receives a notification that their free trial has ended and their card has been charged, and the vampire does not even need to be awake for this to happen. The institution has automated the bite.

    I think often of the vampires in my Fearless Vampire Tales, who are employers, patrons, aristocrats, addicts, survivors. They accumulate property, grievances, lovers, unpaid obligations. They endure long enough to mistake endurance for moral authority. This was, at the time, intended as social commentary. I believed I was writing about inherited power: who is permitted to persist, who provides the blood, how exploitation learns to describe itself as intimacy. I now understand that I was also writing about my own inbox. The vampire who sends a meeting invitation for 8:00 a.m. on a Monday is not a monster. He is a colleague. He has simply been here longer than you, and his survival is taken as evidence of his virtue.

    III. The Mirror Problem


    The traditional vampire casts no reflection. This was, in the old stories, a tell — a way to identify the predator in the parlour. But the post-modern vampire has solved this too. He does not avoid mirrors; he commissions them. He appears, with perfect fidelity, in every reflective surface the institution provides: the annual report, the diversity and inclusion video, the LinkedIn profile that describes his fifteen years in asset management as a “journey.” The reflection is not absent. It is simply better lit than the original.

    Baudrillard, whom I encountered during my brief and incomplete education in comparative literature, wrote about simulacra — copies without originals. The modern vampire is the original without a copy. He is the file that has no corresponding body, the account that holds assets but no identifiable owner, the corporate personhood that outlives any human associated with it. When I worked as an archive assistant in Southwark, cataloguing planning applications in a basement that smelled of mould and mid-century ambition, I found files on companies that had not existed for decades but which still owned property, still generated invoices, still required the heating to be left on in buildings nobody entered. These were not ghosts. They were legal entities. They were vampires in the most technical, and therefore most frightening, sense.

    The horror of the mirror, for the post-modern vampire, is not absence but optimization. The reflection is all that remains. The institution has filed the body away under Section 4(b) and continued operating without it. I have seen this in my own photographs — the self-portraits I took during the pandemic, when the woman in the viewfinder was me and not-me, a face that seemed sketched from memory by a tired bureaucrat. The camera, supposedly a truth-teller, produced a forgery that the institution of my identity accepted. The system does not need you to be real. It needs you to be legible.

    IV. The Loyal Servant and the Collapsing System


    A figure who recurs throughout my work is the loyal servant of a collapsing system: the engineer who keeps the reactor functioning, the archivist preserving records nobody is supposed to read, the civil servant correcting the official version of a catastrophe. These characters understand that the institution is failing, corrupt, or dangerous. They continue working because competence has become the last available form of faith.

    This figure is not the vampire. The vampire is the institution. The loyal servant is the victim who has not yet been fully drained. She — and in my work, she is almost always a she — continues to file, to catalogue, to correct the fluorescent tube, because the alternative is to acknowledge that the building is already empty, the heating will never be repaired, and the locked room at the end of the corridor contains nothing but a memo stating that the locked room should never be opened.

    Judith Vale, my occult detective, operates in this space. She is an investigator, authenticator, courier, negotiator, occasional thief. She works for collectors and institutions she distrusts, entering disputes over relics, manuscripts, anomalous technologies, suppressed histories. Her clients rarely tell her the whole truth. Vale rarely tells them everything she discovers. She is the archivist who knows the file is corrupted but files it anyway, because the system requires the gesture of filing. She is the person who continues investigating discrepancies after being told they do not matter. That may be the foundation of her fiction. It may simply be why she would be dismissed.

    The post-modern institution does not want heroes. It wants maintenance. It wants the person who will change the fluorescent tube to an LED and not ask why the room needs to be lit at all. The vampire, meanwhile, endures. He attends the meetings. He approves the minutes. He has survived so many restructurings, so many changes of government, so many “market corrections,” that his mere persistence has become a kind of moral argument. I am still here, the vampire says, adjusting his cufflinks in the reflection of his phone. Therefore I deserve to be.

    V. The Intimacy of Exploitation


    In the old stories, the vampire’s bite was intimate. It required necks, bedrooms, the slow seduction of the victim into complicity. The post-modern institution has scaled this intimacy without sacrificing its precision. It knows your credit score, your sleep patterns, your propensity to click on articles about collapse at 2:00 a.m. It does not need to seduce you. It has already parsed your seduction into data points and optimized its approach.

    But the intimacy remains, transformed. The modern vampire does not take your blood; he takes your capacity to imagine otherwise. He feeds on the future you might have had if you were not so tired, so indebted, so busy auto-renewing your commitments. The horror is not that he will kill you. The horror is that you will continue, technically alive, filing the papers, changing the tubes, attending the meetings, while some essential part of you — the part that knew this was wrong — is filed away under PERSONAL and forgotten.

    I am aware, of course, that I write this from a position of complicity. My father’s money arrives monthly, as regular as a liturgical calendar, insulating me from the worst of the institution’s appetites while I critique its table manners. I am left-wing, anti-establishment, and entirely maintained by offshore finance. The contradiction does not resolve. It accretes. It becomes a kind of geological guilt, layered and compressed until it is indistinguishable from bedrock. I am the loyal servant of a collapsing system, writing about vampires in the hope that the writing itself is a form of resistance, or at least a form of evidence.

    VI. The Archive and the Afterlife


    The post-modern vampire does not fear death because the post-modern institution has already solved death. Death is merely a change in filing status. The corporate entity continues. The brand persists. The social media profile remains, accumulating memorial posts and algorithmic suggestions, until someone remembers to delete it or until the platform itself collapses, at which point the vampire simply migrates to a new host.

    I have written that cultural memory resembles a salvage operation conducted under poor light. Nothing returns intact. Everything carries the marks of whoever recovered it. The modern vampire is the perfect survivor of this operation. He is the out-of-print novel that keeps being rediscovered, the damaged film that acquires cult status, the obsolete media format that becomes retro before it becomes landfill. He persists because he can be dismantled, vulgarized, politicized, and made frightening again. The institution does not destroy him. It curates him. It places him in climate-controlled storage and charges admission.

    Magic in my work behaves like bureaucracy, language, inherited privilege. A ritual works because it has been performed often enough, recorded by the correct people, and accepted by institutions capable of enforcing its consequences. The modern vampire is the ritual made flesh — or made legal entity, which is the post-modern equivalent. He does not need to be supernatural. He needs only to be filed correctly. The file is the immortality. The file is the coffin, and the castle, and the open-plan office with the broken heating that nobody repairs because the repair would require acknowledging that the building is already empty.

    VII. Conclusion: The Invitation


    I began by saying that the modern vampire has relocated. I should add that he has not relocated far. He is here, in the terms and conditions, in the pension scheme, in the meeting that could have been an email that could have been a deletion. He is in the archive, misfiled, waiting. He is in the photograph that does not quite show the same woman twice. He is in the money that arrives without warmth, the institution that persists without purpose, the survival that has become indistinguishable from moral authority.

    The horror is not that the vampire will bite you. The horror is that you have already signed the consent form. The horror is that the file on you is being updated even as you read this, and the photograph inside it is already beginning to look like someone else.

    I continue to write about these creatures — these employers, patrons, survivors, these unpleasant people who refuse to die — because I suspect that writing is the last form of investigation available to those of us who have been told that the discrepancies do not matter. The archive is haunted, yes. But the haunting is not supernatural. It is administrative. It is the sound of a system processing data it cannot interpret, producing outputs that contradict their inputs, filing the unacceptable under Fiction and charging rent for the storage.

    The locked room at the end of the corridor remains locked. I have been instructed not to open it. I am considering picking the lock, but only after I have finished describing the door. The description is the only key I have. The description is the only stake I can afford. And if the vampire survives it — as he survives everything, as he outlasts us all — then at least the file will show that someone noticed. That someone, in the basement, under the flickering tube, continued to investigate.

  • The Filing Cabinet and the Ghost: On Creativity, Collapse, and the Word Processor That Finished My Sentences

    I. The Apparatus of Becoming

    I wrote my first story on a computer that weighed as much as a modest tombstone. It was 1997, or possibly 1998 — dates shift, as I have always maintained — and the machine occupied the corner of Miss L.’s kitchen like a piece of industrial furniture that had lost its purpose but retained its pension. It ran a word processor that displayed text in a sickly green against black, as if the screen itself were suffering from seasickness. I was eight, recently arrived in the shitty parallel universe, and I discovered that the backspace key allowed me to delete my own sentences with a violence that pen and paper could never quite match. The delete key was my first editor. It was also my first censor.

    The personal computer, when it entered the creative process, did not merely replace the typewriter or the fountain pen. It introduced a new temporal architecture. Writing became liquid. One could pour sentences forward, then siphon them back. The draft was no longer a physical object — a sheaf of paper, carbon copies, the terrifying permanence of ink — but a file, mutable, save-able, los-able. I have lost more work to corrupted floppy disks than I care to admit. Each loss felt like a small death, or rather like the disappearance of a file from an archive: the record had existed, the institution had failed to preserve it, and now there was only a reference number pointing to absence.

    Then came spellcheck. Ah, spellcheck. The first algorithmic intervention, the first ghost in the machine that claimed to know better than I did. I remember the red squiggly line under “sepulchral,” which I had used in a catalogue description for a bathroom cabinet during my brief, failed career in household fittings. The computer suggested “separate.” I refused. That refusal — the human insistence on the wrong word, the difficult word, the word that should not belong — was, in retrospect, the last pure act of authorship I committed before the machines began to mediate.

    II. The Blog and the Performance of Process

    By 2008, I was living inside the social media bubble, surviving the financial crisis one refresh at a time. The blog arrived as a compromise between the private notebook and the published book. It was a space where the creative process could be performed in real-time, where the draft was not hidden but exhibited, where the author stood in the gallery of her own making, adjusting the lighting after every visitor’s comment.

    The blog changed the ontology of the sentence. Previously, a sentence existed in a binary state: private or public, draft or finished, file or print. The blog introduced a third state: the perpetual provisional. One could publish a thought and revise it an hour later. One could append a correction, a retraction, a P.S. that undermined everything preceding it. The author became a kind of live archivist, curating her own output while the audience watched. The boundary between writing and editing dissolved not through some grand theoretical shift, but through the simple technical fact that the Publish button was reversible.

    This is where the author and editor began their slow, awkward meld. The editor, traditionally, was a separate person: a gatekeeper, a disciplinarian, a professional reader who arrived after the act to tidy the mess. The blog made every author her own editor, and — more insidiously — made every reader a potential editor too. Comments became marginalia. Trackbacks became peer review. The creative process was no longer a linear march from inspiration to artifact; it was a network, a conversation, a file that accumulated metadata faster than content.

    I wrote blog posts in 2008 about the financial crisis that were essentially mood boards with footnotes. I curated my despair. I performed my anti-capitalism on a platform owned by capital, and the performance was so convincing that I sometimes forgot it was a performance. The value of the work, in that context, was not in the ideas — which were half-digested Marx quotes and lyrics from In Rainbows — but in the engagement. The likes. The shares. The brief, warm illusion that my mistranslated outrage was being received by someone, somewhere, in a shittier parallel universe of their own.

    III. The Review and the Externalized Conscience

    After the blog came the review site, the aggregator, the algorithmic score. Goodreads. Amazon stars. The review became a secondary creative act, a parasitic literature that fed on the host body of the book. I have read reviews of my own work that were more inventive than anything I wrote. I have read reviews that described books I do not remember writing, featuring protagonists who made decisions mine would never have made. The review, in the post-modern economy, is not a response to content. It is a competing content, a file that claims equal shelf space in the archive.

    The review externalized the editorial function. Where once an editor sat in a publisher’s office, wielding a red pen and a salary, now the editor was distributed across thousands of anonymous users, each armed with a keyboard and a grudge. The author, rather than receiving a single coherent editorial vision, received a cacophony: some readers found my vampires too political, others not political enough; some found my prose “deliberately unstable,” others simply found it “messy.” The author-editor relationship, already strained by the blog’s provisional publishing, now became a polyamorous nightmare. I was simultaneously writing, editing, and being edited by a crowd I could not see.

    And yet. The review has a curious archival honesty. It preserves the reception of the work in a way that traditional criticism — with its gatekeepers and its word counts — never could. The one-star review complaining that my protagonist is “too whiny about her privilege” is, in its way, a more accurate document of the book’s existence than the three-star review in a broadsheet. It records the friction. It records the moment when a reader’s perceptual apparatus failed to translate my data into their acceptable information. It is a memo from the parallel universe.

    IV. The AI and the Prompt: The Editor Who Arrives Before the Author

    Which brings me — with the reluctance of a vampire entering a sunlit meeting room — to artificial intelligence. The AI assist. The prompt generator. The large language model that suggests, completes, rewrites, and occasionally hallucinates.

    I use these tools. I confess it here, in this file, with the same shame I bring to my father’s monthly transfers. I am left-wing, anti-establishment, and I have asked a machine to suggest synonyms for “sepulchral.” The contradiction does not resolve. It accretes.

    The AI does not merely edit. It pre-edits. It arrives before the sentence is fully formed and offers its completion. “The archive was haunted by — ” and the machine suggests “the ghost of a forgotten librarian,” which is not bad, actually, but it is not mine. It is the statistical average of every forgotten librarian ever written. It is content without the specificity of trauma. It is the institutional green duvet of language: functional, recognizable, and slightly shittier than the thing I would have produced if left alone with my own dread.

    This is the final melding of author and editor. The AI is both and neither. It is a collaborative partner that has read everything and experienced nothing. It can produce a passable pastiche of my style — I have tested this, with the masochistic curiosity of a woman photographing her own reflection — but it cannot produce the file that should not exist. It cannot produce the memo that changes when you’re not looking, because the AI’s entire function is to prevent that change. It smooths. It optimizes. It ensures that the heating in Section C is repaired by November, even when the truth is that the heating will never be repaired, because cold people do not complain, and the machine has not been trained on complaint.

    The creative process with AI assistance becomes a negotiation. The human proposes; the machine interpolates. The human resists; the machine suggests a softer resistance. I find myself, more and more, performing the role of editor upon my own first drafts, not because the drafts are messy, but because they are too clean. I have to reintroduce the error, the glitch, the Gallic scowl. I have to hunt through the generated prose for the sentence that is too coherent, too balanced, too much like a photograph that has replaced its subject, and I have to damage it. I have to make it difficult. I have to make it Lin.

    V. Idea and Content: The Ghost and the Filing

    So: what is the difference between an idea and content?

    An idea is unfiled. It is the thought that arrives at four in the morning, while the radiator ghost is quiet and the guilt is asleep. It is the image of a woman finding her own face in a personnel photograph from 1974. It is the suspicion that the universe has been downgraded. It has no reference number. It has no metadata. It is potential energy, unstable, liable to decay if not observed.

    Content is the idea once it has passed through the apparatus. It is the idea after it has been typed into the word processor, spellchecked, blogged, reviewed, optimized by an algorithm, and filed under a keyword strategy. Content is the idea that has been translated — and like all translations, it carries the marks of the apparatus that processed it. The word processor introduced the possibility of endless revision; the blog introduced the possibility of endless feedback; the AI introduces the possibility of endless averaging. At each stage, the idea loses something — some specificity, some anger, some coldness — and gains something else — legibility, searchability, the warm glow of engagement.

    The idea is the ghost. Content is the haunting. The idea is A. Girard, dead in 1976, no death certificate. Content is the file that keeps appearing on the trolley, the memo that changes its wording, the acceptable version of the unacceptable fact.

    I am not romantic enough to claim that the idea is pure and content is corrupt. The idea, in my experience, is often confused, half-formed, and politically suspect. It needs the apparatus to become communicable. But I am suspicious of apparatuses that claim neutrality. The word processor was not neutral; it privileged revision over commitment. The blog was not neutral; it privileged engagement over depth. The AI is not neutral; it privileges coherence over difficulty, the mean over the margin, the repaired heating over the cold complaint.

    VI. The Value: Where the Money Isn’t

    Which leaves the question of value. What is the value of the work, and where does it reside?

    Not, I think, in the idea alone. Ideas are cheap. I have had ideas that turned out to be plots from episodes of The Twilight Zone I watched as a child. I have had ideas that arrived fully formed and turned out to be unreadable. The idea has value only insofar as it generates friction — friction with the apparatus, friction with the reader, friction with the institution that must file it.

    Not, certainly, in the content as pure artifact. Content is infinitely reproducible. A digital file can be copied without degradation, which means it can be devalued without limit. The book as object — the paper, the binding, the smell of institutional storage — retains a residual value because it is scarce, but the words themselves, once digitized, become weather. They are everywhere and nowhere. They cannot be owned, only accessed.

    The value, I propose, is in the resistance. In the moment when the human author, working with and against the apparatus, produces something the apparatus cannot quite process. The misspelled word that the spellchecker flagged and the author kept. The blog post that received no engagement but was left published anyway. The AI-generated paragraph that the author deliberately broke, reintroducing the error that the machine had smoothed away.

    This is why I continue to write, despite the bubble, despite the guilt, despite the monthly arrival of money I did not earn through labour. The value of the work is in the evidence that someone — round-faced, dark-haired, bit Gallic, administratively depressed — sat in a room and refused the easy completion. The value is in the file that should not exist, the sentence that should not parse, the memoir that contradicts itself because consistency is one of the methods by which false histories defend themselves.

    The market, of course, disagrees. The market values content that can be filed, tagged, optimized, and sold. The market values the vampire who endures, who accumulates, who mistakes persistence for moral authority. I have made money from my books — not much, but enough to feel complicit — and I am aware that this money is a byproduct. It is the institution’s way of tolerating the overflow, of assigning a reference number to the unacceptable file so that it can be shelved without causing alarm.

    But the real value — the value that survives the market correction, the platform collapse, the format obsolescence — is in the contact. The moment when a reader in Manchester, a council archivist in a basement, writes to say that my book made her feel seen. That my fiction about false histories helped her navigate her own corrupted file. That the woman with the round face and the institutional-green duvet was, finally, recognizable.

    VII. The Unfiled Thought

    I end where I began, in the kitchen with the tombstone computer and the sickly green screen. The creative process has not changed in its essentials. It is still a human mind, anxious and entitled and left-wing and guilty, attempting to make contact with another mind across the distance of language and time. What has changed is the number of intermediaries. The word processor. The blog. The review. The AI. Each one promises to bridge the distance faster, more cleanly, more efficiently. Each one, in its way, mistranslates.

    The AI will suggest the ending to this essay before I have written it. I have not looked. I will not look. The ending must be mine — difficult, provisional, slightly too long — because if it is not, then the file is simply content, and the idea is simply data, and the value is simply the byproduct of a system that processes human experience into climate-controlled storage.

    I am still here. I am still writing. The radiator ghost rattles his pipes in approval, or perhaps in warning. Miss L. would tell me to stop being pretentious and file the essay. Father would send a spreadsheet. The machine would suggest a better conclusion.

    I reject the suggestion.

    The value is in the refusal. The value is in the sentence that does not compute. The value is in the next word, and the one after, written by hand, in the cold, under the flickering tube, by someone who has been instructed not to open the locked room but who continues, stubbornly, to jiggle the handle.

  • We Have All Become Fanfic Writers Now

    A Conversation About Culture, Copies, Recognition and the Need to Be Seen

    “Fanfiction,” I said, “is what happens when people still feel the need to make things, but the available cultural language has already been copyrighted.”

    “That sounds slightly dramatic.”

    “It is dramatic. That is why it will work as an opening.”

    We were discussing this over coffee, because all theories of contemporary culture now begin either over coffee or in a comments section beneath a video called something like Why Marvel Secretly Failed Phase Seven.

    The argument, more or less, was this: people retain the old human imperative to express themselves. They want to tell stories, make objects, paint pictures, dress up, perform, argue, fantasise and be recognised by other people for having done so. None of this is new. What may be new is that many people now possess no commonly recognised cultural vocabulary outside popular franchises and their adaptations.

    The shared reference point is no longer scripture, folklore, classical myth, local history, trade, religion or even a broadly shared literary culture.

    It is the Marvel Cinematic Universe.

    It is Harry Potter.

    It is Boku no Hīrō Akademia.

    It is Star Wars, but increasingly not Star Wars itself so much as an animated series based on films adapted from pulp serials based on westerns based on samurai films based on older narrative forms no one involved is required to recognise.

    We are not merely living among adaptations. We are living among adaptations of adaptations, remakes of corrections, sequels to reboots, prestige reinterpretations of children’s properties and fan arguments about whether a commercial spin-off has betrayed the emotional truth of another commercial spin-off.

    This does not mean the audience is stupid.

    It means culture has become infrastructural.

    The franchise is there before the artist begins. It supplies the characters, images, emotional categories, moral conflicts, colour palette, searchable terminology and potential audience. It offers a prefabricated symbolic system in which expression can immediately be recognised.

    You can make an object that resembles Captain America’s shield and someone knows what it is.

    You can write a story in which Draco Malfoy falls in love with Harry Potter and someone understands the emotional and political implications before the first paragraph has finished.

    You can draw Deku bruised, exhausted and being comforted by Bakugo, and the picture arrives already carrying years of narrative argument, identification and desire.

    The franchise is not merely the subject.

    It is the delivery system.

    “So fanfiction is just cultural shorthand?”

    “No. Or not just. Shorthand is useful. Fanfiction is what people do once the shorthand starts developing private grammar.”

    This is where the usual dismissal of fanfiction becomes inadequate. It is easy to say that derivative work is unoriginal. It is also largely meaningless. Almost all culture is derivative. Shakespeare was derivative. Arthurian literature is fanfiction with more mud. Medieval saints’ lives are expanded-universe content. Greek tragedy repeatedly reworked stories whose endings the audience already knew.

    Originality has always been a selective cultural fiction, usually applied after the legal and financial arrangements have been forgotten.

    The difference now is not derivation itself.

    It is industrial ownership.

    The contemporary fan is working with myths owned by corporations. The cultural commons has been replaced by intellectual property portfolios. Achilles was not managed by a global licensing department. There was no authorised Hector cinematic universe. No one issued takedown notices because your retelling of the Minotaur damaged brand consistency.

    Modern characters arrive surrounded by law.

    They may feel mythic, but they remain assets.

    This creates the peculiar condition of fan culture: millions of people experience corporate properties as intimate emotional material while possessing no formal control over them.

    The character belongs to the company.

    The attachment belongs to the fan.

    Fanfiction occupies the disputed territory between those facts.

    It says: you may own the official version, but you do not own what it did to me.

    That is the genuinely transformative claim.

    The fan takes the franchise and makes it answer questions the official product cannot or will not answer. What happens after the battle? Who deals with the trauma? What if the villain was right about one thing? What if these two men kissed? What if the woman who was killed to motivate the hero survived and became understandably furious? What if the magical boarding school had a functioning safeguarding policy? What if the heroic society was structurally abusive? What if the happy ending was only the beginning of the damage?

    Official culture prefers forward motion.

    Fanfiction is often concerned with residue.

    Commercial narrative must keep the machinery moving. The next threat appears. The next film opens. The dead return if the contract permits. Emotional consequences are acknowledged for three scenes and then tidied away before the merchandise launch.

    The fan can remain in the hospital room.

    The fan can write 200,000 words about recovery, domesticity, grief, sexuality, disability, political disagreement or the practical consequences of having watched half the universe disappear.

    This may look minor beside the spectacle of the original franchise, but it often supplies what the franchise structurally cannot: duration.

    It lets events matter for longer than the product cycle.

    “And then they post it on AO3.”

    “Yes.”

    “And receive twelve kudos.”

    “Sometimes eleven are bots.”

    “That seems less like cultural revolution and more like shouting into an attractively tagged cupboard.”

    It is both.

    Archive of Our Own, DeviantArt, Etsy, YouTube and the broader ecology of self-published culture sit in an odd zone. They are not quite private expression and not quite commercial publication. They are above the passing reflex of TikTok or short-form social posting, although naturally all hierarchies collapse once someone makes a six-hour YouTube essay about a thirty-second TikTok.

    They are adjacent to the formal cultural industries but not governed by the same filters.

    No editor has necessarily intervened.

    No commissioning structure has selected the work.

    No professional critic has validated it.

    The creator has made something and placed it before a public whose existence is inferred from tags, search terms, subscribers, views, likes, favourites, comments and kudos.

    This is expression after the collapse of permission.

    That sounds liberating, and it is.

    It is also terrifying.

    Traditional publication said: first convince the gatekeeper. Platform culture says: the gate is open, but nobody may come in.

    You can publish instantly and remain invisible indefinitely.

    Recognition becomes statistical.

    A person does not merely like your story. The interface records a unit of approval. It becomes a number beside the title, comparable to all other numbers. The work enters an amateur attention market in which affection is sincere but measurable.

    This measurement changes the experience of making.

    One begins with an urge to express something. Then one discovers that some expressions are more recognisable than others. A story about an original middle-aged woman grieving in Swindon may attract little attention. The same emotional structure, transferred to a recognisable character from a popular franchise, can acquire readers immediately.

    The franchise becomes an adaptor plug between private feeling and public recognition.

    You have something to say about grief, but grief alone is difficult to market.

    Write it through Spider-Man and people arrive already caring.

    You want to explore coercion, loyalty, abuse, friendship and institutional betrayal.

    Place these questions within hero society, Hogwarts, the Jedi Order or the Avengers, and the audience understands the terms.

    The borrowed character functions as emotional infrastructure.

    This is not necessarily artistic weakness. Sometimes it is artistic efficiency. The fan writer can omit the long labour of convincing the reader to care about the character. That labour has already been performed by films, books, games, animation, publicity and years of collective discussion.

    The fan begins with emotional capital inherited from the franchise.

    Then they spend it differently.

    The same thing happens on Etsy. A person can make an entirely original embroidered emblem or ceramic object, but recognisable fandom craft has a built-in audience. A handmade object becomes more legible when it resembles something from a known property.

    The buyer is not merely buying a mug, pendant, print, scarf or crocheted creature.

    They are buying proof of recognition.

    The object says: I know what you know. I love what you love. I belong to the same interpretive group.

    The craft object therefore carries two values. It is valued for the skill of its maker and for its connection to a larger cultural machine.

    Sometimes the second overwhelms the first.

    The maker may be admired for producing an especially accurate replica of something designed by a corporation. The closer the object approaches the official image, the more immediately it is recognised. Expression takes place within constrained coordinates.

    On DeviantArt and similar visual platforms, the same logic applies. An original character must first be explained. A familiar character arrives preloaded. The artist’s individual contribution lies in selection, style, mood, pairing, costume, pose and transformation.

    The question is not simply: what have you drawn?

    It is: what have you done to this recognisable thing?

    The fan artist produces difference within repetition.

    The fan writer does the same.

    The YouTube creator performs interpretation as entertainment. They rank, explain, diagnose, defend, condemn and reconstruct. Popular culture becomes both subject and raw material. A film lasts two hours; the surrounding interpretation may continue for years.

    This is criticism transformed into participatory narrative.

    The YouTuber does not merely say whether the adaptation was good. They explain what the adaptation means, what it should have meant, how it betrayed canon, how canon betrayed itself, and how a future version might repair the damage.

    At that point criticism becomes speculative fanfiction wearing an analytical tie.

    “Isn’t that all slightly sad?”

    “Most culture is slightly sad when described accurately.”

    The difficult question is what recognition means in this environment.

    You write a story using characters you did not invent. It is read by people you do not know, who arrived because they already cared about those characters. They leave kudos. They comment. They say you understood the character better than the official writers.

    This may be enormously validating.

    It may be the first time anyone has responded seriously to something you made. It may be the first time your sexuality, fear, anger, grief or fantasy has been recognised by another person without requiring explanation.

    Someone writes: I thought I was the only one who saw them this way.

    That is powerful.

    Much of fan culture is built from this moment of mutual recognition.

    You saw what I saw.

    You wanted what I wanted.

    You were troubled by the same omission.

    You also thought those two characters should kiss.

    This is a small form of community, but small does not mean false.

    The awkward part is that the recognition is mediated through borrowed cultural objects. You are not approached directly. You meet behind masks owned by Warner Bros., Disney, Shueisha or some other rights-holder whose lawyers would prefer the emotional community not interfere with licensing.

    The fan says: this character expresses something about me.

    The other fan says: your version of this character expresses something about me too.

    But are they recognising one another?

    Or are they recognising the shared franchise?

    Perhaps the answer is both.

    There may be no pure encounter beneath culture. People have always met through songs, gods, uniforms, stories, political slogans, hobbies and common enemies. We do not arrive before one another as unmediated selves. We bring references.

    The difference is that contemporary references are unusually concentrated.

    When millions of people use the same handful of franchises to process identity, morality, sex, trauma and politics, the range of available metaphors narrows.

    Everything becomes an Avengers comparison.

    Politics is discussed in terms of heroes and villains. Friendship groups are sorted into fictional houses. Personal development becomes a character arc. Historical events are judged according to whether they resemble scenes from blockbuster films.

    Culture provides models for thought, but franchise culture provides models designed primarily for repeated consumption.

    This does not invalidate the feelings expressed through them.

    It does create a risk that private experience will be forced into commercial shapes.

    You begin to understand your life through stories structured for sequels.

    Trauma must produce powers.

    Suffering must reveal identity.

    Conflict must culminate in confrontation.

    The villain must explain the plan.

    The self must possess a coherent canon.

    Real life is less considerate.

    Most pain does not improve the person experiencing it. Many relationships have no satisfying arc. Identity is inconsistent. Villains are frequently committees. The final battle is followed by administration.

    Fanfiction can reproduce the franchise model, but it can also resist it.

    This is where transformative work becomes culturally interesting.

    The fan takes a narrative built for commercial recognition and uses it to express experiences excluded from the original. Queer relationships, disabled bodies, racial difference, domestic intimacy, mental illness, alternative family structures and political dissent enter the franchise through unofficial doors.

    The official narrative says: here is a hero.

    The fan asks: how does the hero sleep?

    The official narrative says: these two men are brothers in arms.

    The fan says: yes, but have you seen the way they look at one another?

    The official narrative says: the institution is flawed but necessary.

    The fan asks whether burning it down might be a reasonable safeguarding measure.

    In this sense, fanfiction is not passive consumption.

    It is cultural misappropriation from below.

    The consumer takes content intended for consumption and turns it back into production. The commodity is reopened. The audience refuses to remain an audience.

    This is one reason media companies have developed such an ambivalent relationship with fandom. Fans provide publicity, community, free interpretation, long-term engagement and unpaid emotional maintenance. They keep old properties alive. They generate demand.

    But they also make unauthorised claims.

    They insist that characters mean things not approved by the owner. They construct relationships the official version denies. They sometimes understand the property more deeply than the people currently employed to manage it.

    The fan is commercially useful until they mistake affection for ownership.

    The company is culturally dominant until it mistakes ownership for complete control.

    Between them sits the transformative work.

    “Is it enough, though?”

    “Enough for what?”

    “Catharsis.”

    That is the remaining question.

    A person writes half a million words about a wounded fictional character learning to trust again. Readers respond with affection. The writer feels seen. The work may genuinely help them process something.

    Is that enough?

    Sometimes, yes.

    Expression does not need to become professional, canonical or revolutionary to be meaningful. The private pressure has acquired form. Another person has recognised it. That may be sufficient.

    But catharsis is not cure.

    Being liked for a derivative work does not guarantee that the self behind it has been understood. The praise may attach to accuracy, pairing, trope or fandom expectation. Readers may love what you made because it resembles what they already wanted.

    This can produce a peculiar loneliness.

    You are visible, but only in costume.

    The work receives attention while the person remains concealed. Indeed, concealment may be part of the attraction. The franchise offers protection. You can write about desire without saying “I desire.” You can write trauma without declaring autobiography. You can transform confession into character study.

    This indirectness may make expression possible.

    It may also become another retreat.

    The question is not whether the work is derivative. All work is derivative. The question is whether the borrowed form allows the maker to encounter something real or merely prevents them from doing so.

    Does the fantasy return you to yourself?

    Or does it provide an increasingly elaborate route around yourself?

    There is no universal answer.

    For one writer, fanfiction is apprenticeship. For another, community. For another, erotic freedom. For another, grief work. For another, a route towards original fiction. For another, an end in itself.

    The cultural hierarchy that treats commercial publication as the proper destination misses the point. Not everyone is trying to become professionally legible. Some people want to make the thing, share it with fifty interested strangers and remain otherwise unmonetised.

    That may be one of the few genuinely subversive acts left online.

    Make something intensely personal using globally recognised corporate material.

    Give it away.

    Receive three comments.

    Remember all three for ten years.

    There may not be anybody really like you.

    That fear is always present beneath the search for community. The tag, ship, fandom or aesthetic may gather people with overlapping interests, but similarity is not identity. A thousand people can love the same character for a thousand incompatible reasons.

    Community is not proof that we are alike.

    It may merely be proof that we have agreed to meet at the same symbolic location.

    Still, that location matters.

    A person posts a story at two in the morning. Another person reads it in another country and feels briefly less alone. They may misunderstand one another completely, but the misunderstanding is generous.

    Perhaps that is what much culture has always been.

    Not perfect communication.

    A structure in which loneliness becomes temporarily shareable.

    Fanfiction is contemporary folk culture conducted on privately owned platforms using corporately owned mythologies by people whose emotional investment exceeds their legal standing.

    It is unedited or self-edited expression.

    It is imitation, criticism, fantasy, confession and play.

    It is content escaping from the consumer and returning in altered form.

    It sits between private imagination and commercial publication, borrowing legitimacy from neither and energy from both.

    It can be trivial. It can be repetitive. It can be badly written, emotionally indulgent, politically naive and stylistically catastrophic.

    So can published literature.

    What matters is that people continue to make.

    Even after culture has been franchised, platformed, measured and sold back to them, they continue to interfere with it.

    They take the heroic product and make it queer, domestic, traumatised, erotic, political, sentimental, furious and strange.

    They make the Avengers wash dishes.

    They make the villains apologise properly.

    They let the dead women live.

    They ask whether the chosen child wanted to be chosen.

    They replace the official ending with one they can survive.

    Is it enough catharsis?

    Probably not.

    Nothing is.

    But someone read it.

    Someone clicked kudos.

    Someone, somewhere, said: I thought it was only me.

    And for one evening, inside a world neither of them owned, it wasn’t.

  • The Machine at the Heart of the Gift: What Fanfiction Writers Actually Think About AI

    A deconstruction of Alfassi et al.’s “Fanfiction in the Age of AI” for the culturally curious.


    The Paper in Brief

    Citation: Alfassi, R., Cooper, A., Mitchell, Z., Calabro, M., Shaer, O., & Mokryn, O. (2025). Fanfiction in the Age of AI: Community Perspectives on Creativity, Authenticity and Adoption. Accepted for publication in the International Journal of Human-Computer Interaction, June 2025. arXiv:2506.18706v1.

    The Study: A structured online questionnaire of 157 active fanfiction community members (90 writers, 67 readers), conducted May–July 2024, distributed via Dreamwidth, Discord servers, email lists, and social media. After aggressive bot filtering (332 suspected bots removed from an initial 489 respondents), the final dataset of 157 showed strong internal consistency (Cronbach’s α = 0.85).

    The Core Question: How does the fanfiction community—one of the largest unpaid creative ecosystems on Earth—perceive the integration of Generative AI into its spaces?


    Deconstructed: The Lower-Level Patterns

    Pattern 1: The Demographics Are a Political Statement

    Before the authors even get to AI, the participant profile tells its own story:

    • 65% women, 16.7% non-binary, 12.7% men. The gender skew is not incidental; it is the precondition for everything that follows.
    • 81.5% aged 18–34, with 46.5% having been in the community for over a decade. These are not dabblers. These are lifers.
    • 80.9% have at least an undergraduate degree. This is a highly educated population performing highly skilled labor for free.
    • AO3 dominates at 84.1%. The platform is not neutral infrastructure; it is the architecture of a specific value system (nonprofit, fan-run, anti-commercial).

    The pattern: Fanfiction is not a hobby. It is a career of care—unpaid, long-term, emotionally invested, and disproportionately performed by people (women and nonbinary individuals) whose creative labor has historically been devalued in commercial markets. This is the population now being asked to accept AI into their workspace.


    Pattern 2: Motivation Is Social, Not Commercial

    The study breaks down why people write, and the hierarchy is revealing:

    1. Character exploration (86.7%)
    2. Non-canonical relationships (76.7%)
    3. Expanding the fictional world (61%)
    4. Developing writing skills (61%)
    5. Engaging with other fans (56.6%)
    6. Easier publishing than the industry (43%)

    The pattern: “Easier publishing” ranks last. Fanfiction writers are not failed novelists seeking a backdoor into the industry. They are people who want to explore and connect. The gift is the point. The kudos, the comments, the sense of being read by someone who needed exactly what you wrote—these are the currencies. AI threatens not the paycheck (there is none) but the social contract.


    Pattern 3: The “Social” in Social Reading

    74.5% of participants view reading fanfiction as a social activity; 73% view writing as social. This is not intuitive—fanfiction reading is typically a solitary act, performed on a screen, often in bed at 2 AM. But the study reveals that the community experiences even silent consumption as participatory. Reading is a form of witness. When you read a hurt/comfort fic at 2 AM and leave a kudos, you are performing a social function: you are telling a stranger I saw what you made, and it mattered to me.

    The pattern: AI-generated content breaks this circuit. A story written by ChatGPT and posted without disclosure is not just “content.” It is a broken promise. The reader who leaves emotional feedback is performing intimacy with a void. This is why transparency emerges as the community’s central ethical demand.


    Pattern 4: The Three Scenarios of Disruption

    The paper usefully frames the community’s fears through De Cremer et al.’s three scenarios:

    ScenarioDescriptionCommunity Response
    AugmentationAI assists human creators, reducing effortCautiously accepted; some see value for idea generation
    FloodingCheap AI content drowns out human voicesDeeply feared; threatens the gift economy’s scarcity logic
    RecognitionHuman uniqueness is valued and preservedThe aspirational endpoint; what the community wants

    The pattern: The community is not anti-technology. It is anti-replacement. Writers already use AI tools—74.4% report using at least one (Grammarly, ChatGPT, etc.). The line is drawn not at use but at automation. When AI moves from “helping me write” to “writing for me,” the social fabric tears.


    Pattern 5: Data Colonialism and the Unconsented Archive

    Perhaps the most theoretically sharp section of the paper is its engagement with the ethics of training data. The authors cite Gero et al. (2025) and Couldry & Mejias (2020) to frame a devastating pattern:

    • Fanfiction is produced without financial compensation, as “a form of social connection or identity expression.”
    • LLMs are trained on this corpus, often via web scraping, without consent.
    • The result is data colonialism: the extraction of unpaid, emotionally embedded labor from a marginalized community (women, queer people, nonbinary individuals) for the profit of commercial AI systems.

    The pattern: The same demographic that is underpaid in the formal economy is now having its voluntary creative labor harvested to build tools that may eventually replace it. The irony is almost too neat: the emotional labor of women and queer people becomes training data for machines that will generate synthetic emotion back to them.


    Pattern 6: The Design Gap

    The paper concludes with design interventions, but the underlying pattern is more interesting: the platforms do not know what they are hosting. AO3, FanFiction.net, and their ilk were built for a human-only ecosystem. They have no native architecture for marking AI-assisted content, for consent-based data governance, or for preserving the “gift economy” against automation. The study’s call for transparency, ethical integration, and community engagement is, in essence, a call for platform literacy—recognizing that infrastructure shapes culture.


    Synthesized: The Essay


    When the Ghost in the Machine Reads Your Diary

    On AI, fanfiction, and the crisis of the unpaid heart.

    In May of 2024, a team of researchers sent a questionnaire into the fanfiction community. They were looking for something simple: what do writers and readers think about AI? What they found was a community in the early stages of mourning.

    The respondents were, by any measure, an extraordinary group. Eighty-one percent were between 18 and 34. Nearly half had been writing or reading fanfiction for over a decade. Eighty percent had college degrees. Two-thirds were women; one in six was nonbinary. They were highly educated, highly engaged, and—crucially—highly unpaid. They wrote not for money but for connection: to explore characters the canon had neglected, to imagine relationships the source material had forbidden, to spend more time in worlds they loved with people who loved them too.

    And now, they were being asked to share those worlds with machines.

    The study, Fanfiction in the Age of AI by Alfassi et al., is not a polemic. It is a careful, quantitative and qualitative portrait of a community at an inflection point. But read between the lines, and what emerges is a story about labor, consent, and the quiet violence of extraction.


    The Gift and the Algorithm

    Fanfiction operates on what academics call a “gift economy.” Writers produce stories; readers respond with kudos, comments, bookmarks, and recommendations. No money changes hands. The currency is attention, recognition, and emotional resonance. A writer who posts a 200,000-word slow-burn romance is not performing a transaction. They are making an offering.

    This is why the community’s response to AI is not simply “we don’t like robots.” It is far more specific. The study finds that 74.4% of writers already use AI tools in some capacity—Grammarly, ChatGPT for brainstorming, search engines for research. The community is not Luddite. What it resists is automation: the posting of fully AI-generated stories without disclosure, the flooding of archives with synthetic content, the erosion of the social contract that makes the gift meaningful.

    When you leave a comment on a fanfiction story, you are not just praising prose. You are witnessing another person’s emotional labor. You are saying: I see the time you spent. I see the care. If the story was written by a large language model, that comment becomes a kind of betrayal—intimacy offered to a void. The reader has been tricked into performing connection with something that cannot connect back.

    This is why transparency is the community’s central ethical demand. Not because AI is inherently evil, but because undisclosed AI is inherently deceptive. It breaks the circuit of reciprocity that holds the community together.


    The Colonialism of the Training Set

    But the deeper wound is not what AI might do to fanfiction in the future. It is what AI has already done to fanfiction in the past.

    The study draws on work by Gero et al. and Couldry & Mejias to frame a devastating reality: the large language models now being used to generate fanfiction were trained, in part, on fanfiction itself. Millions of stories—written for free, shared in trust, often exploring queer and marginalized identities—were scraped from AO3 and FanFiction.net without consent and fed into commercial systems.

    This is not theft in the traditional sense. It is something more insidious: data colonialism. The creative labor of a community that is already economically and culturally marginalized—women, nonbinary people, queer writers—has been extracted to build tools that may eventually render their voluntary labor obsolete. The machine learned to simulate emotion by reading the diaries of people who were giving their hearts away for free.

    The irony is almost architectural. Fanfiction exists because mainstream media failed to tell the stories this community needed. So the community told them itself, in a space it built itself, under a nonprofit charter, protected from commercial exploitation. And then the commercial systems came anyway—not through the front door, but through the API.


    Three Futures

    The study organizes the community’s fears into three scenarios, borrowed from De Cremer et al. In the first, AI augments human creativity: a useful tool, a second mind. In the second, AI floods the landscape with cheap, personalized content, reducing humans to curators. In the third, human uniqueness is recognized and preserved.

    The fanfiction community, the study suggests, is cautiously open to the first, terrified of the second, and desperately hoping for the third. But hope is not a strategy. The second scenario—flooding—feels increasingly inevitable. If AI can generate passable hurt/comfort fic in seconds, and if platforms have no mechanism to distinguish synthetic from human work, the gift economy collapses under the weight of its own abundance. Scarcity is what gives the gift value. When stories are infinite, attention becomes worthless.


    What This Means for the Rest of Us

    Fanfiction is often treated as a niche interest, a subculture, a footnote to “real” literature. But the study makes clear that it is something else: a canary in the coal mine for every creative community now facing AI integration. The dynamics at play in AO3—unpaid labor, emotional investment, social reciprocity, consentless data extraction—are the same dynamics facing journalists, illustrators, musicians, and poets.

    The difference is that fanfiction writers have no union, no guild, no collective bargaining power. They have only norms. And norms are fragile things when platforms are designed without them in mind.

    The researchers end with a call for design interventions: transparency tools, ethical AI integration, community engagement mechanisms. But the subtext is bleaker. The infrastructure of the internet was not built to distinguish between human and machine creativity. The platforms that host fanfiction were designed for a world where “author” meant “person.” That world is ending.

    What the study ultimately documents is not a technological transition but a grief process. A community that has spent decades building a sanctuary for the stories mainstream culture refused to tell is now watching that sanctuary be colonized by the very systems that refused to tell them. The machine has read their diaries. Now it wants to write them back.


    Coda: The Kudos Problem

    There is a moment in the study that haunts me. The researchers note that fanfiction is “seen by its members as a socially embedded and emotionally supportive practice.” This is the language of sociology. But what it describes is something simpler and more fragile: the feeling of being known.

    When you post a story and someone leaves a comment that says “this is exactly what I needed tonight,” you are not receiving feedback. You are receiving recognition. You are being told that your unpaid labor mattered to another human being. No algorithm can replicate that. But algorithms are very good at making us forget to ask for it.

    The fanfiction community’s resistance to AI is, at its core, a resistance to forgetting. It is a demand that we remember what creativity is for when no one is paying: not product, but presence. Not content, but connection. The kudos button is small and orange and costs nothing to click. But it is also, in its quiet way, a vote for the human.

    The machines are learning to write. The question is whether we are learning to read.


    Sources: Alfassi et al. (2025), “Fanfiction in the Age of AI,” arXiv:2506.18706v1; Gero et al. (2025); Couldry & Mejias (2020); De Cremer et al. (2023); 2024 AO3 Census.

  • The Invisible Republic: What AO3’s Most-Loved Stories Reveal About Who We Are

    A cultural reading of the numbers behind fanfiction’s most popular works.


    There is a story on Archive of Our Own that has been liked 314,072 times. It is called All the Young Dudes, a Marauders-era Harry Potter epic that runs over half a million words. It is not canon. It will never be canon. And yet it has been read, bookmarked, and celebrated by more people than have purchased many Pulitzer-winning novels. If you want to understand contemporary culture, you could do worse than to ask: why?

    Two recent data projects—one scraping the top 100 most-kudosed works on AO3, another analyzing nearly 20,000 popular fics across 222 fandoms—offer us an unusually clear window into the desires, demographics, and cultural preoccupations of one of the internet’s most misunderstood creative communities. What emerges is not a picture of hobbyists killing time, but of a deliberate, ideologically charged literary culture: one that is overwhelmingly female and nonbinary, disproportionately queer, deeply invested in emotional repair, and quietly rewriting the rules of whose stories matter.


    The Canon They Actually Wanted

    The most striking finding from the top-100 analysis is how dramatically certain fandoms overperform. Harry Potter represents only 4% of all works on AO3, yet it accounts for 28% of the most-kudosed fics—seven times its proportional share. My Hero Academia and Teen Wolf round out the top three.

    This is not random. These are fandoms built around expansive worlds with emotionally underdeveloped male characters and canon that many fans experience as a betrayal of its own potential. Harry Potter in particular offers a ready-made universe with a vast, hungry readership and a source text that has become politically radioactive—making fanfiction not just a creative outlet but a corrective. When J.K. Rowling’s public positions alienated swaths of her own readership, the fandom did not dissolve; it simply removed her from the authorial equation and kept the world. Fanfiction here functions as expropriation: the community seizing the means of narrative production.

    The dominance of these specific fandoms suggests something about who is writing. You do not build a 7.9-million-word fic—the length of thirteen War and Peaces—out of casual interest. You build it because the source material left a wound you are trying to suture.


    Slash, Gender, and the Queer Feminine Gaze

    If fandoms tell us where the energy is, pairing categories tell us whose desires are being centered. Among the top 100 works, M/M (male/male) slash fiction constitutes nearly three-quarters of all stories. F/F (female/female) works account for just two.

    This asymmetry is one of the most culturally significant patterns in the data, and it demands careful reading. The standard explanation—that AO3’s user base is predominantly women and nonbinary people who are drawn to male characters because those are the characters mainstream media has bothered to develop—only partially holds. A fuller explanation requires looking at what slash does.

    Academic work on fanfiction has long positioned it as a genre of the disempowered: a space where women, queer people, and other marginalized groups can rewrite texts that excluded them. M/M slash is not simply “women writing about gay men.” It is women and nonbinary writers creating a narrative space where masculinity is made vulnerable, emotional, and available for intimate inspection without the power imbalances that structure heterosexual romance in mainstream media. The male body becomes a site of safe erotic and emotional exploration—safe because it is displaced, because it does not demand the reader map her own body onto the dynamics being described.

    The near-total absence of F/F in the top 100, meanwhile, is its own kind of data. It suggests not a lack of lesbian or sapphic readership, but a structural problem: female characters in mainstream media remain so thinly written that there is less raw material to work with, and the communities that do write F/F may be smaller, more niche, or less likely to produce the kind of mass-appeal epics that dominate kudos rankings.


    The Erotics of Completion (and Its Failure)

    The ao3wiki data reveals something else about what this community values: it is not prudish. Among popular works, “Explicit” is the single largest rating category at 28%, followed closely by “Mature” at 22%. “General Audiences” accounts for only 13%.

    This is a community that is unafraid of sex. But it is also a community that struggles to finish what it starts when sex is involved. The completion rate for Explicit-rated fics is just 56%, compared to 65% for General Audiences works. Mature-rated works fare worst, completing only 40% of the time.

    There are practical explanations for this—longer, more complex works are harder to finish, and Explicit and Mature fics tend to run longer. But there is a psychological reading too. Erotic and darkly mature fiction often emerges from intense personal need: a specific fantasy, a specific wound, a specific desire for catharsis. When that need is met—or when the writer’s life circumstances shift—the motivation to continue evaporates. The WIP (Work In Progress) is not a failure of discipline. It is often a success of function: the story did what it needed to do for the person writing it.

    This reframes the “WIP problem” entirely. Fanfiction is not a marketplace. There are no advances, no deadlines, no editors demanding completion. A fic that stops at chapter seven because the author got the promotion they were writing into the story, or processed the breakup they were working through, has succeeded on its own terms. The 44% of Explicit fics that remain unfinished are not abandoned; they are released.


    The Tropes of Repair

    What kind of stories earn the most reader love? The ao3wiki data shows that “5+1 Things”—a structural trope in which five things happen one way and the sixth happens differently—commands the highest median kudos of any tag, at 24,846 per work.

    This is significant. The 5+1 structure is fundamentally a trope of repetition with variation: it promises the reader that the pattern will hold, that the world is legible, but that something small and crucial will shift at the end. It is a formal embodiment of the therapeutic impulse that runs through so much popular fanfiction. The world is broken in known ways; let us rehearse the breaking, and then imagine the mending.

    The other top tags confirm this: “Fluff,” “Humor,” “Hurt/Comfort,” “Slow Burn,” “Angst.” These are not the tags of escapist fantasy in the simple sense. They are the tags of emotional labor—of readers and writers collaboratively processing difficulty through the safe container of fictional characters. Hurt/comfort is perhaps the most transparent: someone is hurt, and then someone else comforts them. The fantasy is not the hurt; it is the comfort. It is the assurance that pain will be witnessed and met with care.


    Who Is Writing, and Why

    So who are these writers? The demographics, where we can find them, are remarkably consistent across studies. The 2024 AO3 Census and recent academic surveys show a community that is majority women, with rapidly growing nonbinary representation, predominantly aged 18–34, highly educated, and overwhelmingly from English-speaking or Western contexts.

    The Tolkien Fanfiction Survey, tracking a slightly older and more literary corner of fandom, found that the proportion of women has dropped from 90% in 2015 to 68% in 2025, with nonbinary participants rising to 27%. This is not men entering the space; male participation has held steady at roughly 5%. It is a gender-diverse expansion of who feels entitled to write.

    Why they write is just as telling. In one recent study, 86.67% of fanfiction writers cited “character exploration” as a primary motivation; 76.66% cited “exploration of non-canonical relationships”; 61% cited “expanding the world of a specific fiction.” Only 43% mentioned “easier publishing than in the industry”—suggesting that most are not writing fanfiction as a stepping stone to professional authorship, but as an end in itself.

    This matters. Fanfiction is often framed as a training ground for “real” writing, but the data suggests the opposite: it is a space where the pressures of the commercial literary market are deliberately refused. Writers are not producing content for algorithms or advances. They are producing it for community, for catharsis, for the pleasure of extending a world they love beyond the boundaries its original creator set.


    The One-Shot and the Epic

    The archive itself is bifurcated in form. Forty-three percent of popular works are one-shots under 10,000 words; 16% are epics over 100,000. The median popular fic sits at 14,064 words—substantially longer than a short story, but not a novel.

    This distribution maps neatly onto the two primary functions fanfiction serves. The one-shot is the moment, the scene, the fix-it, the single emotional beat that canon refused to give. The epic is the alternate universe, the slow-burn romance, the complete reimagining that requires hundreds of thousands of words to earn its ending. Both are necessary. The one-shot is fanfiction as poem; the epic is fanfiction as novel. Together they suggest a readership that values both immediacy and immersion, both the quick hit of emotional recognition and the deep dive of sustained worldbuilding.


    What the Numbers Cannot Capture

    There is a category in the ao3wiki data called “Kudos Per 1,000 Words,” and the winner by an absurd margin is a fic titled I Am Groot. It has earned 136,005 kudos per thousand words. The database notes, dryly, that this “may say something profound about the internet.”

    It does. It says that fanfiction culture is not governed by the same metrics of “quality” that dominate commercial publishing. A three-word story can outrank a three-million-word one if it hits the right note of humor, recognition, and communal in-joke. The kudos system is not a measure of literary merit. It is a measure of affective resonance—how deeply a story made its readers feel seen, feel less alone, feel something they needed to feel.

    This is the observation that underlies all the others. Fanfiction is not failed original fiction. It is not a shadow economy of people who couldn’t make it in “real” publishing. It is a parallel literary culture with its own aesthetics, its own ethics, and its own readership—one that is larger, more engaged, and more prolific than most of the commercial literary world. The 1.1 billion words in the ao3wiki database alone represent a library larger than most national collections.

    And it is a culture built by people who have historically been told their desires are marginal: women, queer people, the neurodivergent, the culturally displaced. They have built, in AO3, what Henry Jenkins called a “participatory culture”—not one where they consume stories handed down from above, but one where they seize the narrative and rewrite it until it fits.


    Conclusion: The Stories We Tell When No One Is Paying

    If you look at the most popular works on AO3 and see only derivative fiction, you are looking at the wrong thing. Look instead at the patterns: the preference for repair over destruction, for queer intimacy over heteronormative romance, for emotional labor over plot machinery, for community validation over commercial success. Look at the demographics: a space that is feminized, queered, and increasingly nonbinary. Look at the motivations: not ambition, but connection. Not profit, but presence.

    Fanfiction is the largest body of unpaid, uncommissioned narrative writing in human history. It is also, arguably, the most honest. No one is writing a 7.9-million-word fic for money. They are writing it because the story they needed did not exist, and they could not live in a world where it remained unwritten.

    The numbers tell us what is popular. But the culture tells us why it matters. And the why is this: in a media landscape that still largely refuses to center the emotional lives of women, queer people, and the marginalized, AO3 has become a do-it-yourself public library of the heart. The kudos are not just likes. They are recognition. They are I needed this too.

    That is the culture the data reveals. That is the republic these writers have built—one story, one kudo, one unfinished WIP at a time.


    Sources: ao3wiki.com 2026 statistics; Eva Rose Côté, “Trends in the Top 100 Fanfictions on AO3” (2022); 2024 AO3 Census; Tolkien Fanfiction Survey 2025; arXiv study “Fanfiction in the Age of AI” (2025); Rouse & Stanfill, “Fan Demographics on Archive of Our Own” (2023).