Show newer

@oblomov
> ... satisfies the first three requirements
After that comments-via-AP service suggestion, I had a thought.

A static website only means static page serving, not the avoidance of JS in the webpage that connects to other servers. If there were 3rd-party JS that could pull from a public AP thread URL into the webpage, all responses to the thread OP (your post) would render on the client without involving your static web server.

@oblomov When running your own blog, I recommend sticking to Webmentions. They're basically pingbacks with Microformats-powered semantics (linkback, reply, author, "like", "bookmark", etc). Fediverse interactions can backfeed into Webmentions using services like brid.gy.

Been using them on seirdy.one for almost two years without major complaints; it lets me add JS-free comments to a static site.

Meanwhile, on an unrelated thread on “the worse microblogging platform” I was pointed to this
withknown.com/

I have to look better at its features, but it advertises “#decentralized #indieweb” features, which already makes it quite interesting. I've browsed about, and it seems that this is based on #ActivityStreams, which apparently isn't the same thing as #ActivityPub.

This in itself made me a bit wary, but looking for information on that, I ended up on ...

“You can pay for a blue check mark with Twitter Blue, but select accounts and organizations will get a gray check mark with an ‘Official’ label.”

Had Twitter not fired its entire accessibility team, they could raise the 1.4.1 Use of Color WCAG risk.

@Seirdy Strong agree on this point. Secure boot is freaking awesome on open platforms. E.g., OpenPOWER. Flash your keys to the chip, boot from firmware you compiled and signed yourself into a kernel you compiled and signed yourself, and maybe finish it off with Linux's IMA and EVM systems to extend that assurance of integrity all the way into a userspace you likewise compiled and signed yourself. Feels good.

@mjd The main reason that moved Mastodon to AP was the support for federated personal messages. The main reason for creating AP in the first place was implementation complexity and clarity.

Arguably it worked, as there were only ever a handful of OStatus implementations but now dozens of AP implementations, but we don't have a control group universe to see if OStatus-plus-personal-salmons (basically Diaspora) would have achieved the same with a similar level of public attention.

@Luke @andyc

After all, how much of Mastodon's ongoing adoption has to do with , which is the part of AP that seems to have interested non-Mastodon developers the most? AP may become worthy of a satisfactory victory lap, but not yet.

@chengdulittlea @mhall119 @cwebber

3/2 ;-)

to federated messaging ( ) didn't happen because there was popular competition in that space from Signal, Wire, Threema.

has had no popular competition. In fact, the upcoming competition cooperates via Mastodon-flavoured ActivityPub even if it is simpler or superior - , , 's micro-blogging version with its magic auth.

@chengdulittlea @mhall119 @cwebber

2/2

No offence, but belongs to Mastodon, not ActivityPub.

With the evident looseness of the spec, Mastodon might as well have evolved from or . Maybe AP can chalk up a win if there is a migration to or something else next, not until then.

@chengdulittlea @mhall119 @cwebber

1/

#FediTip for veterans and other helpful people, click on a post and skim the reply thread before offering tips. Someone (or *many* someones) might have already replied with that tip and we don't want to flood people's @mentions. There's enough of that going on as it is :)

@lechindianer mine too! Such an unfussy, unceremonious, situated communicator, with no airs of being one of the inventors of a boss language.

@thezerobit ow! You make compiling Mercury sound like compiling Rust. Maybe it could do with a no-constraint-programming build for limited use-cases?

I haven't hit SWI-Prolog's limits in my short time with Prolog.

I wonder if there have been any attempts to map terminology to common parlance, and avoid crypto terms in discussions and in software interfaces.

To attest content, the "self-attesting" key is used. Others verify your attestation on content using your published "verification" key. doesn't need to enter the discussion until a common use-case pops up.

@abcdw good clarifications for anybody reading, irrespective of the back-up question.

For conversations (properly) using PGP encryption, you anyway have to "process" e-mail (bodies) locally. How is PGP integration in 'notmuch' (and 'gnus')?

Can't PGP fingerprints be encoded into shorter strings like YT video identifiers, but not case-sensitive? Somehow get usability of PGP fingerprints into the ballpark of phone numbers.

I'm growing convinced that people who dislike the extremely efficient email-based workflows we'd grown over decades, and prefer web-based interactions, have been trained to mistake the webmail abomination for email. webmail sucks even more than other apps in the wwworst app store, but having patches sitting on your local machine (where email was delivered asynchronously) for you to deal with in scriptable ways... that's priceless

@abcdw I do wonder if 'notmuch' (and 'gnus') users have more of a back-up ethic than webmail users. I don't know the pre-webmail era, but wasn't it there? E-mail back-up may not have been as big a deal then, since there were no online transactions or e-mail ID used for service log-ins.

Yesterday I followed @ulfurinn just to see if it would work. You see, that's not a Mastodon account. It's a Pixelfed account, a photo-sharing app that — like Mastodon — is part of the Fediverse.

And it does Just Work. It's like having someone's Instagram posts show up in your Twitter feed.

The Web as it was meant to work!

Show older
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.