Robert Sanscartier
Storm shows British state can’t cope with climate chaos
Storm Bert has battered Britain. But so much of the devastation could have been avoided
https://socialistworker.co.uk/news/storm-showed-british-state-cant-cope-with-climate-chaos/
#UK #ClimateChange #GlobalWarming #GlobalBurning #ClimateDestruction #ClimateSuicide #MassExtinction #pollution #ecology #environment #climate
𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇨🇦)
Bitcoin might help.
Bitcoin ends all money printing.
Bitcoin will never have more than 21 Million.
If you want to fund militarism, you have to ask the people to fund it and if they dont, you are out of luck.
No more money printing to pay for militarism.
If we dont switch to bitcoin or something alike, capitalists will continue to abuse the money printers to fund militarism to the detriment of all of us
Hyolobrika
𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇨🇦)
i am on nostr because it is the only truly decentralized social network.
1. it give you a keypair to be in charge instead of email/password managed by instance admins, where they are part of the name others know you by and, where they theoretically could impersonate or censor you.
2. you always have to choose one instance
in relay based your signing keypair owned by you is your account and you can use any relay (=instance) interchangably and even at the same time
𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇨🇦)
Bitcoin will help with taking away the capitalist money printer privilege.
It wont just over night change the difference between poor and rich - this will require further steps, such as mutual aid and worker cooperatives and so on, but at least, anything that is successful cant just be outspent by capitalists printing money and make a cheaper copy cat where everyone is paid way more.
no more billionaires - they all got printed rich.
Chewie
@serapath @Snoro bitcoin definitely will not help.
Oh, you're also on nostr, that explains it 😜
Hyolobrika
Chewie
@Hyolobrika @serapath @Snoro @silverpill @arcanicanis cool! Sounds complicated!
silverpill
@serapath @arcanicanis @Hyolobrika @Snoro @chewie Those posts were not written by big tech standards bodies. They explain some minor technical details, so yes, that might look complicated, but an average developer don't need to think about that, like he doesn't need to think about how HTTP and TLS work.
By the way, the up-to-date high-level spec is here: https://codeberg.org/fediverse/fep/src/branch/main/fep/ef61/fep-ef61.md
𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇨🇦)
@Hyolobrika @chewie @Snoro @silverpill @arcanicanis
i am not against it - but i am not a big fan of the big tech standard bodies approach.
i am all for people hacking on stuff and using it and sharing it with others who might adopt it.
let it be a more natural approach whwre adoption means it becomes an industry standard or best practice.
anyone can propose, other can adopt to grow how widespread something becomes.
source code is the spec and LLMs can soon translate to english if needdd
silverpill
@serapath @arcanicanis @Hyolobrika @Snoro @chewie I write specs because other developers use different programming languages and can't easily read my code. Even if they a familiar with the language, it takes time to understand someone else's codebase, and communicating in human language is much easier.
Another reason is implementation details: every software is unique and developers usually don't want to copy each other. Only features that are common between different implementations are described in specs, this is necessarily a collaborative process.
𝓼𝓮𝓻𝓪𝓹𝓪𝓽𝓱【ツ】☮(📍🇨🇦)
@silverpill @arcanicanis @Hyolobrika @Snoro @chewie
oh sweet. didnt know about it.
i like that.
i still prefer writing code and adopting it over writing specs.
code is executable spec.
maybe not as human readable, but when if not now could you use AI to turn it into readble english?
i remember a time when standards happened because the majority of users adopted a specific package as their dependency.
i really do prefer that over writing specs
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.