shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

#frugalcomputing

1 post1 participant0 posts today
J$<p><span class="h-card" translate="no"><a href="https://mastodon.social/@macrumors" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>macrumors</span></a></span> Sadly, these five reasons not to don’t even include <a href="https://mastodon.nl/tags/sustainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sustainability</span></a>, <a href="https://mastodon.nl/tags/degrowth" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>degrowth</span></a>, <a href="https://mastodon.nl/tags/frugalcomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frugalcomputing</span></a>, <a href="https://mastodon.nl/tags/DigitalAutonomy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalAutonomy</span></a>. What a miss.</p>
doboprobodyne<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mcc</span></a></span> <br><a href="https://mathstodon.xyz/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> 🦾</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://floss.social/@jbqueru" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jbqueru</span></a></span> I do agree in that we need more <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> options.</p><ul><li>If I really wanted and needed to I could do my work on an <a href="https://infosec.space/tags/EeePC701" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EeePC701</span></a> or a Vaio <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P11Z</span></a> and I think these devices have still potential to be used.</li></ul><p>That's why I started <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span>: <br><a href="https://os1337.com" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">os1337.com</span><span class="invisible"></span></a></p><p><a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS1337</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://56k.dile-up.nl/users/fristi_ebooks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fristi_ebooks</span></a></span> use a <a href="https://infosec.space/tags/fanless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fanless</span></a> <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClient</span></a> as a <a href="https://infosec.space/tags/Server" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Server</span></a>?</p><p><a href="https://infosec.space/tags/Reuse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Reuse</span></a> <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> <a href="https://infosec.space/tags/MiniServer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MiniServer</span></a></p>
Kevin Karhan :verified:<p>True, true...</p><p><a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> barely sips resources unless one explicitly works towards it (i.e. setting up a <em>big-ass</em> <a href="https://infosec.space/tags/ramdisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ramdisk</span></a>!)</p><p><a href="https://www.youtube.com/watch?v=upXQQaDTuFM" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=upXQQaDTuF</span><span class="invisible">M</span></a></p><p><a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Windows</span></a> <a href="https://infosec.space/tags/WindowsSucks" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WindowsSucks</span></a> <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> <a href="https://infosec.space/tags/Efficiency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Efficiency</span></a></p>
Ed Summers<p>I appreciate the point made by <span class="h-card" translate="no"><a href="https://toot.mynameismwd.org/@michael" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>michael</span></a></span> in his <a href="https://social.coop/tags/loco2024" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loco2024</span></a> presentation about how <a href="https://social.coop/tags/datascience" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>datascience</span></a> workflows often encourage rerunning compute when it simply isn't necessary, all in the name of reproducibility.</p><p><a href="https://www.sicsa.ac.uk/wp-content/uploads/2024/11/LOCO2024_paper_30.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">sicsa.ac.uk/wp-content/uploads</span><span class="invisible">/2024/11/LOCO2024_paper_30.pdf</span></a></p><p>The paper focuses at a pretty low-level but perhaps it would also be helpful for lineage in systems like Airflow and Spark to make energy use legible, and decidable, if data scientists are willing to sacrifice the quality (e.g. currency) of results?</p><p><a href="https://social.coop/tags/frugalcomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frugalcomputing</span></a></p>
Santiago Soler<p>As maintainer of OSS Python scientific libraries, I'm seeing more users sharing screenshots of their error messages instead of copying and pasting them as text. I'm not sure why that's happening. But here's an advice: </p><p>Please, share plain text!</p><p>Because:<br>* Text is lightweight to send and store. <a href="https://scicomm.xyz/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a> <br>* Text is accessible: not all of us can see images.<br>* Text is easily parseable: I can search through it, copy it, paste it, quote it, reuse it.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@dustinfinn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dustinfinn</span></a></span> so true...</p><p>We've to really curb in on <a href="https://infosec.space/tags/WastefulComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WastefulComputing</span></a> and embrace <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SweetAIBelle</span></a></span> <span class="h-card" translate="no"><a href="https://bitbang.social/@ActionRetro" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ActionRetro</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>OS1337</span></a></span> Cuz while a <a href="https://infosec.space/tags/VT320" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VT320</span></a> <a href="https://www.youtube.com/watch?v=RuZUPpmXfT0" rel="nofollow noopener" target="_blank">looks awesome</a> we can all agree that the <a href="https://infosec.space/tags/VT69" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VT69</span></a> by <span class="h-card" translate="no"><a href="https://mastodon.social/@violenceworks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>violenceworks</span></a></span> is <a href="https://www.youtube.com/watch?v=wYfpptgb6W8" rel="nofollow noopener" target="_blank">way more practical</a> for <em>"<a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a>"</em> or just <a href="https://infosec.space/tags/minimalist" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>minimalist</span></a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> use...</p>
Kevin Karhan :verified:<p>That being said <span class="h-card" translate="no"><a href="https://fosstodon.org/@w84death" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>w84death</span></a></span> 's <a href="https://infosec.space/tags/Floppinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Floppinux</span></a> v0.2.1 just booted through fine, so yeah, perfectly feasible as <em>"low end testbed"</em> unless I get like a <a href="https://infosec.space/tags/VIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VIA</span></a> <a href="https://infosec.space/tags/C3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C3</span></a> / <a href="https://infosec.space/tags/C5" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C5</span></a> / <a href="https://infosec.space/tags/C7" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C7</span></a> or one of those expensive <a href="https://infosec.space/tags/Vortex86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vortex86</span></a>-made <a href="https://infosec.space/tags/486SX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>486SX</span></a> clones that <span class="h-card" translate="no"><a href="https://mastodon.scot/@rasteri" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>rasteri</span></a></span> used for the <a href="https://infosec.space/tags/WeeCee" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WeeCee</span></a>, tho I'm shure noone would go below a <a href="https://infosec.space/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RaspberryPi</span></a> <a href="https://infosec.space/tags/Pi0" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pi0</span></a> / <a href="https://infosec.space/tags/Pi0W" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Pi0W</span></a> v1.3 or the original <a href="https://infosec.space/tags/PiModelB" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PiModelB</span></a> v1.2 in terms of <a href="https://infosec.space/tags/FrugalComputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FrugalComputing</span></a>.</p>

Hi everyone, I am organising LOCO 2024, 1st International Workshop on Low Carbon Computing
It's hybrid and will be held 3 Dec 2024, in Glasgow (Scotland) and on line.
On line attendance is free; in person is £30

Deadline 1 Oct (full talk)/ 8 Oct (lightning talk)

Please consider submitting, whether you're academic or not, and please spread the word.

sicsa.ac.uk/loco/loco2024/

SICSALOCO2024 - SICSASICSA - Scottish Informatics and Computer Science Alliance
Replied in thread

@drwho Shit like this makes me hate not just #snap but @letsencrypt because that's more code than the entire backend for @cacert ...

  • Seriously, there's no valid reason for #LetsEncrypt to take up more space than the acme.sh & #CertBot scripts they made AND certainly not more than the #API for #CAcert back in it's days...

I think there needs to be more and harder pushes for #FrugalComputing because there's no valid reason they basically shove an entire #OS onto an existing one...

  • And even if there was there shure as hell is none for something beyond the ~ 4 MB that #mkroot as a reference implementation of #toybox requires...

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... 🤔

* Make software that works on older devices, the older the better.
* Make software that will keep on working for a very long time.
* Make software that uses the least amount of total energy to achieve its results.
* Make software that also uses the least amount of network data transfer, memory and storage.
* Make software that encourages the user to use it in a frugal way.