@mathieu I'm not trying to slam GNOME here, just being realistic about its limitations, and particularly who can use it (people privileged enough to have reasonably new/ more powerful computers)
Alright, then let me restate it; 2) What can a completely *new* GNU/Linux user, who expects everything to "just work", do *easily* with GNOME that they can't do with Mate?
> Chinese input methods.
How does GNOME handle this that makes it easier to use than in Mate?
Also, still curious about question #3? 3) What does full GNOME do that Fallback doesn't?
Alright, then let me restate it; 2) What can a completely *new* GNU/Linux user, who expects everything to "just work", do *easily* with GNOME that they can't do with Mate?
Also, still curious about question #3? 3) What does full GNOME do that Fallback doesn't?
> Chinese input methods.
How does GNOME handle this that makes it easier to use than in Mate?
BTW I remember seeing a #GNU#Linux distro home page (#ElementaryOS?) that had a diagram laying out all its major components, which I think was the seed of the SB concept.
@msh in reality, most countries have heaps of economic energy that their fiat currencies are too scarce to utilize (or at least can't account for), eg the labour of the under/unemployed, waste that could be recycled/ reclaimed, renewable energy sources, and so on. The idea of local currencies is that they can mine this economic energy, increasing internal wealth, without increasing imports and creating #BalanceOfPayments issues. @clacke
@msh > it sounds like an economic "perpetual motion machine"
This idea rests on the #NeoClassical assumption that economic energy pours into a country's economy from the outside. But that's only true to the degree that the country imports stuff from outside. #FreeTrade Suppression Treaties (PR name "free trade agreements") often have clauses preventing #ImportSubstitution to force countries to import more stuff, whether they need it or not, and thereby, force them to export more. @clacke
@msh in that case it's pretty easy to know; it was killed on purpose by the central government. The monopoly on issuing currency is almost as important to the essence of the state as the monopoly on the use of force, and as important as the power to tax. In every country, states have sabotaged or outright banned local currencies, to enforce this power. #DougRushkoff goes into that history in his book #LifeInc. @clacke
@Cochise We don't need everyone auditing every dependency, that's duplication of effort. But it is useful to know that *someone* has audited each component our software depends on, and *when*. Ideally, share out the work so that each component is reviewed/ audited by the person with the most relevant domain knowledge. Its also useful to know whether someone trustworthy can vouch for each maintainer/ reviewer/ auditor. These are all long term design goals for Software Burger
@Cochise just showing the dependency tree is the #MVP stage of Software Burger. The larger goal is for is to be a tool in ongoing conversations about software architecture, the most efficient way to maintain common components, the ideal size of packages for different purposes, and so on. Also a way of tracking dependency maintenance, and when it is and isn't happening. Visualizing if and when code reviews/ audits have happened could be part of it too.
@tootbrute sounds way more powerful than Bishop (my ancient #AA1 netbook). I ran #LMDE with #Cinammon on a similarly powered machine before I relocated to China and had to get rid of it, and that worked fine. Again, really keen to hear how it goes with Trisquel/Mate.
@clacke the power to issue currency that people consider trustworthy reflects deeper issues of political power and legitimacy. There are reasons that fiat currencies have the tremendous #NetworkEffect that they do, and that any other currency experiment becomes either a proxy for them (eg #CryptoTokens), or is extremely limited in its usefulness (both by legal regulation and in buying power). @msh
@clacke not a coop, because one of the core principles of a coop is voluntary membership. A state, by definition, is not that. As an aside, my politics are a weird mix of social democrat values from unionist family, and my own #counterculture#anarchist inclinations. I'm intrigued by the #P2PF's concept of a #PartnerState as a possible synthesis of the two: http://wiki.p2pfoundation.net/Partner_State
@clacke agreed. It's a clever hack, taxing the revenue of polluters to cross-subsidize the emergence of new businesses providing less polluting versions of the same products and services, while leaving the winner-picking to citizens via markets. If it works, we achieve the results folks often expect from heavy-handed regulation, without centralizing more power in the state, and risking regulatory capture or unintended consequences (eg the Food Bill debate in NZ). @LibertyPaulM@msh
@NylaWoethief this is intriging, thanks for the share. My wife used #Scrivener a lot when writing her thesis, but sadly it's proprietary. Great to see someone has created a #FreeCode replacement! Not so relevant to novels maybe, but she also used #Zotero for managing citations, as a free code replacement for #EndNote. She liked it enough to buy a license for their online backup service, a few years in a row.
I found an interesting app that should prove useful for #fiction#writing. It is #FLOSS freemium software for Windows, MacOS, and GNU/Linux. The interface is really nice, and I can see it being very useful for keeping track of characters, story ideas, etc.
@adfeno so basically, if Electron was ported to #Iridium, all of these accusations of being non-free, against projects that use Electron to package their desktop apps, would evaporate overnight. The same would be true if a fully #FreeCode replacement for #Electron could be found, one that supported the 'design once, deploy everywhere' development style, but didn't inefficiently bundle most of a bloated browser inside its apps.
I think you're overstating your case here, to the point of misleading people. AFAIK Riot *itself* isn't non-free, it's desktop apps have a non-free dependency; #Electron. Actually Electron itself isn't non-free either, it also has a non-free dependency; #Chromium. Actually #Chromium itself isn't non-free either, it just has some dependencies whose license situation is unclear.