pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2024-01-06T18:38:00Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/1No Undo Activities of Follow Activities are generated when the user is unfoll...2024-01-06T18:38:00ZlainNo Undo Activities of Follow Activities are generated when the user is unfollowedhttps://git.pleroma.social/pleroma/pleroma/-/issues/2Implement statuses/mentions endpoint2020-09-10T13:01:36ZlainImplement statuses/mentions endpointFrom TwitterAPI docs:
### statuses/mentions
Returns the 20 most recent mentions (notices containing `@username`) for the authenticating user.
This method will not include repeats in the XML and JSON responses unless the `include...From TwitterAPI docs:
### statuses/mentions
Returns the 20 most recent mentions (notices containing `@username`) for the authenticating user.
This method will not include repeats in the XML and JSON responses unless the `include_rts` parameter is set. The RSS and Atom responses will always include repeats as notices prefixed with `RT `.https://git.pleroma.social/pleroma/pleroma/-/issues/3implement hashtag parsing2018-12-10T13:59:43Zlainimplement hashtag parsinghttps://git.pleroma.social/pleroma/pleroma/-/issues/4Write XML representers for all activity types2017-09-17T15:06:36ZlainWrite XML representers for all activity typesThe ActivityRepresenter at https://gitgud.io/lambadalambda/pleroma/blob/develop/lib/pleroma/web/ostatus/activity_representer.ex only knows how to handle notes for now. It should handle all ostatus federatable messages.The ActivityRepresenter at https://gitgud.io/lambadalambda/pleroma/blob/develop/lib/pleroma/web/ostatus/activity_representer.ex only knows how to handle notes for now. It should handle all ostatus federatable messages.https://git.pleroma.social/pleroma/pleroma/-/issues/5Implement fake Twitter Lists for Public / TWKN timelines2022-02-22T01:00:34ZlainImplement fake Twitter Lists for Public / TWKN timelinesClients like Twidere support lists of users so you can get only a subset o tweets. We could use that to implement a way to view the public TL / TWKN on clients that don't explicitly support it. See https://dev.twitter.com/rest/reference/...Clients like Twidere support lists of users so you can get only a subset o tweets. We could use that to implement a way to view the public TL / TWKN on clients that don't explicitly support it. See https://dev.twitter.com/rest/reference/get/lists/list.https://git.pleroma.social/pleroma/pleroma/-/issues/6Implement character limit for posts.2017-09-17T15:06:48ZlainImplement character limit for posts.This also needs to be exposed in the config.json in the GS emulation layer.This also needs to be exposed in the config.json in the GS emulation layer.https://git.pleroma.social/pleroma/pleroma/-/issues/7Don't allow empty posts.2017-04-25T10:01:10ZlainDon't allow empty posts.https://git.pleroma.social/pleroma/pleroma/-/issues/8Don't allow self-retweets.2022-02-22T01:00:35ZlainDon't allow self-retweets.They don't make much sense.They don't make much sense.https://git.pleroma.social/pleroma/pleroma/-/issues/9Implement deletion2017-09-17T15:07:07ZlainImplement deletionI.e. this: https://www.w3.org/TR/activitypub/#delete-activity-outbox
This also needs representers for the Twitter API and OstatusI.e. this: https://www.w3.org/TR/activitypub/#delete-activity-outbox
This also needs representers for the Twitter API and Ostatushttps://git.pleroma.social/pleroma/pleroma/-/issues/10Implement user settings.2017-09-17T15:06:55ZlainImplement user settings.This will also need frontend changes.This will also need frontend changes.https://git.pleroma.social/pleroma/pleroma/-/issues/11Implement the twitter 'direct messages' endpoint2018-12-07T17:09:30ZlainImplement the twitter 'direct messages' endpointhttps://dev.twitter.com/rest/reference/get/direct_messages
This maps to a note activity that goes only to the recipients.https://dev.twitter.com/rest/reference/get/direct_messages
This maps to a note activity that goes only to the recipients.https://git.pleroma.social/pleroma/pleroma/-/issues/12Implement OAuth22020-09-11T16:52:33ZlainImplement OAuth2This is needed to make clients like Twidere not super slow (password checking is done slowly on purpose) and for compatibility with the mastodon api.This is needed to make clients like Twidere not super slow (password checking is done slowly on purpose) and for compatibility with the mastodon api.https://git.pleroma.social/pleroma/pleroma/-/issues/13Implement the Mastodon API2017-09-17T15:06:25ZlainImplement the Mastodon APIMastodon is getting some good clients and the API is very similar to the Twitter API, see https://github.com/tootsuite/documentation/blob/master/Using-the-API/API.md
This requires a working oauth2 implementation.Mastodon is getting some good clients and the API is very similar to the Twitter API, see https://github.com/tootsuite/documentation/blob/master/Using-the-API/API.md
This requires a working oauth2 implementation.https://git.pleroma.social/pleroma/pleroma/-/issues/14Implement OStatus activity parsing2018-06-13T22:29:32ZlainImplement OStatus activity parsingOStatus activties should be translated into ActivityPub activities when they come in.OStatus activties should be translated into ActivityPub activities when they come in.https://git.pleroma.social/pleroma/pleroma/-/issues/15Restrict nicknames to [a-zA-Z\d]2017-04-26T07:19:03ZlainRestrict nicknames to [a-zA-Z\d]better be safe for now.better be safe for now.https://git.pleroma.social/pleroma/pleroma/-/issues/16Make User.user_info not call the DB every time2017-05-03T11:39:09ZlainMake User.user_info not call the DB every timeThis could be done by just moving the info into the user database model and calculating them when they happen.This could be done by just moving the info into the user database model and calculating them when they happen.https://git.pleroma.social/pleroma/pleroma/-/issues/17Remove the need to persist a statusnet_conversation_id in activities2017-05-03T11:39:28ZlainRemove the need to persist a statusnet_conversation_id in activitiesFor compatibility with the TwAPI, we have an integer id that represents the conversation id in addition to the 'context' field.
This means you have to set this anywhere new activities are created. I'd rather keep it with only the contex...For compatibility with the TwAPI, we have an integer id that represents the conversation id in addition to the 'context' field.
This means you have to set this anywhere new activities are created. I'd rather keep it with only the context. Maybe we could generate new objects of type 'Context' with the id as the context and a field for the statusnet id. They'd have to be looked up from the DB, but could mostly be served from cache.https://git.pleroma.social/pleroma/pleroma/-/issues/18Implement incoming websub2017-05-03T11:38:41ZlainImplement incoming websubhttps://git.pleroma.social/pleroma/pleroma/-/issues/19Implement outgoing Salmon2017-05-03T11:38:50ZlainImplement outgoing Salmon'Hardest part' will be to find a way to create public keys. Probably call out to openssl...'Hardest part' will be to find a way to create public keys. Probably call out to openssl...https://git.pleroma.social/pleroma/pleroma/-/issues/20Implement the ability to search or filter posts by date and time2020-04-23T11:44:47ZlainImplement the ability to search or filter posts by date and timeA very useful feature that all existing OStatus servers seem to be missing is the ability for users to search for old posts made during a specific timeframe. I think Pleroma would benefit greatly from having such a feature. I envision be...A very useful feature that all existing OStatus servers seem to be missing is the ability for users to search for old posts made during a specific timeframe. I think Pleroma would benefit greatly from having such a feature. I envision being able to add date ranges to any search in order to limit results to posts made before and/or after certain dates. This would be useful for searching for historical posts and various archiving efforts.