#Pterotype V2/#ActivityPub PHP library update: implemented object persistence and RSA signature generation/verification. Now on to the bread and butter: an elegant API over the core AP interactions
shameless self promotion, computer security Show more
an article i authored about some tips and tricks for using KeePassX =)
oh my god this is the cutest username/password UI I have ever seen
This is a portrait made entirely from vanilla HTML and CSS - no SVG, no frameworks. It's crazy good.
Cons to the generic server approach:
- I don't want to let down the folks who have already invested their time and energy into the WordPress plugin
- the ActivityPub domain wouldn't necessarily match the content domain, e.g. if I have a WordPress instance at example.com and installed a client, the AP actor associated with my blog would live at the domain of the AP server instead of example.com
- users would have to either self-host the AP server or find a person or service to host it for them
The pros to the generic server approach:
- one identity for all your content via many different client apps (one similar to Mastodon, one a WordPress plugin, one a Hugo plugin, etc.)
- much easier to debug a system where there is only one correct way to host it, as opposed to trying to build an AP server on top of WordPress which can be hosted in a million different ways
- By implement ActivityPub C2S, existing clients can use the new server really easily
I'm wondering if I made the wrong thing with #Pterotype, and I'd love some feedback.
The problem I was trying to solve was how to put WordPress content on the Fediverse, but more generally I want to put all sorts of content on the Fediverse.
I'm starting to feel like the best way to achieve that would be by making a generic #ActivityPub client & server implementation, rather than a WordPress-specific server. Then the WordPress plugin could just be a client to the server implementation.
I trained a neural network on 1,228 types of cookies and apparently these are what cookies sound like to it.
hot take about business and making money on the fediverse Show more
Implemented querying for my #ActivityPub #PHP library - it supports recursive querying for arbitrary fields, e.g. "find all the Notes that are attributed to Actors with the URL "example.com". Next up, updating and deleting objects in the ActivityStreams graph. Then on to signing and verification, server-to-server delivery and a friendly API tying it all together.
Software engineer in #Boston.
Currently working on #Pterotype, a WordPress plugin that puts your blog onto the Fediverse.
Into: procgen, music, fediverse
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!
Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!