@louis I’m always conflicted about #LispWorks. They have some fantastic affordances but the Hobbyist license fees are higher than most “professional” tools. Certainly more than I can justify for my scale of projects just to not have them time out. And multiply by not running the same platform on my laptop as on the server in my closet.
To be clear, I’m not saying it’s /wrong/ per se; the economics are what they are. Just sad that it prices me out.
@curtosis I feel you. I had the same thought process for a full year until I finally decided to push the button for a LW license. While I love FOSS of course, LispWorks is a damn good product in the realm of Common Lisp and I can testify to that without hesitation.
And it is a very small company, not a greedy stock corporation. I have confidence that with my license I support actual human beings who work to put food on their table and have a passion for Common Lisp. And so far my experience with their team was above board.
@louis I'd be beyond happy to enjoy the full functionality of LispWorks and support such a passionate company. And I fully understand the company's rationale for that pricing. Still, I simply can't justity spending that much money.
@galdor@screwtape The protocol ActivityPub is used mainly for server-to-server communication.
Clients, like the Web UI, must use whatever API the server offers. With Mastodon it is the Mastodon REST API (which is also mirrored by some non-Mastodon servers).
The REST API is fine, it allows for fetching for max. 40 statuses per request and you can work your way backwards in the timeline. But Mastodon has some severe rate limits built in so a client has to handle that.
So, when I use the REST API, which I did with the CAPI example, it only takes under a minute to fetch all my posts back to 2022.
The problem is 1. the Web UI and 2. all the other native apps that are built around the concept of a "Twitter-like" experience. So far I miss any client that is built around a more professional feature set so that a user can manage their own posts and conversations.
I'll probably continue to work on my CAPI UI a bit and share status until I reach a shareable state.
> "Or, we could just build our own Mastodon client with Common Lisp."
@louis this would be my solution. Although I would go with Guile Scheme instead of Common Lisp, because of Guix packaging. And I would make a server too, and make it more like Kbin where you can do both Mastodon and Lemmy like posing.
Add comment