"The Automobile Mystique and the Asphalt Nightmare" - Paolo Soleri

#Architecture #Arcology #Cars

#ARCHITEKTON - ARCOLOGIES: ces villes utopiques qui devaient sauver la planète

L'étalement urbain est le grand problème de nos villes modernes, causant la destruction des paysages et de la nature. Et si la solution urbaine ultime existait déjà ? Une ville compacte, écologique, autosuffisante, et même… capable de faire évoluer l’humanité. Cette utopie a un nom : l’ #arcologie.

https://www.youtube.com/watch?v=3laSbTm54_g

#architecture #architecte #vulgarisation #art #construction #arcology #paolosoleri #arcosanti

#CaptainRoysRustyRocketRadioShow: THE #UK #Geek #ScienceFiction, #Fantasy, and #Horror #Podcast

#Whovians, time for another #revisit of #ClassicDoctorWho!

#CRRRRS 593 #DoctorWho: #ParadiseTowers

Listen: https://archive.org/download/roymathurspodcast/2025-08-29-captain-roys-rusty-rocket-radio-show.mp3

Subscribe: https://roymathur.com/podcast.html

Even more #OldWho and #NewWho here: https://www.google.com/search?&q=site:roymathur.com%20Doctor%20Who

#Cult #Beeb #SFFH #TV #Pex #Kroagnon #RichardBriers #SylvesterMcCoy #BonnieLangford #Cannibals #Arcology #Dystopia #UrbanDecay

1973 Short Film Arcology: City in the Image of Man.

https://slrpnk.net/post/25144826

Ah, the beautiful potential and cautionary tale of arcologies. I could flip through the images of Soleri for hours. Hello Future Me does a nice, bite-sized overview of the artist, architect and urban planner coined the term and refined the concept. More information in replies.

https://www.youtube.com/watch?v=4_FMiHUvtBM

#arcology #architecture #solarpunk #cyberpunk

Mistigram: a vignette of a do(o)med arcology, “Everything’s Fine In Here” is a specimen of #TypewriterArt from the desk of @lordnkon that raises a lot of questions seemingly answered by its title. (What’s up with the dome? What’s with the apparently smoldering rubble comprising roughly two thirds of your dome’s contents? Blink twice if you need help!) This piece was included in last month’s science fiction-themed MIST0524 artpack collection.

https://mistfunk.wordpress.com/2024/06/09/mist0524-ldn-everythingsfineinhere/

#arcology #dome #LordNikon #MIST0524 #typewriterArt #typewriterart

A few weeks ago I wrote an ArroyoAtomHandler which would go over each element to generate a page, sort of like the built-in org exporters or my Arroyo HTML exporter. It was bodgy as hell, and I probably could have done a better job at it, but it was just too easy to get confused in working between the Atom and the HTML exporter, and I just didn't like it.

So yesterday I took The Arroyo HTML exporter and gave it the ability to only export a few headings, based on an allowlist of IDs passed in to it.

I also extended the system to cache the contents of Headings' PROPERTIES drawers, in both The Parser Heading Type, and the Arcology Org-Roam Caching Models which can drive other behaviors. I've given the Arcology the same metadata-query powers for Headings which it already has for Pages. This allows me to, at minimum, capture the publish date of any Heading in my system and then query those. The Arcology captures these dates, converts them in to DateTime objects which can then be used to group and order posts, do time-bound queries, and the like, and this can be extended to other metadata stored on the Headings.

Combining these two things together lets the Arcology populate feeds from anywhere in my notebooks as in the Atom Feed Handler. This code design is way more reasonable to deal with and more flexible than the ArroyoAtomHandler was.

So soon I can microblog from my org-mode journal and knowledge system by generating private, topic-specific Atom feeds which automatically cross-post to my Fediverse profiles via Feediverse or a built-in implementation. I can confidently generate a private journal feed that doesn’t have an HTML-page counterpart, it’s just an atom feed of a selection of my org-mode system work1.

I'm pretty close to having this in a position where it can be deployed. I think largely the behavior and features won't change except for some small design cues, but it's not quite feature complete yet. I laid out a Rough Timeline and Task List on the Arcology's repo which will spell out a "1.0".

I've been planning in earnest to ship a "1.0" version of the Arcology publishing platform and the Complete Computer dynamic declarative environment this year. Part of that is re-structuring all these components so that the Arcology and the Complete Computer can be more piece-meal assemblies that others could adopt without pulling in all of my frankly inane software preferences. As part of that, I want to produce a series of video tutorials as a set of documentation, which I have been calling Rebuild of The Complete Computer. I don't have much to share yet on that front, but a plan is coming together.

The Rebuild of the Complete Computer series will be a semi-scripted stream series where I sell and document the org-mode publishing, computing, and productivity suite I’ve developed for myself and my community.

The current design of these sites is fine, but the way I differentiate the sites using certain emoji for each domain makes the site a bit too busy for my taste. I will not stop using Vulf Fonts, and this design carries that forward. What happens now is that each cross-domain link is tinted with the background of the page it'll link to. So if you browse the sites enough, you'll identify where you are based on the coloring at the top. Each site is stored in the DB along with a link color that is set by the Arcology Seed Command and a Django view renders a dynamically generated CSS file and because I've been more and more of an org-babel sicko, those CSS files are paired with one for the current page's site are generated dynamically using org-mode tables. 😈

I also set up a flexbox layout that will show the backlinks and page metadata on the side on a wide enough display, or float them toward the bottom if you're on a narrow display or browsing on mobile. I'm still investigating what changes I need to make to get Tufte-CSS-style sidenotes to work, but this is a good start.

I need to tackle feed generation next, and I am not looking forward to re-doing this to not rely on Pandoc like the current version does. Once I've done that, it can be self-hosting though, which is exciting stuff.