#frugalcomputing — Public Fediverse posts

Hello!

I'm Taylor and I'm a philosophy PhD student transitioning out of academia into who knows what. But I know if I stop reading and writing I get restless, so I want to continue doing that here and on my website.

In #philosophy, I'm into Continental philosophy, Post-Kantianism, history of philosophy, aesthetics, language/semiotics, and classical rhetoric.

I also enjoy #cinema (esp. art films, horror, old Hollywood) and music. I make syllabi of movies and albums to watch/listen through chronologically.

I have no professional background in tech, but my logic brain can pick up on tech stuff pretty quick. I like #Linux, #SelfHosting, #FrugalComputing, and probably more things I haven't discovered yet!

Looking to make friends with other people into #philosophy, #movies, or #tech 👋

#Introduction #NewHere

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://www.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://www.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://www.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://m.earth.org.uk/RSS-efficiency.html

Do you have surveillance cameras? A network-attached surveillance camera can consume a sizeable amount of energy. It's not just the camera but also the NAS or NVR for storage, software for image analysis, and network equipment that's loaded continuously because of the recorded streams. Simple tip to reduce power consumption: just store the event recordings on an SD card in the camera unit. It has downsides, but it's very efficient. #energyefficient #nas #surveillance #frugalcomputing #locaverdi

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://m.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://m.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://m.earth.org.uk/RSS-efficiency.html

RSS Podcast Feed Inefficiency - Climate cost of handling feeds ineptly... #RSS #podcast #FrugalComputing #LowCarbonComputing #greenSoftware - https://m.earth.org.uk/RSS-efficiency.html

Sometimes compute needs to be quick and can't be shifted to "cleaner" locations because of the hardware required (e.g. GPUs), data-locality, or governance factors.

#microservice architectures could allow you to adapt the *quality* of an application, by turning various value added features off when they are drawing on dirty energy, and back on when they are clean.

https://www.sicsa.ac.uk/wp-content/uploads/2024/11/LOCO2024_paper_40.pdf

& more in preprint: https://arxiv.org/abs/2411.19058

#loco2024 #frugalcomputing

"Declaration on an academic response to the planetary crisis"

How can we, as academics, respond to the ongoing planetary crisis? The declaration

https://docs.google.com/document/d/165TXefhnIqlpGMkPuWgeGS8lBVhSKf7uVlt6CmIKjT0

identifies seven pragmatic steps we can take.

If you support this initiative, please sign using this link: https://docs.google.com/document/d/1TCrQIIDsJAI6JvOuDOvlzldkrEwhmtCoHOxcy1HlGsc/edit?usp=sharing

This is an initiative of S. Keshav,
Robert Sansom Professor of Computer Science at the
University of Cambridge

#FrugalComputing #ClimateEmergency #PlanetaryCrisis
#Academics

The past few days I've been thinking a lot again about one of the thought/design models most influential on my own #OpenSource practice: Frank Duffy's architectural pace layers (and Stewart Brand's subsequent extension to different contexts), their different timescales and interactions as basis for resilient system design:

1. Each layer exists & operates independently, moves at different timescales (from seconds to millennia and beyond)
2. Each layer influences and only interacts with its direct neighbors

"Fast layers innovate, slow ones stabilize." — S.Brand

I always found that model super helpful for analyzing and deciding how to deal with individual projects and components in terms of focus/effort, and asking myself which layer this thing might/should be part of. Lately though, I keep on trying to figure out how to better utilize that model to orient my own future practice, also with respect to the loose theme of #PermaComputing and how to frame and better organize my own approaches to it, incl. how to reanimate or repurpose some of the related, discontinued, but not invalid research & projects I've been doing along these lines over the past 15 years...

I understand and appreciate most of the focus on #FrugalComputing & #RetroComputing-derived simplicity as starting points and grounding concepts for attempting to build a more sustainable, personal, comprehensible and maintainable tech, but these too can quickly become overly dogmatic and maybe too constraining to ever become "truly" permanent (at least on the horizon of a few decades). I think the biggest hurdles to overcome are social rather than technological (e.g. a need for post-consumerist, post-spectacular behaviors), so I'm even more interested in Illich/Papert/Nelson/Felsenstein-inspired #ConvivialComputing, #SocialComputing, IO/comms/p2p, #Accessibility, UI, protocol and other resiliency design aspects becoming a core part of that research and think the idea of pace layering can be a very powerful tool to take into consideration here too, at the very least for guiding (and questioning) how to approach and structure any perma-computing related research itself...

Given the current physical and political climate shifts, is it better to continue working "upwards" (aka #BottomUpDesign), i.e. primarily focusing on first defining slow moving, low-level layers as new/alternative foundations (an example here would be the flurry of VM projects, incl. my own)? Or, is it more fruitful and does the situation instead call for a more urgent focus on fast-moving pace layer experiments and continuously accumulating learnings as fallout/sediment to allow the formation of increasingly more stable, but also more holistically informed, slower moving structural layers to build upon further?

It's a bit of chicken vs. egg! In my mind, right now the best approach seems to be a two-pronged one, alternating from both sides, each time informing upcoming work/experiments on the opposite end (fast/slow) and each time involving an as diverse as possible set of non-techbro minds from various fields... 🤔