posse — julian

Review: Sistema Twist & Sip 600 ml Bottle

Thu, 16 May 2024 09:10:01 +0000

The cap leaks, from new, so unsuitable for carrying in a school bag. Now the bottom is cracked and leaking too, as soon as dropped from ~1m carrying heigh on its first morning going to school. Pointless.

We're better off just re-using any ordinary “disposable” drinks bottle.


600 ml size — leaks, cracks, pointless	380 ml size — also leaks

Both bought from Tesco, 2024-05-15.

POSSE — posted reviews on tesco.com

2024-05-15 First review (2 star: cap leaks).
2024-05-16 Second review (1 star: cap leaks, cracked on impact, as above).

#POSSE #review

Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @julian@wrily.foad.me.uk · matrix me · Fedi follow me · email me · julian.foad.me.uk Donate: via Liberapay All posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise

POSSE: TWIM: Moderator Tools for PubHubs

Fri, 29 Mar 2024 19:30:00 +0000

This is my POSSE copy of the announcement posted in This Week in Matrix (TWIM) 2024-03-29.

This Week in Matrix 2024-03-29

Dept of Interesting Projects

Moderator Tools for PubHubs

JulianF announces

This week I have put up a web site documenting my work on Moderator Tools for PubHubs.

PubHubs is a Dutch research project to enable citizen-facing organisations to provide online group communications, value-aligned with their real-world presence. It uses matrix protocol, combined with an interesting and different user identity model involving pseudonyms and selective cryptographic disclosure of identity attributes such as “is over 18” or “is a member of organisation X”. Each hub is built around a non-federating Synapse server, with their own identity plugins and custom client.

I have been working on three aspects of introducing initial moderation tooling. Some of it crosses over with general matrix (this week's Pantalaimon role is a side product of the Draupnir part), while some is different (Attribute Disclosure), and the third part is general (research and planning for Civilised Discourse).

My funded stint is coming to an end and I am looking for ways to continue in any related area of work — please matrix me @julian:foad.me.uk!

#PubHubs #matrix #POSSE

POSSE: TWIM: Pantalaimon role for matrix-docker-ansible-deploy

Fri, 29 Mar 2024 19:00:00 +0000

This is my POSSE copy of the announcement posted in This Week in Matrix (TWIM) 2024-03-29.

This Week in Matrix 2024-03-29

Dept of Ops 🛠

matrix-docker-ansible-deploy (website)

Slavi announces

Thanks to Julian Foad, matrix-docker-ansible-deploy can now install the Pantalaimon E2EE aware proxy daemon for you. It's already possible to integrate it with Draupnir to allow it to work in E2EE rooms – see our Draupnir docs for details.

See our Setting up Pantalaimon documentation to get started.

#PubHubs #matrix #POSSE

Fediverse-Ideas #41: Bring Your Own IDentity (BYOID)

Sat, 23 Sep 2023 13:41:00 +0000

POSSE: I posted this in “fediverse-ideas” as Bring Your Own IDentity (BYOID) #41, on 2023-09-23. Comments are included below.

Related to development of all social (people-focused) communications and sharing systems, fediverse included.

Own Domain

We can't build people-oriented social tech in the way that Big Tech do, where they say “this is our system, you'll have an address @ our-big-tech-domain, and all your links belong to us.”

Earlier today I replied to Johannes Ernst who observed that people shouldn't need to think about the difference between someone's fediverse handle and their email address, they should be the same. I wrote,

@J12t Absolutely! We should just need “my address”. I've been writing about aspects of this. And it's strongly tied in with the value of having one's own address at one's own domain. Don't want my email addr to be me @ mastodon, nor my fediverse to be me @ gmail :–) rather I want them both me @ my-domain. And to make that efficient and affordable, servers (and server operators) must support Bring Your Own Identity #BYOID .

https://wrily.foad.me.uk/tag:ownDomain

Own Domain is a truly cross-platform issue. It applies to matrix just as to fediverse and others. It's about bringing the person to the centre.

A recent key insight I had was actually “my own” registered domain isn't necessary. A substantial part of the value is in having an address at a domain that isn't belonging to a particular one of the service providers we use, but in having the use of an address at a domain that belongs to someone, anyone, whom we trust to let us use it for the long term. Could be a company, one's government, a charity. The key is to be able to switch and mix service providers without borrowing a new and different address from each one.

Main issues include:

getting server software to support BYOID
getting server operators to support and encourage BYOID (and adapt to doing their brand recognition a different way)
making domain registration easier and cheaper and reliable for ordinary folks (includes sub issues such as: facilitating subdomain use, see Public Suffix List)
making domain management easy, standardised, automated, at least as far as enabling providers of matrix/mastodon/etc. be able to plug in their service to my domain with minimal effort on my part)

I'm presupposing, by bringing up this topic in this forum, that a majority of readers here will understand the reasons why this direction makes sense. (That's something I have tried to write about on my blog but, though I try, explaining and appealing to normies to understand the importance is not my forté.)

I feel like we're missing something, that having all my different protocol addresses matching isn't merely about being easy to remember, it's not a trivial nicety. It's somehow a key to building deeper integration of our personal data within our personal tech. It's hard to think of use cases that can't be achieved by linking to external sites the way we do now, but my intuition is integration can be done better this way.

And I think BYOID goes a huge way towards solving the account “portability” issue.

Yet our delightful new federated things, wonderful in themselves, are yet, still, being built as big tech mono-sites: “join us and get our lovely service at our address” (mastodon.anything, fedi-thing.whatever, matrix-circles, matrix.org, beeper.com, on and on add infinitum).

Only a few rays radiate in the right direction:

ye olde email (BYOID is widely available)
Blue Sky spec (but, sadly, not the blue sky central server)

(I thought I'd be able to name more.)

Running the service oneself, be it email or fedi or matrix, isn't easy. I self-host only in order to bring my own domain, not because I want to. Currently without self-hosting I explain it as I'm Unable To Be Me .

Discussion:

Social Coding FSDL matrix room #socialcoding-foundations:matrix.org (alternate link)

Idea #23 Domain names as handles

(EDIT 2023-12-23: Typo “people should –> shouldn't need to think”.)

glyn commented 2023-12-12:

Another advantage of BYOID would be to retain one's identity when migrating accounts between servers, as happens in the fediverse.

I can see the attraction of using domain names as identities as it leverages the current DNS infrastructure. However, it seems that the requirements for BYOID are fewer than those of domain names, so a much cheaper solution could be found.

Have you looked at identities via keyoxide.org and similar technology?

circlebuilder commented 2023-12-13:

FYI There's an issue on Federating Keyoxide.

glyn commented 2023-12-21:

One aspect is puzzling me. How would BYOID work when applied to more than one type of ActivityPub service, e.g. microblogging on a Mastodon instance and photo sharing on a pixelfed instance?

For example, if I used BYOID on both a Mastodon and a pixelfed instance, which instance would my id refer to? Or, putting it a other way, how could I refer to myself on one or other of the instances?

julianfoad commented 2023-12-23:

@glyn: Bring Your Own ID does not mean we have only one ID we can bring. We can still use a separate ID for each service. Let's say my preferred handle is “julian”. I can bring “julian@toot.mydomain” to the microblogging service, and bring “@julian@pix.mydomain” to the pixelfed service. (Or any other format that works, perhaps “@julian+{toot,pix}@mydomain”.) The essential point is that these ids are under my control (perhaps delegated to some third-party of my choosing) rather than controlled by the provider of my “toot” and “pix” services.

So, that's the first level.

In addition, I also write about how I would like to use one and the same ID for multiple services, here and in some of my blog posts. That's a more involved thing than Bring Your Own ID. I would like to explore that further but haven't yet, beyond observing that the syntax differences across different protocols (like whether to write a leading '@' sign) are superficial.

#ownDomain #POSSE #fediverse #matrix

POSSE: TWIM: UnifiedPush notifications for your Matrix server with ntfy

Fri, 08 Jul 2022 20:18:44 +0000

This is my POSSE copy of the announcement posted in This Week in Matrix (TWIM) 2022-07-08.

This Week in Matrix 2022-07-08

Dept of Ops 🛠

matrix-docker-ansible-deploy (website)

Matrix server setup using Ansible and Docker

Slavi says

Thanks to Julian Foad, matrix-docker-ansible-deploy now supports installing the ntfy push notifications server for you.

See our Setting up the ntfy push notifications server documentation to get started.

JulianF adds

To explain what it's for: Using the UnifiedPush standard, ntfy enables self-hosted (Google-free) push notifications from Matrix (and other) servers. Especially useful for users of Google-free Android (such as from f-droid).

If you try it, please report any feedback or problems or improvements in #matrix-docker-ansible-deploy:devture.com . Any updates to the scripts or docs may appear first on my branch before being merged into the playbook.

#degoogled #matrix #unifiedPush #POSSE