New API calls #848

New Issue

2016-03-15T13:03:20+01:00

PeterSurda commented

2016-03-15 13:03:20 +01:00

(Migrated from github.com)

Came over BM:

No, the API's clientStatus doesn't give that info. But it gives some other useful info so I can implement at least that, thanks for the suggestion (wait for apiclient.py v1.25).

What angers me more about the API is that it doesn't allow to list only the headers of messages, i.e. everything except the message body, like what you get with apiclient.py -l or --ls. Each time I have to grab the whole inbox or the whole sentbox and then show you just headers. If you had hundreds of messages, let alone with the binary files, that would mean MBs if not GBs of useless data transfers :-(

I can easily add the knownnodes info into the clientStatus, add getAllInboxMessagesHeaders and getAllSentMessagesHeaders and fix the broken listAddresses2, but then it will only be in my API and not yours. I can't make a pull request on github because I communicate only via BM. I wish there was a chan where developers could just post their patches and if they were simple and straightforward they would get prompty merged into the github tree..

Came over BM: No, the API's clientStatus doesn't give that info. But it gives some other useful info so I can implement at least that, thanks for the suggestion (wait for apiclient.py v1.25). What angers me more about the API is that it doesn't allow to list only the headers of messages, i.e. everything except the message body, like what you get with apiclient.py -l or --ls. Each time I have to grab the whole inbox or the whole sentbox and then show you just headers. If you had hundreds of messages, let alone with the binary files, that would mean MBs if not GBs of useless data transfers :-( I can easily add the knownnodes info into the clientStatus, add getAllInboxMessagesHeaders and getAllSentMessagesHeaders and fix the broken listAddresses2, but then it will only be in my API and not yours. I can't make a pull request on github because I communicate only via BM. I wish there was a chan where developers could just post their patches and if they were simple and straightforward they would get prompty merged into the github tree..

PeterSurda commented

2016-03-15 15:26:09 +01:00

(Migrated from github.com)

apipatch.txt

[apipatch.txt](https://github.com/Bitmessage/PyBitmessage/files/174079/apipatch.txt)

Maffelz commented

2016-03-24 19:23:25 +01:00

(Migrated from github.com)

Afaik this repository is considered as abandoned and people are working on a fork (initiated by mailchuck iirc).
You probably want to push enhancements over there.

Edit: just checked the repo out, seems like you already found it ;)

Afaik this repository is considered as abandoned and people are working on a fork (initiated by mailchuck iirc). You probably want to push enhancements over there. Edit: just checked the repo out, seems like you already found it ;)

PeterSurda commented

2016-03-24 19:25:53 +01:00

(Migrated from github.com)

The mailchuck fork will be merged here. This is why I opened a ticket here, because I plan to do it after it's merged.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-23#848