Nah. The weird take is promoting paying a right wing chud run, crypro bro ad company $60 USD for a chromium skin browser.
A real non cult, non paid shill, android recommendation would be Vanadium or Titanium.
I hope you’re getting paid (either in the brave bat crypto tokens, or normally) to post this stuff. Cause doing it for free just for cult reasons would be even weirder.
I don’t get why brave cultists try to shove brave into these guides. It’s not bad because it’s chromium. Brave is bad because it’s a crypto bro browser run by a right wing chud ceo. If you are running Brave you might as well just use Omarchy. Both are right ring chud run. At least the Omarchy right wing chud isn’t running a crypto bro ad company. Both are just terrible.The fact that this guide suggests buying a $60 license to brave is insanity.
That is just dumb of them. I would expect a wholly mainline kernel supported machine. At least within 6 months of release.
How did installing cosmic “fry” your laptop? There where situations in the 90s where a bad x11 conf could damage your CRT, but outside of overclocking it’s pretty hard to damage your hardware now days.
Np. I only mention it because sure it’s a weirdly pervasive piece of misinformation.
That and I generally support strong copyleft licenses that primarily act from a non USA base of laws.
Not true. The EUPL defines distribution broadly enough that it covers saas style network use. It’s like the AGPL.
From the article:
And it is quite a divergence from the licenses I’ve used in the past. EUPL is a strong copyleft license that closes the “SaaS loophole” by requiring reciprocal licensing regardless of how the software is distributed.
From the official source:
For many open licences, distributing software is obtaining it (i.e. via downloading) in order to install it on your own device. Licences do not cover remote use, when a user interacts remotely with server-provided functionalities. The definitions in article 1 of the EUPL assimilates “communication to the public” to “distribution” and therefore targets and covers SaaS (software as a service) and the ASP (application service provider) activity.
Article 1 defines as “- Distribution or Communication: any act of selling, giving, lending, renting, distributing, communicating, transmitting, or otherwise making available, on-line or off-line, copies of the Work or providing access to its essential functionalities at the disposal of any other natural or legal person.”.
Therefore on this specific point, the EUPL is similar to the AGPL.
Source: https://interoperable-europe.ec.europa.eu/collection/eupl/faqs
Strong recommend for Seafile. It’s way faster than nextcloud, it has a good web ui, and nice clients on all platforms.
I can not express how much faster than nextcloud it is.
Obviously open source too.
By all means quit using Debian. That’s your prerogative. But claiming you are going to sabotage a community volunteer run, non profit, open source community is just dumb. Good news is that you won’t actually do it, but still, you sound dumb.
You have it mostly backwards. XML has like 40+ types that are all standardized. JSON only has the basic JS types. XML is a superset of JSON when it comes to types.
How would you represent a double float, or binary data, or a datatime in JSON. You would have to use strings in JSON. In XML you would use the xsd:double, xsd:binary, and xsd:dateTime.
JSON only works if you think in JavaScript. For languages with more complete / complex data systems it does not do unless you resort to the string thing.
For your information:
Easier to read: https://www.ibm.com/docs/en/jfsm/1.1.2.1?topic=queries-xsd-data-types
The official spec: https://www.w3.org/TR/xmlschema-2/
As for validation I think “right tool for the right job” is the best approach here. How do you know your validator is validating correctly? That’s the beauty of XML. Validation is part of the spec. XML is more complicated, but only because it’s more capable than json. Just like protobuf is more complicated than JSON. It’s also more complicated and not centered on JSON types.
I’m gunna disagree with you XML comes with validators and versioning as part of the XML spec. You can validate XML files against XSD descriptors that can be published and even referenced by the XML file.
The only downside of XML over json is that XML is verbose AF.
Strict validators, versioning, checking, and definitions is EXACTLY what you want in a storage format.
ODF is also XML. It makes sense here.
More information for you: https://en.wikipedia.org/wiki/XML_Schema_(W3C)
Hot take. Nextcloud is hot garbage. If you want file sync use Seafile. So so so so much faster and more resource efficient. For the rest of next cloud functionality just use a tool specific to that.
Nextcloud is still tied to the old php/fpm model. There are better approaches now days. Hell even owncloud is rewriting away from the php/fpm approach.
I don’t like anti LGBT+, crypto bro run, ad companies. You got me there.
Every time I see people recommending anti LGBT+, crypto bro run, ad companies I will call it out.
You’re the one defending paying $60 USD to an anti LGBT+, crypto bro run, ad company every time someone says anything negative about it.