Forest @forestjohnson@pixie.town

@karlexceed eat the luxe

@karlexceed ?

@aynish so the rules can't rewrite the rules?

It looks like it might be really hard to make anything big and do internet stuff on this thing. I can see the coolness based on how simple it is to implement, but I wonder if that comes with a bigger cost of difficulty implementing apps on top of it.

I'm not sure I buy the impetus to throw everything away and restart.

@aynish huh, wait, its not rewriting text is it ? ? It's rewriting some internal structure that the text represents ? I obviously don't get it but right away I'm worried about lack of strong separation between code and data

@aynish what are rewriting rules ?

@technomancy I saw this as more like "providing a builtin ui for gts" or just integrating the two somehow.. I felt like separate server and client webapp would be a needlessly confusing stumbling block if I was trying to get more of my local friends on fedi

@technomancy fry them or just let them sit somewhere dry and airy with space around em and they will ripen before they spoil

@dumpsterqueer I thought you were talking about those memes where people put photos of stereotypical objects that are associated with a certain subculture or a certain identity.

@technomancy If you ever find anyone who has done this or deployed it or packaged it in some way, let me know because I'm curious about it.

@technomancy I had planned on setting this up myself. I never tried using the single instance configuration option for Pinafore, I'd only ever planned on heavily modifying it to deeply integrate with GoToSocial.

For example, Pinofor does not support the concept of modifying your profile, but go to social does. So in order to allow users to do that, I would have to kind of mix and match between two different web applications that link to each other or redirect to each other somehow.

@reese kohls harder cash

@tante

last time I heard about the server load from mastodon being expensive to operate, I heard it's the act of pushing that puts load on the server and takes it down. Not the act of serving, typically. It sounds like serving the static content is relatively easy cpu-wise. But it sounds like the pushing code is still based on a one-thread-per-request model that thrashes the CPU w/ context switches and doesn't work very well unless you have a whole lot of cores.

Something like gotosocial that has proper non-blocking IO would be a lot cheaper to operate on a smaller computer, but bandwidth will always be an issue I guess.

It sounds like you are talking about making a CDN, kind of like how PeerTube can have videos "seeded" by random volunteers on the net ?

Such a thing could even be layered on top with JavaScript, without needing to modify the server

@aynish hmu sometime, I could probably help at least a bit.

@aynish was tempted to recommend looking at some of my projects to get a vanilla js boilerplate if you are interested... until I remembered how jank they were, evolved from a codebase that predates `fetch` , etc etc