Summary

Fixed InfoQ platform user detection by switching from the deprecated /public/v1/my/menu endpoint (which returns 404) to the working /public/v1/user/get_user API endpoint.

Related Issue

N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)

Changes Made

• Created new packages/detection/src/platforms/infoq.js file with detection logic
• Added detectInfoQUser import and registration in packages/detection/src/detect.js
• Implemented POST request to /public/v1/user/get_user API endpoint

Implementation Details

Root Cause:

The original InfoQ detection used the /public/v1/my/menu endpoint, which now returns 404 and is no longer available.

Key Changes:

• Use POST request to /public/v1/user/get_user endpoint with credentials: 'include' to maintain session
• Send empty JSON body {} as required by the API
• Parse user information from response JSON data object
• Extract nickname and avatar fields for user identification
• Convert avatar URLs to base64 using convertAvatarToBase64 utility when avatar is hosted on geekbang.org to bypass CORS restrictions

Technical Notes:

• Checks response status code and JSON structure for proper error handling
• Validates login status by checking code === 0 and presence of uid
• Properly handles missing data with optional chaining and fallback values
• Avatar conversion prevents CORS issues when displaying user images from geekbang.org domain

Testing

Testing Checklist

• I have tested this code locally
• I have tested on the affected platform(s)
• I have verified the changes work in the target browser(s)

Manual Testing Steps

1. Log in to InfoQ in the browser
2. Load the extension/application
3. Verify that InfoQ user detection works correctly
4. Confirm username and avatar are properly extracted and displayed

Screenshots/Videos

N/A

Additional Notes

This fix uses the current working API endpoint and follows the same pattern as other platform detectors in the codebase.