dontconnect not honoured #1161
Labels
No Label
bug
build
dependencies
developers
documentation
duplicate
enhancement
formatting
invalid
legal
mobile
obsolete
packaging
performance
protocol
question
refactoring
regression
security
test
translation
usability
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Bitmessage/PyBitmessage-2024-12-06#1161
Loading…
Reference in New Issue
Block a user
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?
on a pristine install, if you modify PORTABLE mode and / or change NETWORK settings - say SOCKS5 settings back and forth - or such - then pyBM (run from current v0.6 py sources in Linux) will connect even though initially DONTCONNECT is set in the KEYS.DAT file. This may be surprising or not desirable behaviour.
so if you really want DONTCONNECT, you have to pull the network cable, thus air-gapping the machine.
Peter says, he "cannot reproduce" it, so make of it what you want. 👍
Ok I'll look at it, maybe it's the portable mode that is causing this.
You did not bother to explain the issue. For example:
can be tested using #1178
and 3 options
I think that people expect PyBM to remain offline after closing the settings dialog. I think that maybe after closing settings, the three-choice dialog should show up again. That appears to be more understandable for a beginner.
"let me configure..." does not imply that BM goes online after I am done configuring.
"let me configure..." option needs to be stated unambiguously, i.e.:
"let me configure and stay the heck OFFLINE"
does not look 100% OK to me either. the menu option wording ("conn./disconn netwk") is inconsistent initially.