

Checking about getting it updated.
Mostly @andypiper@macaw.social on the #fediverse - more links here.
Keyoxide aspe:keyoxide.org:JQTSX3JMH2G6U6UAUH5VPUP4SE
Checking about getting it updated.
there’s a big difference between running a service on volunteers, and having full-time folks to keep things running / answer the regulation discussions / keep maintaining / keep adding the features that folks are looking for. This is not primarily an infrastructure spend. There’s also an amount of legal work involved, unfortunately. So, those are some of the elements we’re looking at.
These are part of the assets that will be transferred from the GmbH to the non-profit.
I wrote about this on my blog. I like the notion and points made here, but I also think we’re not helping by re-inventing things that already exist, so I’m torn on it. I have been happy with the existing one.
“new” == ~3 years old (but looking to move from alpha to beta in 2024 IIRC). It’s a good server!
Built and using it - lots of fun. https://dev.to/andypiper/getting-arty-with-a-pi-3dk9
I think forcing all posts to be opted-in to the search, and depending on users to opt-out, would be far more controversial? Either way, the user does get to control this within the platform.
There’s also a really nice deep dive into the updates here.
I wrote a blog post about using Postmarks and contributing to the project https://andypiper.co.uk/2023/09/11/bookmarks-in-the-fediverse/
At the moment it is explicitly designed as a single-user implementation, although I’m sure it could be pivoted to become multiuser. I’ve simply set up my own on Glitch and it is working great! -> https://pipesmarks.glitch.me/
understandable! No problem, just thought it could be useful, but realise you should make those choices carefully.
You can use the Graze browser extension that will help with this.
This is hilarious and I am here for it. They can’t pay their bills, can’t imagine they have funds to get a legal case together.
Do you mean you’re trying to access Threads’ ActivityPub endpoint(s)?
I’m pretty certain that you have to use signed requests, and bear in mind that not all users have federation enabled.
I just confirmed that by using the
fedify
CLI to test. Runningfedify lookup andypiper@threads.net
fails, but withfedify lookup -a andypiper@threads.net
(which spins up a local server and performs authenticated requests) I get back JSON from the WebFinger endpoint.You’ll probably get some folks able to share their experiences integrating / testing with Threads federation in some of the Fediverse Developers related Matrix rooms.