in the dark 1984 future, all communications are harvested by the government *google harvests everyones communications* well its not the government so its fine
I've been able to hang out and do some work and I don't have to wifi at home and I don't really require to buy a coffee either, and there are all these public resources here, in a respectful quiet atmosphere
"Value Flows is a set of common vocabularies to describe flows of economic resources of all kinds within distributed economic ecosystems."
"Purpose: to enable internetworking among many different software projects for resource planning and accounting within fractal networks of people and groups. The vocabulary will work for any kind of economic activity, but the focus is to facilitate groups experimenting with solidarity / cooperative / collaborative / small business ecosystem / commons based peer production / any transitional economies."
Google, Microsoft, Apple wants to create less stupid programmers by creating new languages like TypeScript, Kotlin, Swift, instead of just training them
@z428@wyatwerp@switchingsocial@staltz There's a lot discussions internally in the SSB community, upcoming academic papers, and a committee reworking the protocol, and they are not determined to keep immutability. It would be possible to mutate or delete posts after posting. So it's important to remember that SSB is not static, there's a lot of development going on. — @staltz
We received a request to #Tusky in the past week, as Mastodon has now opened API for moderation.
As we don't want to spread ourselves too thin we think it'd be better if someone else on here worked on this, but you'd also receive our full support and help where we can.
Let us know if it's something you'd like to work on, and we'll give you a boost!
A good piece of software exists and is enjoyed by many users. It's basically done and development has slowed down, but it nevertheless continues to be useful to its users.
Later, a new piece of software enters the same market to solve the same $task. It has to rewrite everything from zero, which may take years. As they make improvements over the years, each announcement keeps them on top of the news cycle, with each inch they move towards the finish line.
Result:
$newproduct erodes the mindshare from $oldproduct. It has been present at the forefront of the public's minds and quickly gains marketshare, and users who were familiar with $oldproject prior to the introduction of $newproject start to age out of the market.
This happens even if $oldsoftware is free/open-source and $newsoftware is proprietary, if $newsoftware is missing important features of $oldsoftware, if $newsoftware is a gear in the capitalist machine and will eventually spit its chewed up users out when they get sold to the highest bidder, etc.
you give it a URL and it makes a snapshot: two HTMLs, WARC file, PDF, full page screenshot, then sends it to archive.org to be 100% sure. It's too easy to fake a screenshot, but this is a compelling pile of evidence.
it's not for a regular user, though: piping URLs to console commands isn't a common knowledge. But I hope someone will make a service or something.
@emacsen Sorry if it appeared like it's just my personal gripe with one project, but from my perspective, it's a whole new trend that's spreading throughout FOSS, and IMO leads us to a very grim future.
From my experience, there's a dichotomy between developing software as a product/experience or as a tool.
Whenever someone treats a piece of software as a product, tries to make things out of the box, etc. they end up hiding complexity - oftentimes inherent complexity of the problem the software tries to solve - under the carpet. That leads to all kinds of issues when the user wants to do something nonstandard, or encounters an edge case.
It also often correlates with the developer thinking they're smarter than the user, and trying to force their decisions onto users.
OTOH, when developing a tool, the developer exposes how it works to the user, and passes the decisions - and responsibility for them - onto the user. This often means the UX isn't as nice, because the user is forced to face the real complexity of the problem at hand.
I see those two approaches as mutually exclusive. I hope one day I'll be proven wrong.
Yeah, though it's not actually federating the Moodle LMS but rather creating a new education-focused social network (which will also be accessible from within Moodle).
@acka47 We just use some standard Activities supported by other implementations so far. We do have custom Objects, but they're done as extensions of standard Objects (like Link) so other implementations can interoperate without knowing anything about MoodleNet.