*Disclaimer – Products & services introduced in this blog are discontinued; check out our ecosystem for current alternatives.
Since when such 'subtle' adjustments softly crept into my social media life: Posted tweets turned inaccessible due to irrational accounts lockup; Accomplished blogs vanished without a single trace thanks to the sudden so-called maintenance; Collected Playlist shifted grey along with the expiration of platform's copyright; Followed public accounts collapsed overnight whilst the contents got blocked and the usernames gone with the wind; Subscribed videos should have been laying peacefully in cozy web couches whereas apart from unscrupulous advertisements the mere stuff left was unreasonable delete announcements...
Shall I hate the platforms? Considering they provide us with a diversity of use case scenarios, perhaps I shouldn't be too harsh on them. Nonetheless, in terms of exploiting users' property for their own profitable capital, imprisoning users in the scope of their services, and monopolizing the jurisdiction of clients' spiritual assets, the remaining respects are long gone. Instead of employing dictatorship towards consumer resources, an optimal platform is preferred, acting as a mere carrier as well as an aggregator of digital contents- for customers themselves ought to be entitled to be responsible for their own options, spreading their own recognition as well as collecting their own preferences. Provided the platform fails to satisfy their demands, they can just switch to another one. Users, at any time, shall be empowered to take away every single piece of the content properties. Most significantly, the output participants produce rather than the enormous scale the platform extends counts, for it brings out restless vitality in a sketch-newly-established platform.
Therefore, during the past three years, I have organized my personal blog along with constructing two federal universe instances; And now, my companions and I, generate RSS3 and programs on the basis of it—Re:ID.
In the world of RSS3, platforms are no longer THE ONE RULE users. In fact, they constitute the heart of our network-Rather than at all kinds of platforms' mercy, COMMIT FOR YOURSELVES; Re:ID offers its customers a compatible layer: Not only can they carry on followings and daily sharing through conventional platforms, but also users are enabled to synchronize messages tweeting on RSS3 network, bursting cross-platform restraints and meanwhile preserving contents of their free will. Furthermore, in response to multi-platform and distinct content composition requirements, we are attaching multi-language/account/platform support for Re:ID, hoping that different platforms may match corresponding accounts. We are developers as well as application users, and users will continuously be the end that drives all demands and all our loyalty directly towards them.
Adopting Chrome/Chromium Plug-in developing strategies, we divide kernel codes into Content Script(webpage injection)/Background Service Worker (as its name suggests)/Popup Page(refers to minor ones)/Options Page, four modules in total.
- Content Script is in charge of anchoring the synchronized button on the webpage while simultaneously mounting hooks for event listeners. As users complete their delivery, the subjects will be automatically uploaded and integrated into the RSS3 Network.
- Background Service Worker currently dominates evaluation regarding whether URLs of the ongoing invoked label page are supported or not, additionally implementing conversion and modification to specific icons.
- Popup Page plus Options Page produce grants and control for users when accessing resources, along with revealing instruction information on webpages; it is quite convenient for users to realize functions such as detecting/registering/inviting.
Given that our network is currently located at the testing stage, membership of a fresh user requires an invitation from those who have participated in the program. Owing to our support for executions on Twitter, you may effortlessly deliver tweets involving your address at one click and wait for invitations to join in. We will also continuously follow associated stamps, ready to deliver our most sincere invitations to every user who wishes to give the brand-new RSS3 ecosystem a shot.
At present, Re:ID as our imaginary prototype already comprises elementary structure/executions/function characters, basically achieving compatibility with Twitter synchronization delivery, also on the shelf of Chrome Web Store, making it more convenient for downloading and employing the steadily constructed version. Our team constantly tries to include support for more platforms, optimization for details, and realization of functions. With the iterations and cultivation of the RSS3 protocol, more accomplishments for content are ever-evolving. Meanwhile, being a liberty-oriented/anti-centralization/anti-investigation software, Re:ID will be maintained based on open source granted by GPL v3. We welcome companions from the community to join our endeavor at any time and carry on contributing to the ever-flawless RSS3 world.
The information turbulence is restlessly splitting our media space into isolated pieces. Monopoly platforms attempt to take every advantage of our resources; they intend to shape us into 52Hz whales that send out companionless calls. Nevertheless, we are no longer solitary; we haven't been solitary. Our associations transcend platform bonds, our values surpass platform restrictions, and we possess what we own from the beginning of our lives: wisdom, passion, and courage; we create what we truly devote to.
If you are interested in RSS3 and willing to contribute to the ecosystem, feel free to reach out to us anytime!