Incidental Remarks

@chrisgerhard

Learning, init.

Still so much CSS to write…

It would seem like it’s time to buy a case.

Filled a small paddling pool to try and cool the dog down this morning. She quickly drank as much of the water as she could manage, spent the following hour puking most of it back up, and now has a near constant stream of piss coming out of her.

Fediverse followers, note there will still be a fair bit of testing spam coming out of this account while I work out the kinks of my Gotosocial<==>Hugo nonsense.

Still, it will all be fine when the tanks are powered with electricity.

This death, like the rest, is a baked-in consequence of our choices.

From road laws and enforcement, through infrastructure design, right down into the setup of our communities, and the function of modern living being designed around the necessity of flinging multi-tonne juggernauts around the place just to go about your day in any normal fashion.

And collectively, we’ve decided it’s fine, for example, to have hundreds of Panzer tanks driving past schools every day.

Suddenly I had this thought today when pondering using different writing tools. Looks like plenty of people do it so might give it a go. Keep the writing completely separate from the website. Decoupling all the things.

Webfinger (and similar systems) can store meta data about an actor, but we seem to only use webfinger for endpoint / uri discovery.

My understanding is that we ask a social media server (e.g. a mastodon instance) for the ActivityPub outbox for “@user@server.com” and maybe some other info.

But I’m sure it can store anything we like, so why not social graph stuff? I’m mainly thinking about connections and interests.

E.g. mine would list all the ActivityPub accounts I follow and then a list of topics I’m interested in. Then everyone in that list who I follow would have a file that did the same.

Why then, can I not query these files for all ActivityPub accounts, up to 4 degrees of separation away, that are interested in Cycling or Football?

I feel like the fediverse in missing a trick. It’s a halfway house between an algorithm on-boarding you and the cack-handed manual discovery that is being relied on currently.

But this is such an obvious thought, I must be missing something.

Images are working and so are @basil mentions.

Think I’ll call that a night before I break something.

My days are spent on handover meetings and writing half finished thoughts and observations in a wiki. It’s a hoot.

Perhaps the compromise is to copy the files between the folders on the server.

And upload them to the repository.

But omit the images from the rsync to the server.

Removes one leg of the round trip, and keeps the repository source completely intact.

When dealing with images I upload here, I need to send the images from Gotosocial to my Hugo blog.

Do I maintain the purity of the Hugo GitHub repo even though it’s a wildly inefficient round trip? It’s basically moving an image file from /gotosocial/storage to /var/www/images but via GitHub.com

Do I just make the Gotosocial code copy the image to the folder I need it, meaning the Hugo site is not fully self-contained in GitHub. I.e. I can’t just clone the repo and run Hugo to have a fully functional and complete site.

The Dev team at CurrentEmployer Plc consists of 5 Devs of varying abilities. 4 of us have been at the company about 12 months and 1 guy about 6 years.

This person is leaving and so obviously there’s a tremendous amount of knowledge transfer and documentation that needs doing.

Déjà vu all over again. Single points of failure and institutional memory.

Oh, and of course we’ve been told that managing a smooth handover is the absolute overriding priority* for the team.

*but existing priorities are also important and should not suffer.

There she is. (This just drives home the point that I need to get attachments working)

And, in theory, it should handle fediverse replies as well.

I would like to have it infer when something is a response to an internet article, e.g. Detect if the first line of a post is a URL, in which case assume the post is “in response to”.

What’s also not done yet are deletes and attachments.

Deletes should be simple… Media attachments… Not so much.

So, if it’s all working…

This is a post written in tusky, that Gotosocial will create in its own database.

It will also send the post info to my GitPubHub endpoint, which will build up the markdown for the note and send it off to GitHub.

Where a job will be triggered to build and deploy the Hugo site with the new note.

This is the first reply sent by my github publishing webserver endpoint

This is the first note sent by my github publishing webserver endpoint