The only way to preserve privacy while having a central and easy authentication mechanism I can think of is to use IndieAuth[0] which is built on top of OAuth 2.0.
Of course, you will need to be your own provider, using an IndieAuth provider service defeats the purpose, which is what I see most IndieWeb devs are doing.
I have worked with graduates joining remotely during the pandemic, like most graduates they also lacked the skill to work in a real environment, but we can teach them, it's easy. But during the AI boom, the people who could teach the graduates were let go, leaving only a handful of senior engineers that had to "increase their productivity" while also mentoring the juniors. Guess where people cut corners to keep their job longer?
The main threat to small web is the reachability, I serve Atom and JSON feed, support microformats, microsub, and micropub, syndicate my posts to other platforms all without ads or telemetry. But all that effort means nothing if it doesn't reach the intended user base, it's just shouting at the void.
We can have a small community somewhere, but people who search for niche things should find them -- which used to be search engines after the .com boom and the burst. Now we are back to the small forms again, which is lacking the reach because--- new people can't reach the forms as they can't find them in the first place.
If someone new to the internet find the website, then nothing else matters.
Most of all websites will lose their traffic, some already did.
- People using the search console see the drop
- Product owners scratch their head
- Investors backing out because not having many visitors
- Small bloggers adding more ads because their revenue is dropping
- Sponsors backing out from their blogs because it's loosing more visitors
- Small web crumbling
- People google what is happening
- Google says 'The "small web"—independent blogs, personal forums, and niche websites—is disappearing due to corporate consolidation, aggressive AI-driven search indexing, and high maintenance costs. These factors have pushed independent creators onto walled-garden social media apps, leaving personal websites to suffer from "link rot".'
An acronym is a specific type of abbreviation formed from the initial letters of a phrase and pronounced as a single word. I was being more specific. And the ones you are pointing out are from the header.
> An abbreviation whose expansion is provided the first time the abbreviation appears in the content
Content is the main body of the article (press tab ones you land the page, it will take you to the main content if you don't know what that is), which contains only one Acronym, “SC 3.1.4” → which is a link that take you to a place with its definition. I don't understand what you are fighting over. But I'm not going to reply more to someone who defends people who do not know how to write articles that are more friendly towards the reader.
The comments are annoying. No matter the niche, it is always good to write the abbreviation the first time it is used, in fact, W3C recommends it[0]. Anyone who does not follow this either are not informed well enough, or has ableism. Most replies in this thread shows the latter.
I would rather not hand mine or my neighbours' health data to a spy-tech firm, who will have unlimited access to their data[0].
Not having the system (it's not like it's already in use anyway) is always a good step in the right direction. And a replacement built-in UK will provide more jobs, more tax money, and digital sovereignty for UK.
You don't need to know the account or account number, just need to know the transaction logic, which most backend developer will know of as long as they work in that area.
If the product managers keep boasting about their new strategy (which I have seen in almost all companies I have worked for), even the juniors will know what's going on.
Unsure why this is a reply to the OP, the only thing common is RMS and nothing else.
But, RMS is known to be socially awkward, the same goes for many autistic individuals. It's just that he doesn't mask and comes out as “rude”.
If send an e-mail, he will usually take his time to write down a succinct response.
> Surprised how many people don't seem to know about it.
There are a few reasons for that.
1. The link to APK cannot be found on the official site[0], so it needs to be looked up in a search engine.
2. Even when downloading from the site, they try to scare you away with a warning [1]. The reason for warning could be avoided by hosting their own F-droid repo, but they refused it, claiming you can download APK and not listening to reason[2].
Though for people using F-droid can still get Signal through the Guardian repository [3]
Thing about the signal APK and the Guardian one is that, it still have the so called "crap" in the final APK, it just runs a background service when required google services are not detected, causing battery drain for many[4].
The drain could also be avoided by supporting UnifiedPush (it can fall back to FCM when it's detected), but they don't want to do that either[5].
This, I set an alias for `adb` to use `"$XDG_DATA_HOME"/android` instead of `~/.android` because it stores the keys there for whatever reason. I would rather not see my home folder being cluttered with hidden files, it makes backing things up unnecessarily complex.
export ANDROID_USER_HOME="$XDG_DATA_HOME"/android
alias adb='HOME="$ANDROID_USER_HOME" adb'
Font customization is need to emphasise, it helps the reader understand the sentence better, other styles such italics, underline, and strike through… would greatly improve understanding the context and increase readability, it's just a matter of good typesetting.
Inline links also help with the same, people who dislike it should be able to move them out of the context (like some terminal based browsers).
I don't care about image, video etc, they can just be a link to the resource if/when needed... given alt text/CC is supported or accessibility.
Same for color coding stuff and CSS, users should customize their client for that if they want to, not the server.
The only way to preserve privacy while having a central and easy authentication mechanism I can think of is to use IndieAuth[0] which is built on top of OAuth 2.0.
Of course, you will need to be your own provider, using an IndieAuth provider service defeats the purpose, which is what I see most IndieWeb devs are doing.
You will need to own a (sub)domain though.
[0] https://indieweb.org/IndieAuth?redirected=IndieAuth