2 improvements for developers : custom fields slugs & blogposts

I’ve been developing for several years a social website  (https://goutu.org) based on Peepso plugin (free version at the moment).  I noticed two opportunities for improvement in the direction of developers in Peepso, and I hope you’ll take them into consideration for future updates : 

1. When creating a custom profile field, we are missing the possibility to provide a “slug” to the field, as we could do for WP posts. The only “key” to the field is computed by Peepso and results in an arbitrary ID (e.g. “peepso_user_field_22598”), but this ID will be different on the remote version of my website. Therefore, I’m having a hard time accessing this field from the code. It would be much easier to address custom fields whenever we had the possibility to declare this slug in the field creation form, without being shown to the end user.
2. The blogposts class only allows “post” post type to be published and treated as an embedded object with its companion post. This forces me to completely replicate this blogpost class on my own code, since I need to have activities added to the activty stream, for other post types than “post” (e.g. “recipe”, or “menu”…). It’s a pity, just because there are 2 or 3 lines of code checking the post_type and discarding it, if different from “post”. The plugin would be much more expandable if there was a filter defined for allowed post types into the blogpost class.

Regards,

Pascal.

The page I need help with: [log in to see the link]