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

I can't send to a mailing list if I'm hosting it #402

New Issue
Closed
opened 2013-08-12 22:40:39 +02:00 by grant-olson · 3 comments
grant-olson commented 2013-08-12 22:40:39 +02:00 (Migrated from github.com)
Copy Link

This is probably similar to #239 but the case is a little different.

  1. I'm hosting a mailing list.
  2. I tried to reply to someone else's post.
  3. My send hangs with the text "Waiting on their encryption key. Will request it again soon.

I don't so much care if the original message hits the peer-to-peer network, but it would be nice to be able to reply without having to use a different bitmessage instance and/or fake out the reply by sending a broadcast.

This is probably similar to #239 but the case is a little different. 1. I'm hosting a mailing list. 2. I tried to reply to someone else's post. 3. My send hangs with the text "Waiting on their encryption key. Will request it again soon. I don't so much care if the original message hits the peer-to-peer network, but it would be nice to be able to reply without having to use a different bitmessage instance and/or fake out the reply by sending a broadcast.
grant-olson commented 2013-08-12 22:50:27 +02:00 (Migrated from github.com)
Copy Link

I doubt it matters, but the reply was sent via the API.

I doubt it matters, but the reply was sent via the API.
PeterSurda commented 2015-11-27 15:04:52 +01:00 (Migrated from github.com)
Copy Link

I can't reproduce it in the UI, it was probably fixed in ceeea1da73, or slightly later, because I remember that broadcasts didn't work at the beginning of my changes.

It may still not work when using the API though, in this case, it is supposed to send a broadcast rather than a normal message. So it actually probably is a frontend issue and not an API issue. The API doesn't magically know that when you call sendMessage it is actually supposed to send a broadcast instead. What are you using as a frontend, or perhaps what were you using at a frontend when you encountered this?

I can't reproduce it in the UI, it was probably fixed in https://github.com/mailchuck/PyBitmessage/commit/ceeea1da732eb02f15bdd4287a3cfc804227693f, or slightly later, because I remember that broadcasts didn't work at the beginning of my changes. It may still not work when using the API though, in this case, it is supposed to send a broadcast rather than a normal message. So it actually probably is a frontend issue and not an API issue. The API doesn't magically know that when you call sendMessage it is actually supposed to send a broadcast instead. What are you using as a frontend, or perhaps what were you using at a frontend when you encountered this?
PeterSurda commented 2015-12-11 23:53:41 +01:00 (Migrated from github.com)
Copy Link

Sorry decided that this is a frontend issue and there's nothing for me to fix here.

Sorry decided that this is a frontend issue and there's nothing for me to fix here.
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
wontfix
Milestone
No items
No Milestone v0.6.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-02-27#402
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?