Filling the Gaping Hole: now, me too!

The Chronicle of an Actually Relevant (p2p) eX-Cheerper Remake

Social platforms are being replaced by GVO co-entertainment (strictly good vibes only) apps, they’re just much more profitable. I fear the next for deconstruction will be e-mail; it‘ll take some more time, because it’s a bit older and the providers are much more diverse, and oh, it is based on something we cared to make global standards for (back when we thought human communication was really important for the masses), anyway, we’ll better hurry with replacements, yeah?

This story will be updated as any progress is being made. The end result will be a completely self-sufficient system implementing the major functionality of the departing service. The system will be implemented as several self-server comps which are nothing more than container “composites” that need some container host configuration and depend on some “core” and “std” comps of self server. The code shall be peer-sourced (not open-sourced), as it is standard with the platform (you’re welcome to be in touch with me personally), but important excerpts shall be published here.

Day 0

So, first of all, I have to thank the snowflake idol, the progressive progressor, the one and (thanks god) only Muskman, for helping to kill’em “social platforms” of the past; the classic Cheerper is biting the dust…

https://costashapiro.com

*CLICK*

…and clearing the scene for the next big thing: the real social platform, with any and all social systems or applications actual social users may have (1) an actual need of, and (2) collective resources to dev.

And now — thanks to our unanonymous friend — what could be a better place to start — well, after spending several personal years on:
a personal automation / person-to-person platform, that is the self server
— than with implementing the trivial (textbook!) social app for it!?

So yes, I have an actual need of the “cheerper” functionality (see above), and yes, I also have resources to dev (a few work days of mine), but I used to think it was too trivial for people of the day, and now… it doesn’t only look “advanced”, it’s even actually dead relevant as well!..

I’m calling the user-facing comp “upd”, because you “upd”ate others on stuff with it, and then, you keep yourself “upd”ated of others’ “upd”ates, right? I might even make it “std” with the self server distribution of mine.

…specifically, with:

• a 2-way-sync (“drv”) comp “xwitter”, for the smoothest user transition:
  in human language, this means that you can have your cake and eat it too; you can be in both systems at the same time, with this comp having both your eX-Cheerper account and your “upd” comp mutually updated in near-real time;
  this will entail integrating eX-Cheerper API — not resorting to Selenium- based scrapping, hopefully
• an authentic WUI for “upd” — a self-prescribed exercise of crafting an advanced React component — it will look minimal and be e-a-sily better than ex-bird’s (ads-optimised apparently):
  it’s a surprise, it’ll be awesome, no details for now, stay tuned for release
• the backend will be git, which is fully integrated for p2p work in the self-server platform already:

git decentralized

Yes, just git, with all the comp’s user interaction fitting in its semantics, e.g. if each user has a repo with a “username” branch for their “μlog” and following peers’ remotes (with their “username” branches), then, I’m not sure about likes, but shares will be implemented as cherry-picking other’s “upd” commits, and such an “upd” will just be an HTML fragment file (potentially containing references to [URIs of] other “upd”s).

Then, done!
The damn thing is ready for millions of users! Billions! $)
That’s because the current platform revision is enough for this kind of p2p (peer=person) comp already — while a big media sharing support is in the works still, but since it’ll be just extending the platform’s git integration, this checks out.

You see, the only really challenging part about the Cheerper technology was its infra and ops (“sysadmin” in the old money). The self server, a distributed “0-ops” platform, takes this complexity away and makes the trivial Cheerper concept a highly accessible “primitive” software piece again, as it should naturally be.

The suggested development not only opens up many interoperability options, since we’ll be using the industry’s standard for “formalised” co-operation (git), and keeping things primitive: e.g. tagging may be implemented with directories of softlinks in the repo FS.

…And then, in no time, eX-Cheerper will be totally depopulated of human users, with only crawlers and bots then roaming the underloaded Muskman’s servers, while humans will enjoy truly secure communication — with no one but themselves responsible for it — indefinitely.

p.s. Interested devs are welcome to ping.
p.p.s. Now, which platforms should I use for the two comps? But before that, the next step is tech shopping: as mentioned, UI (“upd” comp) will be brand new and authentic, on Node+TypeScript+React probably, but let’s see what public resources I can find for the sync’ing “xwitter” “drv” comp…