I have created an application, and my plan was to make it public and use this app to accompany my paper to be submitted to a journal, which requires anonymous submissions. Therefore, I need to remove the creator information from the application, so that reviewers will not recognize me as the creator. Is this possible?
To be super clear, let’s take below app as example
what I want to do is to remove the user icon at bottom-right and make the app anonymous.
That is part of the Community Cloud UI and can’t be removed. Can you create an new, anonymous GitHub account and deploy from that? You’d need to copy your files into a new repo without forking to prevent tracing it back to you through the GitHub code if it’s public, though.
Edit: Oops. @SiddhantSadangi said it first. I missed the reply.
I have the same need. i don’t understand this new decision from streamlit.
it’s kind of forces people to create several anonymous github account or migrate to an other hosting service even if it’s not free. i wonder if streamlit could offer a paid hosting service but which offers a domain name and more flexibility in the ui.
Thank you very much. This is of course one of the options. Since you are Streamlit Team Member, let me elaborate on the topic. I think that there is some group of people in the streamlit community that would appreciate such capability for applications. For example, just in my laboratory, a handful of students are using streamlit to accompany their papers, which sometimes requires to be anonymous. I guess this is some kind of recent update, because I was not seeing my account information on the application before. Anyways, I will create an anonymous github account!
That’s a great point, about double-blind peer reviews. We hadn’t considered that use case!
And now that I think of it, this issue wasn’t created by the introduction of the bottom-right avatar — because even before that launched you could just click on the Github icon in the top-right and discover the author. Or the Fork button.
And I’m not even sure where else that information appears. Perhaps it’s in the JS payload somewhere? Without a full audit, we couldn’t tell.
So the solution here would require a fair amount of research.
Either way, I’m happy you found a solution. It’s definitely a bit annoying, but it’s the most robust solution for a lot of reasons.
Yes, this is a recent change and part of the new profile pages we’re rolling out for users. We’re focusing on the “community” part of Community Cloud to make app sharing and discovery easier. However, your use case is interesting as a valid, non-commercial, educational scenario so I’ll be sure to pass it on to engineering.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.