15:48

Mastodon Front-end

Mastodon and other Fediverse instance Front end
Great for when you have an instance that have no front-end, like in my case a GoToSocial instance.
15:32

So it appears I’m already listed in Fediverse observer: fediverse.observer/∞

14:18

My #GoToSocial instance has been running for less than a week, and the folder is using up to 1.7Gb already. I wonder how are the other users’ experience so far? #Fediverse #Mastodon

14:18

My #GoToSocial instance has been running for less than a week, and the folder is using up to 1.7Gb already. I wonder how are the other users’ experience so far? #Fediverse #Mastodon

09:31

Tried many todo/tasks app. Even selfhosted: Vikunja, Tududi. But I still keep coming back to RememberTheMilk. Why?

21:07

Touchdown #Iloilo Touchdown #Tigbauan

00:04

Next steps with Bluesky - hosting your own data and more on the API

The thing is, ATproto/Bluesky have been growing a lot lately, and things have moved on very fast. Everything in that previous post still holds up and works, but there have been some interesting developments that warrant an update, namely: you can now host your own data. It’s pretty straightforward too. It does have some implications for working with the APIs, which I’ll get to shortly.
More about the Bluesky API.
00:00

If you own a domain name, why would you wanna keep your #Bluesky handle at @username.bsky.social?

23:56

A 'Hello World' for bluesky/the AT protocol

I’ve documented my baby steps with the protocol below with a few examples - essentially: authenticate, post a “Hello World!” skeet, then reply to that skeet (no, I don’t know why they’re referred to as “skeets”), and get some author information. I’ve done these initial experiments with Postman/cURL, so that I didn’t have to faff around with setting up any sort of language or framework tooling. After all, it is just HTTPS. Hopefully you can translate them into your tool of choice.
This could probably serve as a documentation of the Bluesky API.
23:12

One day, I’ll finally take #Proxmox for a spin—because why settle for simplicity when you can have a full-blown virtualization playground?