After poking around more, I thiiiink we can do something here using Mastodon's built-in APIs pretty trivially. Not quite the same thing as an unopinionated ActivityPub bridge, but as Andy said RSS works as an interface for that for folks who want to get technical (whereas I think most folks just want to be able to auto-publish toots for their new issues!)
@buttondown Mastodon implements ActivityPub as a `{rails}/lib/*` essentially where you store code very specific to your project or, more likely, code that has not yet been encapsulated into a Gem yet
Just moving Mastodon's AP client usage to a Gem. It would 1 step away from switching out the client with for example a compiled rust implementation instead of makeshift interpreted Ruby
I love Ruby, but its also important to understand how these systems work; the cost to instance operators is alot
@RyunoKi@buttondown@helge Those two changes and possibly the {rails}/lib/.* going into its own Gem package would mak a solid patch to help the majority of Mastodon instance operators which use the vanilla RoR Client.
Expecting them to all switch servers at this point that quickly is just not realistic, have to bridge the gap and make it easy.
@RyunoKi@buttondown@helge Honestly both Django + Rails client would be better served using C, Rust, whatever is the most mature, stable and will guarantee feature parity b/c we dont want to cause any feature loss (One reason Iodine needs Puma stats like additions to it)
I have limited time but I could walk someone through converting sidekiq to just redis+rails workers. That + switching to iodine would be very significant for very little work. Will see statistical significant measurements
@RyunoKi Wait you learned new things? I learned new things!
We need to be coordinating on definitions clearly defining problems by what is solvable quickly and with the most reward, and ideally release it as patches for instance operators to try before trying to get it pulled in again.
Id hate to have said something stupid confusing you because I was upset in general not at you and failed reading comprehension of your post.
I'm very far from perfect, but A LOT of ruby/c/rails/rack exp
@smallcircles@ekis@RyunoKi Regarding HTML parsing, I didn't write *that* bit myself. But I do like HTML Conduit's approach! Then again if you're writing in Rust, you'd probably want to use a Rust lib...
tl;dr; With XHTML's legacy, I don't think WHATWG-standard error correction is worth it. At least anymore! As long as you didn't *totally* fall over upon poorly-formed markup...
I'm working on a UI system that utilizes just servo since it functions as a stand alone render engine; I was to the point I was writing my own lexer and parser for HTML just never rendered the nodes. Continued experiments with JS off for the time being; but like srvo or pwa options
I'm interested in server-side use mostly, but some impressive experiment is Makepad, that offers a Figma-like DSL for complex UI. In their conference vid multiple apps are live-embedded in their presentation slidedeck.