The Palace

» see thepalace.com as it lived, on the wayback machine

~ the obit ~

the palace was a graphical chat platform launched in november 1995 by time warner interactive. the core idea was that text chat could be more interesting if it had a visual stage. you joined a "palace" (a server with a set of themed rooms). you picked or made a "prop" (a small 2D avatar). you walked around the rooms. when you typed, your message appeared as a comic-strip speech bubble floating above your prop. other users in the same room saw your bubble appear in real time.

i never used the palace. by the time i got online in late 1998, mIRC was the chat tool everyone in turkey used, and the visual-chat layer never had reach here. but the palace shows up in any history of pre-web visual interfaces, and a small dedicated community is still using it in 2026 on hobbyist-run servers.

time warner interactive sold the product to a spin-out company called communiternet (later renamed communities.com) in 1996. communities.com ran it as the main commercial palace operator for several years. the platform kept going through the late 1990s with a real but small user base. communities.com ran out of money around 2001 and the official commercial palace network shut down.

the server software was eventually open-sourced or reverse-engineered, depending on which fork you look at. small operators (the running enthusiast count is in the dozens, not thousands) still host palace servers today. owners can still log in. the original commercial network and most of the rooms it hosted are long gone.

~ the rap sheet ~

~ how it actually worked ~

the user side was a custom client (windows, mac, and a brief linux build later). you launched it, you typed in a server address (a particular palace), the client connected, you got dropped into a room. each room had a painted background image (a beach scene, a bar, a castle hall, whatever the palace operator had built). other users showed up as small bitmap avatars on top of the background.

chat was text typed into a small box. when you hit enter, your text appeared as a comic-style speech bubble above your prop, visible to everyone else in the same room. older bubbles faded over a few seconds. private messages were possible but the public conversation in the room was the main channel.

your prop was customizable. the basic option was a "smiley" face you could colorize. advanced users designed custom props (custom-drawn 32x32 bitmaps with transparency) and saved them as personal collections. some palaces had elaborate prop economies where members would trade animated props they had drawn. others restricted props to a default set.

~ the palace community shape ~

each individual palace was its own community. you would have your favorite palaces. the most famous early palaces were the welcome palace (run by the company), various themed palaces (medieval, sci-fi, fan communities for specific shows or bands), and adult-themed palaces. each operator set their own moderation rules, their own prop policies, their own room layouts.

the social shape was different from IRC. on IRC the conversation was the main thing. on the palace the conversation was happening in a place. the place mattered. you would log in and see who was hanging out at the bar, then go to the chess room to see who was up for a game, then visit a friend's custom palace to see what new room they had built. the spatial metaphor produced different social patterns.

this is also what made the palace feel like a precursor to second life and to modern VR-chat platforms. the basic idea (you are a small avatar in a graphical room with other small avatars) was working in 1996. the difference is that the palace was 2D and committed to text chat as the main communication channel. second life went 3D and added voice. VR went stereoscopic. but the social shape was already there.

~ how it died ~

two things killed the commercial palace. the dotcom crash and the web. communities.com had been raising money throughout the late 1990s. when the funding environment collapsed in 2000-2001, the company could not raise more. the user base was real but small, and the commercial platform never converted to a sustainable business model.

the web also kept eating chat. in the mid-1990s the palace's graphical interface was a real differentiator over IRC and AIM. by 2000 the web had its own chat tools (java applet chats, basic web messengers, msn web client). the palace's custom client started looking like an extra step. younger users went to AIM and yahoo messenger because their friends were already there.

communities.com formally closed around 2001. the commercial palace network went offline. existing palaces had to migrate to alternative server software (an open-source variant called openpalace, plus several commercial-but-cheap forks). the official servers and the official client distribution stopped. the platform did not die suddenly, it just shrank into a hobbyist size.

~ what is still there ~

several fan-run palace servers still exist in 2026. the active ones tend to be old-timer communities, often with members who have been on the same palace since the late 1990s. you can still download a palace client (modern builds of openpalace work on current operating systems). you can still log into a palace and see other small avatars walking around.

the openpalace project keeps the protocol alive. it is not actively under heavy development but it is maintained well enough to run. some operators charge small monthly fees to support hosting. others run their palaces for free as personal projects. the total ecosystem in 2026 is small, maybe a few hundred active users at peak times across all servers.

the cultural memory is what the people who used it carry forward. anyone who hung out at a palace in 1997 to 2000 remembers the specific feel of it. the painted backgrounds, the slightly-jerky avatar movement, the speech bubbles, the friend you only knew as a custom prop they had drawn. that texture is gone from modern messaging. the palace had it. the people who were there know what it was.

@}-->--

« previous  ·  random  ·  next »