Working on a logo redesign for the wrapper. Some good shit. Or, it might be bad shit, not sure.

Nice new login screen – check it out here: https://blue.amazingca.dev/login

Nothing crazy added to next version of wrapper, just post quoting. Felt I had to get this one implemented quickly because the app is going to allow the users who don’t directly post using the api to start using the feature. You can view a live demonstration of the feature by viewing this post: https://blue.amazingca.dev/?username=sharding.bsky.social&postid=3jpyxrbn62c2p

v1.1 of Damus is out and it is super fucking sweet. 🤙

yo hey 👋 now you can send posts to bluesky social with the wrapper -> https://blue.amazingca.dev

Psychotic killers in horror movies have a surprisingly good immune system.

Who would’ve thought that decentralized social networks, which generally have less people than centralized ones, would have led to my addiction to social media in the first place. The engagement on these platforms are insane.

Mobile view should look even more clean now. I’ve added a toggle that shows the rolodex content, along with a reply indication for posts in the feed. Yes, and now the thread getter is the next major step for each post. While it is not possible to grab the user followers without authentication, I could add a long-form search based on a set of users that are cached on the client side. From there, it can traverse through each and add detected follows to a counter. It is kind of extensive, but it could get a rough estimate on user followers.

Parent post system is next priority. Might do user authentication, still thinking about it. Atm, the developers at Bluesky are making their web app, so it might not be that useful long term.

While it is possible to implement a posting system on the web app, because it would have to handle the user tokens I have some doubts on safety/security. Obviously they would be stored locally, though I feel the exchange of the user’s handle and password for them should be done at least manually by the user in a client made for those requests. If I do go forward with implementing that, it should alleviate most of the api limitations for users with an account.

The next minor release adds user follows to the profile screen. While that’s the only new feature for now, this one has some slight UI improvements on mobile/desktop devices, along with major foundational changes in the scripts, which should hopefully allow for easier & speedier feature implementation in the future.

I am pleased to announce that my web client adaptation of Bluesky Social's API is now out. Please keep in mind that I have no connection with Bluesky in any way, shape, or form. I just wanted to have some web interface in the meantime. There are a few areas where there isn't enough implementation, but I'd say it does a majority of the things it needs to do. Check it out here: https://blue.amazingca.dev And here's a screenshot for you all:

I have user posts added, though unfortunately it only goes back a short while (around a week). Idk why atm. What I am working on is getting post threads on there.

I’ll get the client on Cloudflare’s servers by the end of tonight.

Bluesky Social’s app just came out on the App Store:

App Store

Bluesky Social App - App Store

Download Bluesky Social by Bluesky PBLLC on the App Store. See screenshots, ratings and reviews, user tips, and more apps like Bluesky Social.

It’s still in public beta though, but it’s definitely progress.

Alrighty, so I’ve got user details imported (currently just handle, name, description, and user follow count atm). Next step is to get that user’s posts in there & add the fancy thread detail view when looking at a particular post.

So according to a post on the platform, the Bluesky Social app is currently undergoing the review process. So expect a debut sometime today/tomorrow. I think that it’ll still be in public beta, as you need an invite code to signup. However, the app will be viewable.

Alright, so I have a “feed” thing imported. Basically it just grabs the most recent post from each cached user. I could do some sorting using ISO timestamps, but that could lead to a feed that changes post interpolation due to interlaced user activity. I’d say this system works fine though.

Here is a screenshot of the current client progress. I don't have a feed implemented yet, but I've imported user DIDs and have successfully implemented a post grabber/a user data retriever <-[SOON].

Currently working on the wrapper! Hopefully, if all goes well, I can get it out tmr. There’s a lot of api methods I need to implement and whatnot.