Log in to your Recall account to give feedback

Feature Requests

Better LinkedIn post parsing
When I save a LinkedIn post, there is a lot of metadata (from JSON config I believe) that should not be saved as part of my recap. See for exemple https://app.getrecall.ai/item/c0ac765e-c4a9-4134-936b-c3850d20a583 . There is three sections in the recap and the first two are irrelevant for a human. Cut and pasting below: LinkedIn Configuration Data The provided text appears to be a collection of JSON data from LinkedIn, containing various configuration items and tracking information for different features and experiments. The data includes information about job posting, premium features, and user interface components, such as buttons and game entry points. The text mentions specific experiment IDs, treatment indices, and tracking keys, indicating that it is related to A/B testing and user experience optimization on the LinkedIn platform. The provided text appears to be a collection of configuration items for LinkedIn's Chameleon system, which is used for A/B testing and experimentation. The text includes various experiment IDs, treatment indices, and tracking information for different LinkedIn features, such as job posting, organization administration, and profile creation. The text does not provide a clear narrative or main topic, but rather seems to be a technical configuration file or data dump for LinkedIn's internal systems. LinkedIn User Profile Data The provided text is a section from a larger document titled 'Post | Feed | LinkedIn'. The text includes various API requests and responses, as well as JSON data containing information about a user's LinkedIn profile, including their name, headline, and profile picture. The user, Sylvain Carle, is the Co-Founder and Executive Director at CIVIC. Another user, Kelly Gauthier, is mentioned as the President at Rally Assets. The text also includes information about the users' connections, privacy settings, and profile pictures.
0
Load More