Here's that #ReadAs demo instance, running the just-released v0.2: https://readas.labs.abunchtell.com
Once v1.0 is finished, I'll put it up on https://Read.as and open up registration to everyone.
#Microblogpub blogs can also be followed with #ReadAs, and should handle posts without any issues (still need to test). But existing posts aren't pulled in on follow either, because of how the outbox is set up.
Going to need to fully use go-fed for outbox parsing, instead of my currently hacked-together (and much less robust) solution.
#ReadAs getting close to a point where I can throw up a demo instance.
✅ Pulling in a user's existing posts when you first follow them
✅ Fixing post viewing when not logged in
✅ Fixing database schema so it can eventually support posts from both local and remote users
- Typography improvements
- Instance configuration with JSON file
Okay, the issue with Pleroma should be fixed now on my end. Will test again once I've made a few other fixes.
This is just a small test to see if the post shows up on #readas.
Roadmap and current progress on #ReadAs here: https://github.com/writeas/Read.as/projects/1
As soon as v0.2 is out, I'll start creating issues that'll be up for anyone to grab. If you're interested in helping with development or documentation, let me know!
Okay, #readas schema looks better now -- all users in the same table, and the domain discovered on the webfinger request is used, for Mastodon instances that are hosted on a different domain than the one used in user handles.
A few more things I'd like to add on Write.as in the near future:
- Auto-linking fediverse handles in bios (need to resolve handles to fetch profile URLs; store usernames)
- Support mentioning fediverse users (resolve handles, send mention activities, shorten and link handle URL)
- Make canonical handles more discoverable on custom domains (searching for something like @blog@example.com returns correct @handle in webfinger request, or whatever will make this work)
After I get these changes in (mostly around the database) I'll throw up an instance so I can start testing with #Plume and microblogging platforms. But so far everything works great in my testing with Write.as
Now Update and Delete activities are handled on #ReadAs, and requests are being verified. Going to mark this as v0.1 and move on to:
- Pulling in a user's existing posts when you first follow them
- Fixing post viewing when not logged in
- Fixing database schema so it can eventually support posts from both local and remote users
- Typography improvements
Part of the fun I have with this is figuring out how to build a simple application in as little time as possible that's still useful from day 1 -- and after some thinking I figured it out.
So v0.1 will have a GUI only for the primary use case: reading things. It'll eventually be multi-user (schema is set up for it), but single-user upon release. And to do anything besides the primary use case, you'll use cURL or Postman or whatever to call the API.
Last night got the database schema worked out to handle everything that'll be in the MVP and versions after. Today have been adding the API layer and bringing over code I needed from Write.as.
Casual dev-related updates from @write_as / @writefreely, tooted by @matt.
This account isn't super active. You might want to check out our other profiles!