TL;DR: Even highly advanced users like Korr could benefit from more customization options within P123—without needing a formal feature request for every idea. That said, I’ve mostly resigned myself to using downloads, unless P123 sees open, customizable tools as a way to grow and market the platform.
People can now download the rank performance test, upload it into Claude and run the artifact to get a graphic of feature inversions.
This is just an example, A member could just as easily ask Claude to create an artifact that gives a t-score. Too many steps (with the downloads) I know.
But the reason I mention it here is artifacts run in the browser. P123 could off-load some of the computation. P123 could give us a place to share artifacts and maybe allow them access to some of the data without the download and upload steps.
Also, I like all of Korr's ideas but I would probably do it slightly differently. I would not mind taking his ideas as an artifact and customizing them..
I really think P123 needs to give users more flexibility that doesn’t require a formal feature request for every creative idea we have. Almost no feature requests get implemented—and understandably so. It would be impossible to fulfill them all.
Maybe not with artifacts per-se but something like it that runs in the browser, that is open source and members can contribute and could be modified by Claude (or another LLM). Members (and Claude) could do some of the heavy-lifting as far as providing feature requests in other words.
A bit of a repeat but this was a popular feature that P123 will never implement as a feature: Python program to find correlations and multicollinearity
Algoman's feature could not be done with artifacts or anything as simple. But we could start with artifacts (or something like it) and work on some open-source Python code (including Algoman's popular code) later.
Briefly we had code that was run in Colab which had direct access to P123's data. A sandboxed safe environment where code could be modified. AWS could be used too.
This feature is really just like the API however. But for mew members not yet ready for using an API there are things we could do to attract them to P123.
Imagine a beginner-friendly, low-code path to API-style workflows—and a community space to share, modify and improve them. That’s the idea.