Mention closed-source apps in addition to open-source apps per @aklapper
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sat, Mar 29
Per @aklapper, it's best to show both closed-source and open-source TOTP apps.
In T16018#21478, @Cigaryno wrote:In T16018#21476, @aklapper wrote:I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
Some FoSS devs may not be familiar at all with open-source TOTP apps. I personally use Google Authenticator so I agree with you and also, I have my TOTP content on WinAuth too, which is unmaintained however I am not ready to switch TOTP app on my Windows PC (my revs from now on are created from an Ubuntu VM due to the arc troubles I am having on Windows).
In T16018#21476, @aklapper wrote:I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
In D25934#25089, @aklapper wrote:I'd prefer not to remove common proprietary software options but list FOSS options first.
I'd personally not remove common proprietary software options (as it makes life of users potentially harder if they already have such an app installed) but list FOSS options first.
I'd prefer not to remove common proprietary software options but list FOSS options first.
I will submit a patch shortly.
In D25926#25064, @aklapper wrote:What is there to "further review"? It's two lines...
What is there to "further review"? It's two lines...
Can this be further reviewed?
Fri, Mar 28
Thanks for the hint.
Well done \o/
Remove duplicated assignments to $stderr
Add link to T16023
Fix lint message
Update to detect stderr messages
As said in https://we.phorge.it/D25931#25023 I think this is a sub-task of T15243. And in this specific case, very probably we don't want to log anything. So your report could be considered a regression caused by T15243.
Thanks my friend. I 100% understand the problem and I'm happy you shared the stack trace in the task and I'm happy about this test plan that helped me to reproduce,
arc diff
git rebase master
It seems H29 works lol. I've improved it a bit to do not trigger if the celerity map was already touched.
No problem! I'll send you my crypto wallet address. Once the money has arrived you'll receive your clipboard content as an NFT.
Yep thanks, I need my clipboard of the 12 of August 2024 to get back the "D25772" to copy-paste it here and attract hackers asd
My keylogger thanks you! Would you like to know anything else about your online patterns?
You clearly hacked my account lol
30 seconds for a review?! I think you broke a record.
git rebase master
Thu, Mar 27
Looks like a Good Starter Task.
Wed, Mar 26
In D25926#24899, @Cigaryno wrote:robots.txt can have the solution for that (see below).
[...]
For search engines, the solution is to add this to robots.txt:
In theory yes if everyone behaved. In practice, robots.txt is ignored and LLM/AI crawlers are ruthless. (For example, GNOME GitLab admins recently installed Anubis to run background checks on your machine.)
(I cannot double-accept so only just one accept asd)
In D25926#24898, @valerio.bozzolan wrote:
- more search engine rabbit holes (but maybe not that bad)
robots.txt can have the solution for that (see below).
Uhm. Good points:
In D25926#24895, @aklapper wrote:Why would a logged-out user (who does not want to or cannot create an account) want to know about Repository management log or Repository limits? I don't see how that's their business (or interest)?
In T15999#21434, @aklapper wrote:Some items in the task description make me a bit uncomfortable in my instance.
I don't think you need to be uncomfortable on your instance (phabricator.wikimedia.org)
For Herald, it looks to be restricted to trusted contributors to restrict who can create personal rules (they actually can vandalize tasks via personal rules with the action set to claim the task), that's not something to take care of at all on your instance.
Project members, maniphest reports, user tasks and badges are actually useful for logged-out users.
But everything that's Diffusion-related sounds pointless for your instance as every repo is a read-only mirror of the repos on a Gerrit instance.
Why would a logged-out user (who does not want to or cannot create an account) want to know about Repository management log or Repository limits? I don't see how that's their business (or interest)?
Some items in the task description make me a bit uncomfortable in my instance. Why does everyone need to see Diffusion sync, pull, and push logs? Why Herald transcripts? Why repo management if you cannot manage? What are actual use cases which outweigh security implications?
In D25926#24890, @avivey wrote:There might be some security implications to this.
Why is this needed?
There might be some security implications to this.
Why is this needed?