functional.cafe is one of the many independent Mastodon servers you can use to participate in the fediverse.
functional.cafe is an instance for people interested in functional programming and languages.

Server stats:

223
active users

Wow, what a weird rabbit-hole I just ended up down.

So, the “Spread Mastodon" page (tutorial?) recommends a cool-sounding browser extension as an alternative to all those constantly-dead 'fedifinder' / Twitter-person-looker-upper-tools: the ‘Whosum Social Assistant' browser extension.

Sounds cool! Sounds like the correct solution to this problem!

Public

… but if you click the link, you just get this. A empty page with the modal saying “Please enter your password to get access.”

what, okay, fine, somebody's got something misconfigured.

Public

So, this thing was supposedly open-source, right? Let's go find the source.

Easy, there's a GitHub! Great! github.com/positivesumnet/soci

I mean, no activity in two years, and all the links in the README are broken, but it's a start.

Whosum Social Assistant Chrome Extension. Contribute to PositiveSumNet/SocialAssistant development by creating an account on GitHub.
GitHubGitHub - PositiveSumNet/SocialAssistant: Whosum Social Assistant Chrome ExtensionWhosum Social Assistant Chrome Extension. Contribute to PositiveSumNet/SocialAssistant development by creating an account on GitHub.
Public

Well, even if their bespoke site is down, it's probably still on the addon repositories, right?

Chrome has nothing, chromewebstore.google.com/sear

but it _is_ on the AMO … with precisely one user. What? There's multiple blogposts about this thing around the web. addons.mozilla.org/en-US/firef

sus.

chromewebstore.google.comChrome Web StoreAdd new features to your browser and personalize your browsing experience.
Public

Okay, let's look up the author; I can reach out on Masto (which they'll obviously be on, right? They wrote a whole-ass manifesto about switching to Mastodon.) and tell them that their website’s down; not to mention they'll probably be an interesting follow.

The GitHub committer for the project is github.com/scafaria; there's an e-mail address … at a domain which redirects to the same, empty website as we found at the start: positivesum.net

There's a LinkedIn link … to a 404. Ditto for YouTube.

There's no Mastodon handle listed, but there is a Twitter handle … also gone.

x.com/scafaria

This is my account for non-commercial prosocial activities egP8Zk7N - scafaria
GitHubscafaria - OverviewThis is my account for non-commercial prosocial activities egP8Zk7N - scafaria
Public

some more OSINT yields toad.social/@scafaria as an old handle; gone.

The only thing I could find on the web, other than the GitHub, was a Medium account that _hasn't_ been deleted, scafaria.com/about - but only has one short post.

Public

So, take a breath: who cares? People have an innate right to remove themselves. Hell, the EU enshrined that in law.

Here's the thing: this raises some serious alarm bells, for me.

Let’s talk about browser extensions.

Public

Browser extensions sit in a strange position, security- and privacy-wise.

- They have unparalleled¹ access to parts of our lives that the average user is going to assume are fairly private.

- They’re much less audited² than other, similar software (non-web, non-extension software either has a higher barrier-to-entry, triggering users’ own trust expectations; or is less privileged in its access; or has a larger, less-niche userbase who are more focused on that particular piece of software itself.)

(1. modulo some admirable efforts by browser vendors that, to be honest, fall short of the mark)

(2. again modulo Mozilla doing their best; they do human-review some extensions, but only popular ones that are flagged first by an automated process. blog.mozilla.org/addons/2020/0)

Mozilla Add-ons Community BlogOpenness and security: a balancing act for the add-ons ecosystem – Mozilla Add-ons Community BlogFinding the right balance between openness and security for the add-ons ecosystem has been a key challenge. We have some ideas for our next phase.
Public

There have been numerous³⁺⁴⁺⁵ major security incidents related to browser extensions. My hackles skyrocket when something seems even a tiny bit fishy around one — and yours should too.

[^3]: cyberhaven.com/engineering-blo
[^4]: spin.ai/blog/browser-extension
[^5]: labs.guard.io/fakegpt-2-open-s

www.cyberhaven.comFinal analysis: Chrome extension security incident
Public

So, while I do respect this person’s right to disappear, if they’re a real person — I’m also immediately concerned about whether this was even a legitimate tool in the first place.

A quick dig around in the source doesn't yield anything that's obviously suspicious to me; and both versions visible on the AMO match the contents of the respective git tags. o I'm closing this out believing that, yes, this person really did just opt to remove themselves from the Internet; and this really was just a project that died when they left.

Public

But for me, the takeaway was still: the browser-extension ecosystem is a scary place.

We need both more automated tooling _and_ more user-education; because the potential for harm and ease of access are simply enormous.