About the auth app.
I think we can get some basic thing up, for test purposes. It could serve as a template for developers, to already now give a general direction for what principles to design around.
6 Likes
Maybe Mirror the Github site from CodeBerg? It’s quite easy in fact. CodeBerg is essentially a Github lookalike from the UI perspective so learning curve almost flat.
Get the six admins to sign up for CodeBerg its free, then mirror the Github repositories of your choice?
That also goes for Autonomi generally doing the same?
More censorproof to be on two separate systems.
Codeberg is based in D, so any suppression or shutdown action driven by a govt or party political agenda via the D govt will take for ever and that slowness buys the hosted party some time to move things.
MS with the US govt behind it, can be quite swift, if they decide they want to shut anything down.
2 Likes
D?
Where is that?
germany .de?
Anyway I have signed up with Codeberg and will have a nosey
2 Likes
One thing I like about Git repositories is they are inherently decentralized. Every developer has their own copy on their local machine. Of course, Git repos aren’t for tracking issues, hosting a wiki, CI infrastructure, etc.
Does Codeburg allow you to leave and make it easy to keep your issues, wiki, etc? I tried finding documentation about backups and migration away from Codeburg (and also Forgejo, what their platform is based on). Documentation about backup/restore seems scarse.
I try to consider the angle of vendor lock-in. For example, to my knowledge, cloud-hosted Gitlab supports backups & migrations to a locally running Gitlab instance. And, to avoid self-hosting unless Gitlab does something egregious, it’s possible to make backups from time to time (maybe even store them on Autonomi). So if there ever is a ban from the platform (which I’ve seldom heard of), at least there is the option of self-hosting.
I see Codeburg bans users, enforces a Code of Conduct, can take offense if you don’t ask permission before your project consumes resources they deem too much, are highly opinionated on licensing choices (e.g. recommending against “permissive licenses” like MIT, CC, etc) - their Terms of Use explicity forbids licenses that haven’t received the blessing of the Free Software Foundation or Open Source Institute.
For now, I’m not convinced the chance of bans on Codeburg is lower than Github.
2 Likes
The point is adding a mirror reduces centralisation whether Codeberg are better or worse. If they are in the EU, that’s a big plus because we see Microsoft cutting off services in response to USG actions (cf. ICC).
There’s also this:
GitHub, as all centralised services was always going to go bad one way or another and I expect it to get worse.
Mirroring seems a wise precaution at this point.
2 Likes
Something like this:
Keystore Daemon: User Guide
Keystore Daemon For Developers: Architecture & Protocol
A peek on main.rs.
I haven’t tried running it yet 
But I’ll write some tests to see that it’s working.
4 Likes
We should be careful not to be too prescriptive, imo.
Half the fun is just hacking away with code, then finding areas to standardise on.
Granted, I’m probably not really committee material, but we should bear in mind that autonomi is overtly decentralised. Alignment where it makes sense is good though.
I remember REST won out over SOAP because of the simplicity of the former. Herding devs may be like herding wilful cats. Some just want to do their own thing and are all the better for it.
5 Likes
Moi? 
Both are useful.
2 Likes
Agreed, we definitely don’t want to introduce more overhead than necessary. That said, right now the only controlling force is MaidSafe and the Autonomi foundation. We have a decentralized network with really just one organization calling all of the shots. So the idea here is to define a process that we as a community can use to manage the network and application level proposals as they come in. Today, if MaidSafe disappeared, we would be screwed. We do a lot of talking on the forum, but we aren’t in a position to take this thing over if something were to happen. I’m sure we’d eventually figure it out, but in my opinion it is better to have a contingency plan ready. Additionally, it really isn’t MaidSafe’s concern what we do at the application level. If someone comes up with a great idea today, there isn’t a community driven process in place to propagate that idea into something actionable and accepted by the larger developer community. Ideas can spread through osmosis, but having some structure in place really helps the flow of ideas in my opinion.
3 Likes
I’m for using oetyngs keystone for authentication - looks good for me =D
2 Likes
I checked who is at least mirroring at Codeberg: from 2019 to 2021 a few early org names most of us know:
2019
Doge Dogecoin
Ethereum
2021
Wikipedia
Mozilla
Ansible
OpenBSD
CodeBerg CI
to name a few… over 500+ orgs there now… big and small and growing fast
4 Likes
Good name
I think there are three things that will decide most of all what people will use:
What autonomi is designed for
What works
What people want to use
And then, some things are more or less easy to find. The die hards will find their way.
But a lot of people will be put off when information is scattered or confusing. So, that is something I always give my thumbs up to, examples and docs.
And the “keystone” app, that’s just a demo thing Was very fun to build.
3 Likes
I’m really not good at typing..
4 Likes
I’ve not looked at the thing yet but I like “keystone” 
3 Likes
Had a quick look and it looks good. I think easy to add a dweb API that does facilitates this for web apps, either by taking on the keystone, sorry KeyStore role or communicating with the daemon. Seems better to just have one process in the longer run though.
dweb already uses a similar process for deriving keys for different apps, data types and named objects - it just doesn’t store the master key yet. I was imagining this would be stored in a Vault and that apps and users would be able to manage their keys in that value using dweb REST API and CLI.
2 Likes
Autonomi_Community now exists on Codeberg as an organisation
What is an organization?
An organization is a group of users that have access to a shared account. As such, they can all access the different repositories of the organization. An organization can be composed of several teams, each having a defined role in the project’s development and also different access rights. This makes organizations an easy and powerful tool to collaborate on a project.
Everyone can create organizations on Codeberg for free. The following sections will show you how to create and manage an organization.
Let me know your Codeberg user names so I can add you and then we can appoint other admins.
Migrating existing repos looks straightforward.
2 Likes
A step in the right direction, especially that they use Forgejo and they are working on federation actively, so kinda decentralized
2 Likes
It will make a good backup until we get Gitonomi set up
3 Likes
Yep, these should be like guidelines and encourage apps to make structures that can be used by other apps to access data.
That way its not prescriptive for all Apps but guidelines that can be morphed into a useful “rules” for an app.
For instance a anttube app creator could use the guidelines to develop a set of APIs and data structures for storing the meta data required for video/media and channels and search metadata. Then define APIs for their App.
They publish that and others can access the data, create APIs into their own Apps that follow the same rules & layout.
Thus people can add in the wealth of anttube media into their App which is not a anttube alternative but a completely different sort of App. From a AMSR app to landscaping app to instructional tutorial app to what ever that wants video/media playing or searching.
1 Like