This is an open-to-the-public meeting. Our engineering team meets and all everyone in the community is welcome — app developers, app users, and the simply curious. You can listen in, ask a question, or participate in our discussions of engineering concerns or questions.
Over the past weekend, I introduced a number of lightning developers to Blockstack. The explorer wasn’t working (as of this post, the homepage isn’t displaying any names or data). I understand that this is because of internal resource constraints. I wanted to flag this again with the hope it more resources can be dedicated to improving it and adding basic features like the ability to see possible transactions immediately when they hit the mempool.
Thanks @larry, we’re actively working on fixing the Explorer’s homepage problems at the moment, and kicking off a sprint formally to make a variety of other Explorer improvements starting next Tuesday.
Is there an issue filed for the mempool-related request in particular? If not, mind filing one so we can make sure to consider and prioritize properly?
We met last week to discuss the situation, and came out of that with a number of action items. Some of those are already in the works. We will be dedicating a lot of time to explorer stability in the near future.
In terms of new features, we meet regularly to go over tickets and prioritize. We can add this idea (I definitely like it!) to get prioritized.
To summarize the feedback from the collections design forum post, there were 2 major points brought up by community members.
1) The ability to have multiple instances of each collection type. As a user, you might want to store your sensitive data in a separate collection and be able to choose which collection to share with an app.
Meeting discussion: This may or may not be a common use case. We don’t currently have data to support this, but many participants of the meeting said that they would want this feature. So what we want to do is make sure this can be enabled later with the current design. We will not implement this with the MVP of collections.
2) The ability to only roll back changes made by 1 single app to a collection
Meeting discussion: This also might not be a common use case. The ability to roll back to a specific date should satisfy 99% of cases. However we could add the app name to the historical file naming scheme so that the feature can be implemented later in the file manager.