Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename Fbits to Wake #15

Open
Angeesantos opened this issue Feb 21, 2024 · 13 comments
Open

Rename Fbits to Wake #15

Angeesantos opened this issue Feb 21, 2024 · 13 comments

Comments

@Angeesantos
Copy link

Hi, Good Afternoon!

I'm Angela and I want to know how you guys can change the name of our technology platform. We've recently undergone a name change, and we would appreciate it if you could kindly update the information to reflect our current name.

Today, at Core Web Vitals Technology Report, we appear as Fbits, being necessary to change for Wake.

image

We understand the importance of maintaining accurate and up-to-date information on your service and believe that this change will help ensure the accuracy of our representation. We kindly request your assistance in making this update.

Furthermore, all websites listed under the FBITS technology are owned by us.

Please inform us about the necessary steps and the information you require from us to facilitate the update of our platform's name. We are committed to providing any documentation or details that may be needed promptly.

We appreciate your attention to this matter and look forward to your response. Thank you for your ongoing support.

@rviscomi
Copy link
Member

The Fbits detection is in this file:

https://github.com/HTTPArchive/wappalyzer/blob/main/src/technologies/f.json#L449-L458

Is the fbits JavaScript variable still the best way to detect Wake?

@Angeesantos
Copy link
Author

Angeesantos commented Feb 21, 2024 via email

@Angeesantos
Copy link
Author

Angeesantos commented Feb 21, 2024 via email

@rviscomi
Copy link
Member

Sorry for my unknowledge, but what the "cats:6" means?

Category 6 is Ecommerce, so given that this is a rename I assume that doesn't change.

Rick, can we insert more information like description?

Yes, all of the supported properties are documented in the README. Most things have no effect anywhere on the HTTP Archive side (including the Tech Report dashboard) but we do plan to start incorporating the description field, so I'd encourage you to suggest one.

@Angeesantos
Copy link
Author

Hi Rick!

I received an e-mail from Barry who told that, for a quicker action, I should move infos from f.json to w.json file and I just did it.

"Wake": {
   "cats": [
     6
   ],
   "description": "Wake is an ecommerce software with integrated digital solutions to manage online stores.",
   "headers": {
     "X-Powered-By": "Wake"
   },
   "icon": "Wake.png",
   "js": {
     "wake": ""
   },
   "saas": true,
   "website": "https://wake.tech/"

Can you check it please?
https://github.dev/HTTPArchive/wappalyzer/blob/5e8d4898f4c0260343a19db532f5a467fcb39dfc/src/technologies/w.json

@Angeesantos
Copy link
Author

Actually, I can't.

image

Angeesantos added a commit to Angeesantos/wappalyzer that referenced this issue Feb 22, 2024
@rviscomi
Copy link
Member

Yeah you'll need to fork the repository and submit a pull request to make any direct changes.

I do have some reservations about the wake JS variable detection. That might be so generic that it leads to false positives. Probably not a big deal, but if the X-Powered-By header is reliable enough, maybe we use that alone?

For testing, do you also have a few example URLs of pages that use Wake?

@rviscomi
Copy link
Member

From a quick test of loading the sample pages, it looks like the X-Powered-By header is only present 9/14 times and the wake JavaScript variable is never set. Does that sound right?

Site X-Powered-By: Wake wake
https://www.stanley1913.com.br/  
https://www.puravida.com.br/    
https://www.b2cstore.com.br/  
https://www.dlkmodas.com.br/  
https://www.newlentes.com.br/  
https://www.abcdaconstrucao.com.br/  
https://www.esportelegal.com.br/  
https://www.suggar.com.br/  
https://www.camys.com.br/  
https://www.justapprove.com.br/  
https://www.mundotupperware.com.br/    
https://www.forlabexpress.com.br/    
https://www.marisa.com.br/    
https://www.yeesco.com.br/    

@Angeesantos
Copy link
Author

Rick, following your review, can you check if the Fbits JavaScript variable is set in these URLs please?

@rviscomi
Copy link
Member

It's not consistently used, and it doesn't add any coverage missed by the X-Powered-By header

Site X-Powered-By: Wake wake Fbits
https://www.stanley1913.com.br/    
https://www.puravida.com.br/      
https://www.b2cstore.com.br/    
https://www.dlkmodas.com.br/    
https://www.newlentes.com.br/  
https://www.abcdaconstrucao.com.br/    
https://www.esportelegal.com.br/  
https://www.suggar.com.br/  
https://www.camys.com.br/    
https://www.justapprove.com.br/  
https://www.mundotupperware.com.br/      
https://www.forlabexpress.com.br/      
https://www.marisa.com.br/      
https://www.yeesco.com.br/      

Angeesantos added a commit to Angeesantos/wappalyzer that referenced this issue Feb 23, 2024
@Angeesantos
Copy link
Author

Ok Rick! I forked the repository again and submited a pull request to make changes by including Wake infos and deleting Fbits from the file.

"Wake": {
   "cats": [
     6
   ],
   "description": "Wake is an ecommerce software with integrated digital solutions to manage online stores.",
   "headers": {
     "X-Powered-By": "Wake"
   },
   "icon": "Wake.png"
   },
   "saas": true,
   "website": "https://wake.tech/"

@Angeesantos
Copy link
Author

Hi Rick, how are you?

Can you please check the request I did? So we can start visualizing Wake infos instead of Fbits, reinforcing our position in the e-commerce ranking.

@rviscomi rviscomi changed the title Core Web Vitals - Change technology's name Rename Fbits to Wake Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants