Apache ECharts
group: inks@inks.tedunangst.com
tags: #graphics #inks #javascript #library #visualization #web
tags: #einsatz #geld #lizenz #menschen #opensource #redis #web #wissen
đ§” âŠzum obigen Toot von drei Jahren fĂ€llt mir auf, dass einige #OpenSource Produkte mittlerweile ihre #Lizenz wechseln um nun #Geld zu verlangen. Mit anderen Worten, die haben #Menschen anhand ihr #Wissen und #Einsatz ausgenutzt um nun schonungslos Profit zu ergattern. DiesbezĂŒglich gehören weit verbreitete Werkzeuge fĂŒr #Web-Entwicklung und der gleichen, die Alternativen zu #Redis & Co. bauen sich nun "langsam" auf.
tags: #browser #chrome #firefox #fun #internet #it #joke #privacy #web #webbrowser
Any popular web browser are based on Google Chrome, except Firefox đ€
https://mastodon.social/@publictorsten/114223873439053263
tags: #OpenTechFund #SmallWeb #encryption #eu #fascism #letsencrypt #smalltech #ssl #tech #tls #usa #web
to: https://ec.social-network.europa.eu/users/EUCommission https://infosec.exchange/users/letsencrypt https://social.nlnet.nl/users/nlnet
đš Letâs Encrypt at risk from Trump cuts to OTF: âLetâs Encrypt received around $800,000 in funding from the OTFâ
Dear @EUCommission, get your heads out of your arses and letâs find @letsencrypt âŹ1M/year (a rounding error in EU finances) and have them move to the EU.
If Letâs Encrypt is fucked, the web is fucked, and the Small Web is fucked too. So how about we donât let that happen, yeah?
(In the meanwhile, if the Letâs Encrypt folks want to make a point about how essential they are, it might be an idea to refuse certificates to republican politicians. See how they like their donation systems breaking in real timeâŠ)
CC @nlnet @NGIZero@mastodon.xyz
Wenn Letâs Encrypt plötzlich nicht mehr klappt, wird das halbe Internet aus Zertifikatsfehlern bestehen. https://www.heise.de/news/Nach-Trump-Dekret-Kampf-um-US-Foerdermittel-fuer-Tor-F-Droid-und-Let-s-Encrypt-10328226.html
tags: #comic #technomage #unix_surrealism #web
JavaScript Temporal is coming
group: inks@inks.tedunangst.com
tags: #browser #inks #javascript #library #programming #update #web
May I just say so myself that Iâm loving playing with KittenÂč to build DomainÂČ (shown below) and PlaceÂł.
Âč https://kitten.small-web.org
ÂČ https://codeberg.org/domain/app
Âł https://codeberg.org/place/app
Justified Text: Better Than Expected?
group: inks@inks.tedunangst.com
tags: #design #html #inks #web
Golden rule for a better #web: stop using a service if their browser-accessible website is a simple âdownload our appâ page.
BuyVM is changing hands and the Luxembourg location will be moved to Netherlands. So basically no freedom of speech and more likely government meddling when being involved in more controversial topics. Just so everybody knows.
More info on their Discord (sadly).
Edit: https://fluffytail.org/notice/ApwMFDlD3GhGD1CK4e
A Tour of WebAuthn
group: inks@inks.tedunangst.com
tags: #auth #inks #opsec #programming #security #web
My approach to running a link blog
group: inks@inks.tedunangst.com
tags: #inks #links #social #web
Substack's UI and 1Password just cost me $2,023
group: inks@inks.tedunangst.com
tags: #browser #business #inks #ux #web
tags: #scroll #ui #ux #web
to: https://mastodon.social/users/adactio
Donât Fuck With #Scroll
If Not React, Then What? https://infrequently.org/2024/11/if-not-react-then-what/
https://trwnh.com/unstable/what-is-web
or: the many webs interpretation, what #web means to me, and how do we build the #socialweb
> we define "social web" as "people who want to be social on the web", but this probably depends on what you consider âwebâ, because we certainly already have many many ways to be social on the internet [...] i think that âwebâ means âanything with linksâ.
> in a more practical sense, it's âanything accessible by a web browserâ [...] pull from those acronyms the âhypertext webâ
the way extensibility works in a closed-world #fediverse is that "every implementer talks to every other implementer". or maybe there is a central registry of extensions that everyone submits to their authority, as stewards of the "protocol" that is used to build the "network". this trades out the n:n relation between implementers and other implementers, for an n:1 relation between implementers and the central registry.
the way extensibility works in an open-world #Web is you just do it.
11/?
to build the #fediverse as its own "social networking protocol" then seemingly requires that we instead go with the closed-world assumption, contrary to the #Web
it requires ahead-of-time communication and coordination, where implementers need to be willing and available to talk to any other implementer, and this load grows with every new implementer.
it requires you to be aware of other extensions, present and future, because your extension might conflict with someone else's extension.
10/?
this is the fundamental divide between #fediverse thinking and #Web thinking, where #ActivityPub straddles the line between both.
i've seen it said that the "open-world assumption" at the foundation of the Web is actually an undesirable thing for a "social networking protocol", and as a consequence, specs built on that open-world assumption are "completely unsuitable" for that "protocol".
but do we need a "social networking protocol"? do we even need "social networks" in the first place?
9/?