Bitmessage/PyBitmessage-2025-03-02
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 56 Actions Packages Projects Releases 5 Wiki Activity

Feature request: way to get sync progress from API #745

New Issue
Open
opened 2014-12-12 01:56:48 +01:00 by stevedekorte · 6 comments
stevedekorte commented 2014-12-12 01:56:48 +01:00 (Migrated from github.com)
Copy Link

It would be nice if there were a way to get some rough measure of sync progress via the API. Something like: 1) the number of total cached messages visible on connected nodes and 2) number of cached messages on local node. This way clients could poll it to display sync progress to the user. Otherwise, they think it's broken and see no reason to leave the app open while it syncs.

It would be nice if there were a way to get some rough measure of sync progress via the API. Something like: 1) the number of total cached messages visible on connected nodes and 2) number of cached messages on local node. This way clients could poll it to display sync progress to the user. Otherwise, they think it's broken and see no reason to leave the app open while it syncs.
PeterSurda commented 2015-11-12 00:07:02 +01:00 (Migrated from github.com)
Copy Link

This sounds interesting.

This sounds interesting.
stevedekorte commented 2015-11-12 00:09:55 +01:00 (Migrated from github.com)
Copy Link

Right now I just show # of messages processed, which at least let's users see that it's doing something. What I'd really like to show is: "number of messages other nodes have told me about but I don't have yet".

Right now I just show # of messages processed, which at least let's users see that it's doing something. What I'd really like to show is: "number of messages other nodes have told me about but I don't have yet".
PeterSurda commented 2015-11-12 00:11:21 +01:00 (Migrated from github.com)
Copy Link

Yes that's how I understood it too. I think it would be helpful to see the progress status and I also think it is doable.

Yes that's how I understood it too. I think it would be helpful to see the progress status and I also think it is doable.
PeterSurda commented 2015-11-12 00:11:44 +01:00 (Migrated from github.com)
Copy Link

Do you want this shown in the UI, exposed to the API calls or both?

Do you want this shown in the UI, exposed to the API calls or both?
stevedekorte commented 2015-11-12 00:13:23 +01:00 (Migrated from github.com)
Copy Link

In the API. We've written our own Bitmessage UI app called Bitpost: https://voluntary.net/bitpost/

We may be doing a JS port next year and moving to the JS implementation of Bitmessage.

In the API. We've written our own Bitmessage UI app called Bitpost: https://voluntary.net/bitpost/ We may be doing a JS port next year and moving to the JS implementation of Bitmessage.
PeterSurda commented 2015-11-12 01:03:33 +01:00 (Migrated from github.com)
Copy Link

Look at the latest two commits in my fork (53062f61b9 and f933cea697) for guidelines how to write the API change yourself. The commits expose the number of unsynced objects to the GUI in the network tab. I don't plan on making the API change myself before 0.6, but I can merge a commit if you want to do it.

Look at the latest two commits in my fork (https://github.com/mailchuck/PyBitmessage/commit/53062f61b9eff29059bad81237161c8d4ee81ca1 and https://github.com/mailchuck/PyBitmessage/commit/f933cea697d47f700ab36c566fc6a6e31f36cfb3) for guidelines how to write the API change yourself. The commits expose the number of unsynced objects to the GUI in the network tab. I don't plan on making the API change myself before 0.6, but I can merge a commit if you want to do it.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
enhancement
Milestone
No items
No Milestone v0.8.0
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-03-02#745
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?