High-level datatypes library

[loziniak]

@RolandR

What about starting a companion crate instead - autonomi-util maybe?

I was thinking about autonomi-hld or autonomi-highlevel, so that we don’t end up with too much diversity there, utils can be anything… Do you think it makes sense? Are there any utilities you are thinking about, that would not be high-level datatypes?

@RolandR

I misread your second post - I thought it was also directed at me. Please disregard

No problem! This could be directed at you, perhaps this could also be somehow abstracted-out and useful for others as part of a crate, then it applies as well hahaha

@happybeing

I opened an issue about this for discussion with Autonomi and other devs, share here, but nobody has commented.

You mean this one: feat: Unify PublicArchive and PrivateArchive in a single type (for discussion) (edit: there’s also forum thread) ? Perhaps there were too few of us to have an opinion at all in the topic I still don’t, because I still haven’t used Archives.

@happybeing

That’s a different use case. It useful for each app to be in uniquely identifiable so named data created by the same user with different apps doesn’t clash.

Sure, there are data specific to a particular applications. But do you think it’s unapplicable to common formats?

@oetyng

I posted today about extracting these things out of the code I’m on.

So, we count you in, right? Then I’m setting up a repo now, and everyone, who makes a PR, will be added to the team. Or right-away if you give me your GitHub IDs, I may not have them all…