We are still a massive €254 short for the server bills for mstdn.social, misskey.ai, mastodon.coffee, pixey.org and some more free open source services
Hopefully next month I can pay most of it with a new job but that doesn't help now..
If you can, please think about supporting me in paying the bills for the various #Fediverse services I host for free❤️
If not me perhaps your own server admin
Hot take: it is useful to add issues to your issue tracker even when it's technically an "upstream problem":
* it makes it easier to find the issue for others running into it
* it provides a place for users to share workaround for this particular instance of the problem
* it reminds you to help upstream fix it
* sometimes there is a fix in using upstream differently (or even replacing it)
Debian gets this right and even has some nice standardized metadata for this (https://wiki.debian.org/BugTriage#Working_with_upstream)
Computer, ARM history
The ARM chip was also designed to run at very low power. [Sophie] Wilson explained that this was entirely a cost-saving measure—the team wanted to use a plastic case for the chip instead of a ceramic one, so they set a maximum target of 1 watt of power usage.
But the tools they had for estimating power were primitive. To make sure they didn’t go over the limit and melt the plastic, they were very conservative with every design detail. Because of the simplicity of the design and the low clock rate, the actual power draw ended up at 0.1 watts.
In fact, one of the first test boards the team plugged the ARM into had a broken connection and was not attached to any power at all. It was a big surprise when they found the fault because the CPU had been working the whole time. It had turned on just from electrical leakage coming from the support chips.
Yes, it's an issue. The ultimate solution is to get all jurisdictions to do what NZ did and remove software from the scope of patent law. In the meantime, compromises such as defensive patents may be necessary. But since they also implicitly endorse the patenting of software, it's crucial to have robust debate about whether they really are necessary and what other defensive options exist for libre software communities.
> another company that filed a patent for using Holochain
Ah ok, that makes more sense. A blog piece that tells that story would be useful here. IANAL either but ...
... rather than filling for their own patent, couldn't the HC folks have used the same money and prior art to invalidate the other patent? Wouldn't that create a precedent that could strike down future patent applications involving HC?
The Lost Ways of Programming: Commodore 64 BASIC
"When Commodore 64 starts, a welcome screen from BASIC awaits you. Even if you want to use it to just play games, you start with a programming environment. This tells you that you too can become a programmer and you certainly do not need to download gigabytes of tools and wait hours for your XCode or Visual Studio to install. "
@dcz ah, so, Erlang/Elixir? Or are there more declarative options? A far-out option is Parasail (Ada with implicit parallelism but not declarative). A more Prolog-y option seems to be Mercury which has implicit parallelism. A mundane option might be GNU parallel?
@dcz late to the thread, but I am a recent follower of Prolog. https://www.swi-prolog.org seems to have threaded execution, not sure whether it is implicitly parallel under the hood. But why not gorge on bountiful free/open software? Write Prolog that generates a Makefile and run it with 'make -j $CORES' ? Or run many Prolog instances (pengines?) designed in a control hierarchy?
@clacke @strypey in hindsight, the drama over the drafting process of the #Holochain #CAL seems to be fear of it being more effective in promoting #FLOSS than #FSF or #OSI #Licence s. You did voice concerns about FUD, but wouldn't you say that FUD against GPL failed (people serious about software were not all sheeple)? And I bet the people behind that FUD themselves free-loaded off GPL'ed software (and stayed silent on the more effective AGPL - probably stayed silent on the CAL too?).
The licence itself seems to be an amalgam of an improvement over AGPL w.r.t data and LGPL-like permissions for parts of the subject of the #Licence . Mostly good, the only gripe might be that it will take lawyers to confirm if it is trouble-free for open projects to use it or Holochain and the like. But that seems "just" 1 "autonomy audit" away.
@matslats greetings. Just read your website. Tempted to say "kudos" to your way of living, but you say altruism needn't be appreciated 🙂
What do you think of property rights? Shouldn't they be abolished in a wholly-communal society? Before the British leech attached itself to India and did land "reforms", land was a commons!
@mike_hales @gert @strypey @lightweight @bhaugen @organizingInFedi @matslats https://webxdc.org by the people behind @delta is interesting, in that it is webapps that uses chat as auth. As I understand, a "server" could be a chatbot sending webxdc apps as responses and handling app responses. If Quicksy support "appears", running community-member-friendly services sounds more tractable than otherwise.
Yes timebanks could be in for some resource sharing, there seem to be many implementations. In my mind, a NoBank would also make sense, just a database of who owes what to whom, which can then be settled automatically (unlike with your bar tab). Both would work best in local contexts, but that is IMO the most important context.
BTW, FYI, I also posted this: http://nlchat.citiwise.eu/chat/sei/index.html#!/Co-op-dev
I write software (C++) for a living.
QOTO: Question Others to Teach Ourselves. A STEM-oriented instance.
An inclusive free speech instance.
All cultures and opinions welcome.
Explicit hate speech and harassment strictly forbidden.
We federate with all servers: we don't block any servers.