Mirror of the Rel4tion website/wiki source, view at <http://rel4tion.org>
Clone
HTTPS:
git clone https://vervis.peers.community/repos/yEzqv
SSH:
git clone USERNAME@vervis.peers.community:yEzqv
Branches
Tags
ideas.mdwn
[[TODO|TODO/OPEN]] move these somewhere else easier to manage…
- Software translation server with an RPC API, allowing desktop UI and web UI to be developed independently. And make a desktop GUI, e.g. by modifying an exisitng PO editor to send strings to the server and read changes from it too. I remember writing more about it somewhere, maybe it’s in sparkle-decadence or still in rdd-wiki or something
- Replace website passwords and “captcha” by allowing people to connect via e.g. SSH from the command line or a GUI program, or the web browser, and then they don’t need a password. For security have a desktop tool which notifies the user when something reads the SSH key, to make sure it isn’t stolen. Hmmm while this can work like Gitolite, does it prevent spam? A spammer can still generate an SSH key. Hmmm… how can I log in to websites with JS off, but without the stupid captcha? IDEA: Use GPG trust and have a network which identifies known spammers. GOAL: Make it work transparently, don’t make web admins waste hours on spam fighting. SSH key idea still good, or even just password - it allows access not from a web browser without JS dependency. The idea is to be able to get information from and send commands to websites without an all-in-one browser application. There would be an API and clients.
- How to make a web service, fr33domlover’s version:
- Make sure there’s a good reason to make it a service, and make sure it’s not more centralized than necessary - preferrably distributed
- Define the functionality
- Define a web-accessible API
- Define the mechanism of using it through the web (e.g. like SQL databases, and there’s CGI, XML-RPC and so on)
- Create a desktop library, with support for batching, caching etc. if relevant
- Create a commandline program which uses it
- Create a desktop GUI which uses it, preferrably with some desktop integration
- Distribute all of this as distro packages (I would start with Debian)
- Is there a good reason to have a web interface? Maybe even just for browsing the content and making simple queries via HTML query forms? No problems, make a web interface. Otherwise, don’t.
- This method will also help make web services only when they’re really needed, and prevent all our data moving to the centralized cloud. Everything should be decentralized and local by default, and anything centralized should be planned well and have a good reason to exist!
- Things to build with this method, where the web service is a Razom database:
- Decision making, like Loomio
- Break down the functionality of social networks into actual problems, and design solutions while trying to avoid the individualism, narcissism and addiction problems all the social networms create
- Federated login: Allow services to trust each other, e.g. by GPG trust, and allow SSH/PGP keys of a user on one serve to be automatically accepted on another. This is somewhat like OpenID, but really federated and decentralized (in case you haven’t noticed, most/all the common OpenID providers are giant greedy corporations)
- Translation server as described above
- Are you beginning to notice a pattern? Everything is basicaly a database with a specialized API and clients which use it! Hmmm… I wonder if this is part of my vision of Razom helping build systems quickly and easily, or I’m just being a dreamer, and have been since the beginning :-) Hmmmm… ikiwiki is not like that. It uses a git repository. Well, could still work: Metadata is in a Razom database/file, and the pages are in a git repo. Yeah, can still work… and ikiwki does have an RPC interface, doesn’t it? I don’t remember.