Ryuno-Ki
@ekis As far as I know, @buttondown is written in Python.
So implementations such as https://codeberg.org/helge/bovine/ by @helge could have a higher chance of adoption.
Or BookWyrm's implementation in Django (although I see issues with the license). Finally FunkWhale is another project with ActivityPub.
Buttondown
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!)
Tim Chambers
Ryuno-Ki
@ekis I have to admit I learned new things, but you got me really confused.
All good now.
she hacked you
@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.
she hacked you
@RyunoKi To be clear it was pointed out that I correctly skimmed this lib folder for ActivityPub and confused a simple client for the AP daemon.
So not much at all would be gained besides simplification and easier future management.
But we want to save instance operators money, and like next week.
she hacked you
@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
she hacked you
@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
Ryuno-Ki
@ekis I did!
Puma and Iodine weren't on my radar before.
I only get nerdsniped by @smallcircles on WASM before so the references to FFI is also something I should learn.
Ryuno-Ki
@alcinnz @smallcircles @ekis Team XHTML here.
I'm more inclined to client-side things. It's incredible what you can build nowadays. And we don't even scratch the surface!
alcinnz
@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...
she hacked you
@RyunoKi @smallcircles WASM you looking at pwa using just the browser engine?
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
small circle 🕊 in calmness
Oww, that is interesting use of servo. Regarding the parsing I may point to work of @alcinnz
For wasm I made some survey some time ago: https://discuss.coding.social/t/solidground-wasm-component-based-development-wiki/367
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.
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.