Playing with the Bluesky/Fediverse bridge, and even the RTs are reflected!
When someone questions the role of linking or dismisses it as spammy behaviour, they are often viewing it through the #closedweb lens, where linking outside the walled garden is discouraged or penalized. The #openweb, however, relies on this practice to thrive. So, before sounding off with uninformed critiques, remember: linking on the #openweb is fundamentally different from linking on the #closedweb.
#Openweb: This refers to the original, decentralized ethos of the internet, built on openness, freedom, and people's autonomy. Linking enhances knowledge sharing, amplifies lesser-known voices, and enables people to explore varied content freely.
#Closedweb: This describes platforms dominated by algorithms, corporate interests, and paywalls. On #dotcons, linking is often spam and is penalized or buried, precisely because it can disrupt the curated control these platforms wield over what people see.
Remember also that part of the adversary here is foreign governments, not actual candidates. Their goal is not necessarily to pick the winner, but rather to weaken the legitimacy of the US government's ability to function. Disinformation about election integrity is a central weapon in their arsenal for achieving this.
The concern here is that old search engines can give you links and you can go into them to verify the content. AI taking over our search engines hides the sources of information, forcing us to blindly trust the AI and wherever it got its information from.
@foone alas, people don't write JavaScript for the browser anymore.
(They write it for the _bundler_ instead)
I don't want to convert my entire project to EMCAScript Modules and build it with a Bundler. It doesn't work that way and really doesn't need to work there way.
The UTF-8 encoded BOM is an offense to engineering.
Oh hey TIL why the UTF-8 byte order mark is the seemingly random byte sequence <EF BB BF>. It's simply because that's the UTF-8 encoding of U+FEFF, the code point that's also used as the byte order mark in UTF-16 and UTF-32.
UTF-8 has no issues with byte ordering, so the UTF-8 BOM is an oddity that shouldn't be emitted. But it exists and is specified because it's what happens if you take a BOM-ful UTF-16/32 sequence and naively transpose it to UTF-8, the leading U+FEFF BOM becomes <EF BB BF>.