An expat Canadian, confusing Brits for more than a decade. Grab a chair; he's just gettin' started.

Block / Report User

If this user/feed is violating this Pod's (nfld) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@jlj does not follow you (they may not see your replies!)

Recent Twts

Recent twts from jlj

 (4 days ago)

@prologic@twtxt.net (#oeax64a) Good points, on all fronts. :-) Not suggesting we need redundancy, btw; just that it’s a part of resiliency, itself often part of a decentralised network that has some sort of service level agreement, or similar expectation.

 (4 days ago)

(#oeax64a) That said, though, there is no redundancy whatsoever. I haven’t spent enough time in this space to know how much redundancy/replication and federation are supposed to be a part of any and all things decentralised. I mean, there’s a network’s ability to sustain attack on its infrastructure, and then there’s its ability to maintain the pseudonymity of its clients, writ large and under such attacks. So, in a nutshell, maybe I am using the term incorrectly when talking about yarn.social. :-P

 (4 days ago)

@lyxal@twtxt.net (#oeax64a) Nice! I’ve had that ‘push-back’ about decentralisation as well, in response to my using it with yarn.social. I wouldn’t say, by extension, that all open source projects could then fall under that definition, since, starting with the simplest argument, not all projects are code that’s to be self-hosted and publicly-facing. But, even beyond that, many of those projects won’t be designed to ‘federate’, in the loosest sense. And I think yarn.social does federate in that sense, and is therefore a valid example of a decentralised social platform.


I’m now running yarnd! A small – but very exciting – step forward for the rebranding! :-)

A very smooth transition, @prologic@twtxt.net, FYI. Cloned the new project, built it, set up new symlinks, decided to create a new systemd service, stopped the old one and started the new one (pointing at the same pod instance).


(#4xjds2a) @prologic@twtxt.net I’m assuming you’re talking about LibreTranslate: self-hosted is actually their preference; or at least registering an API key with their instance.

I’m actually thinking about running my own instance; ‘cause I have lots of free time. 🙄😉