"There’s no good reason for any of this. These aren’t cutting-edge interactive applications; they’re pages with text on them. We used to print those on paper, but as soon as we made the leap to computers, it became impossible to put words on a screen without executing several megabytes of custom junk?" https://eev.ee/blog/2016/03/06/maybe-we-could-tone-down-the-javascript/
But #Scoop, #theSpinoff, and now #Stuff, show us that there are other ways media organisations can be owned, managed, and even funded. A brave government would set up a media democracy commission, with antitrust powers to break up struggling media empires, instead of subsidizing their investors at public expense. The broken up entities could be sold to their workers or their audiences/ communities, or both, using the most suitable option from a standardized set of cooperative ownership models.
If your DNS service is stopping you from accessing a site, how do you know that it's been blocked by them? How can you find out why they are blocking it? Maybe services like this need to restrict themselves to blocking only Javascript (to prevent attacks using JS) and popping up a malware warning, like NoScript does when it detects cross-site scripting. That way, the user can review the HTML/CSS page (if any) and choose to block the site for them, or allow JS and continue to browse it normally.
@tomosaigon agreed, but every little bit counts, especially for users on dial-up, rural ADSL, or metered mobile data. As the old saying goes, if you take care of the cents, the dollars will take care of themselves. If everyone points to another resource waster as an excuse to keep wasting resources, nothing will change.
3) localize servers. Where servers are needed, host them as close as possible to where their users are. Eg NZOSS hosts all its services at the CatalystCloud.nz datacentre in Aotearoa, because most of the people using them are located here. If all network services aimed at kiwis did that, it would significantly reduce the traffic on the cables connecting Aotearoa to the rest of the world's networks.
* again, more use of generic native apps * increase the use of browser cache and persistent storage, to avoid the same data being downloaded over and over again on the same sites. * make it easy to download media, rather than streaming it over and over again.
Some examples: 1) Get rid of all unnecessary Javascript * rebuild all simple brochureware sites as static sites using only HTML/CSS. * increase the use of native apps to reduce the avoidable transmission of web apps. Generic, multi-account ones implementing open protocols, not branded ones tied to nonfree services. * get rid of all user tracking and ad serving
I assume the #SPDX standard includes a place to put the version number and release date for software packages, maybe this could be helpful? https://spdx.org/using-spdx-documents
Also: * #PrivateBin.info, a fork of #ZeroBin, a "minimalist, open source online pastebin where the server has zero knowledge of pasted data" * #PasteBin.to, another zero-knowledge pastebin but it uses #CloudFlare * #HasteBin, but it doesn't seem to work without allowing scripts from ajax.googleapis.com.
Is there a metadata standard for tagging software releases, so that sites like the Free Software Directory ( directory.fsf.org ) can automatically list the latest release without human maintainers having to constantly check for new releases? Could this be part of the #ForgeFed spec?
Free human being of this Earth. Be excellent to each other! #Vegan #Permaculture #Transition #PeerProduction #FreeCode #CreativeCommons #SciFi #Comedy #Juggling