My phone dies in 3 hours torrenting
Lol...In any case, you only need to pop in for 15 minutes or so every 2.5 days.
Even better - just have it connect periodically, like every 10 to 30 minutes, automatically
Exactly! "Killer app."
Topic: [ANNOUNCE] Bitmessage - P2P Messaging system based partially on Bitcoin - page 15. (Read 89873 times)
June 16, 2013, 11:46:01 AM
In any case, you only need to pop in for 15 minutes or so every 2.5 days.
Even better - just have it connect periodically, like every 10 to 30 minutes, automatically
Exactly! "Killer app."
June 14, 2013, 10:00:33 PM
My phone dies in 3 hours torrenting
Lol...In any case, you only need to pop in for 15 minutes or so every 2.5 days.
Even better - just have it connect periodically, like every 10 to 30 minutes, automatically
June 14, 2013, 07:46:24 PM
My phone dies in 3 hours torrenting
Lol...In any case, you only need to pop in for 15 minutes or so every 2.5 days.
Yeah, for this reason, having a mobile implementation might be nice. For those who want to be able to send "text messages" prism-break style
Sure, you wouldn't be able to have it running constantly.
June 13, 2013, 09:01:32 AM
My phone dies in 3 hours torrenting
Lol...In any case, you only need to pop in for 15 minutes or so every 2.5 days.
June 13, 2013, 08:52:12 AM
My phone dies in 3 hours torrenting
June 13, 2013, 08:47:59 AM
True but 10 constant connections on a phone would kill the battery in a couple hours. You need 1 push or at least pull, not 10+ pulls
I seed torrents on my phone just fine. Your GPS will drain it far faster than some connections. June 13, 2013, 08:25:26 AM
True but 10 constant connections on a phone would kill the battery in a couple hours. You need 1 push or at least pull, not 10+ pulls
June 13, 2013, 08:16:31 AM
Mobile isn't feasible at this time until a solution like electrum exists
Why's that? June 13, 2013, 04:17:00 AM
Mobile isn't feasible at this time until a solution like electrum exists
June 13, 2013, 03:50:14 AM
Sorry if this was discussed before, but does anyone work on mobile bitmessage client?
June 12, 2013, 09:57:54 PM
I tried that and it worked perfectly. I didn't realize that opening the .py file ran python automatically... what am I typing "python [path]" for lol... it appears that the launcher file only properly launches bitmessage when linked directly to the bitmessagemain.py file rather than python [path].
Well, glad we sorted this out, lol. Kind of a strange issue, and not really that important, but hey now it takes me 2 fewer seconds to start the program.
Well, glad we sorted this out, lol. Kind of a strange issue, and not really that important, but hey now it takes me 2 fewer seconds to start the program
. That's interesting. I'm running Debian and it needs the python command. I guess Mint just didn't like it. IT KNOWS what you mean.
June 12, 2013, 09:55:19 PM
I tried that and it worked perfectly. I didn't realize that opening the .py file ran python automatically... what am I typing "python [path]" for lol... it appears that the launcher file only properly launches bitmessage when linked directly to the bitmessagemain.py file rather than python [path].
Well, glad we sorted this out, lol. Kind of a strange issue, and not really that important, but hey now it takes me 2 fewer seconds to start the program.
Well, glad we sorted this out, lol. Kind of a strange issue, and not really that important, but hey now it takes me 2 fewer seconds to start the program
. June 12, 2013, 03:50:25 PM
Yeah, still doing the same thing; not really sure what the issue is. Main Menu is just a GUI for what I was doing manually. I used Main Menu to create the link - still nothing happens when I click it. If I change selection in properties to "Application in Terminal" then the terminal opens for a split second, displays no text, and disappears. (Just like when I set "terminal=true" in the .desktop file)
On the other hand, if I type "python $HOME/PyBitmessage/src/bitmessagemain.py" right into the terminal, it opens no problem.
Really strange. I'm using Linux Mint (14 Mate). I doubt this has anything to do with bitmessage, though. Anyone else having this issue?
Interestingly, (and probably irrelevant) the desktop launcher file I created opens xterm but the "Main Menu" launcher opens mate-terminal.
On the other hand, if I type "python $HOME/PyBitmessage/src/bitmessagemain.py" right into the terminal, it opens no problem.
Really strange. I'm using Linux Mint (14 Mate). I doubt this has anything to do with bitmessage, though. Anyone else having this issue?
Interestingly, (and probably irrelevant) the desktop launcher file I created opens xterm but the "Main Menu" launcher opens mate-terminal.
I installed Bitmessage on a Mint machine the other day and had that same problem. When you try to open the program from the launcher it wouldn't work, but if you right click on Bitmessage and then create a desktop icon it will work when you double click from the desktop icon.
June 12, 2013, 02:40:57 PM
Yeah, still doing the same thing; not really sure what the issue is. Main Menu is just a GUI for what I was doing manually. I used Main Menu to create the link - still nothing happens when I click it. If I change selection in properties to "Application in Terminal" then the terminal opens for a split second, displays no text, and disappears. (Just like when I set "terminal=true" in the .desktop file)
On the other hand, if I type "python $HOME/PyBitmessage/src/bitmessagemain.py" right into the terminal, it opens no problem.
Really strange. I'm using Linux Mint (14 Mate). I doubt this has anything to do with bitmessage, though. Anyone else having this issue?
Interestingly, (and probably irrelevant) the desktop launcher file I created opens xterm but the "Main Menu" launcher opens mate-terminal.
On the other hand, if I type "python $HOME/PyBitmessage/src/bitmessagemain.py" right into the terminal, it opens no problem.
Really strange. I'm using Linux Mint (14 Mate). I doubt this has anything to do with bitmessage, though. Anyone else having this issue?
Interestingly, (and probably irrelevant) the desktop launcher file I created opens xterm but the "Main Menu" launcher opens mate-terminal.
June 11, 2013, 09:21:52 PM
I've sub'd to the addresses in this thread and have not received anything yet. But I did get a friend to install it and successfully received a message from that friend.
My connection light is consistently yellow. I did enable port forwarding on the router, and configured my firewall (UFW) properly. The first time I launched it it was green. I think my ISP does something sketchy with the modem firmware's DHCP settings to limit connections on P2P software, so maybe that's what's preventing the green. Who knows.
For some reason I can't get it to launch via a desktop shortcut; have to use the terminal every time. I tried different formats for the command, still nothing - the term opens for a sec and closes. Any suggestions? I'm a linux n00b so maybe I missed something. I checked "Start in terminal" and command is python $HOME/PyBitmessage/src/bitmessagemain.py (same command I use directly in terminal.) xterm starts for a second then quits, with no visible text.
I was skimming and read part of this as "because some Windows 3.1 users have reported...."
And I was like
My connection light is consistently yellow. I did enable port forwarding on the router, and configured my firewall (UFW) properly. The first time I launched it it was green. I think my ISP does something sketchy with the modem firmware's DHCP settings to limit connections on P2P software, so maybe that's what's preventing the green. Who knows.
For some reason I can't get it to launch via a desktop shortcut; have to use the terminal every time. I tried different formats for the command, still nothing - the term opens for a sec and closes. Any suggestions? I'm a linux n00b so maybe I missed something. I checked "Start in terminal" and command is python $HOME/PyBitmessage/src/bitmessagemain.py (same command I use directly in terminal.) xterm starts for a second then quits, with no visible text.
I have reverted the EXE on the website back to the prior version (0.3.1) because some Windows 7 (and Windows server) users have reported having an issue sending messages with the current version.
I was skimming and read part of this as "because some Windows 3.1 users have reported...."
And I was like
You want to get Bitmessage to open up from a launcher icon?
If so, you should have a program called Main Menu. Open that. Then click on the category you want Bitmessage under. For me, I put it under Internet. Then create new. Then type in for the command "python /home/user/PyBitmessage/src/bitmessagemain.py" and click on the little icon, then navigate to the little can. If you have any further questions, let me know. We'll get 'er done.
June 11, 2013, 09:18:46 PM
Yeah man I'm on Windows 3.1...
June 11, 2013, 09:09:57 PM
I've sub'd to the addresses in this thread and have not received anything yet. But I did get a friend to install it and successfully received a message from that friend.
My connection light is consistently yellow. I did enable port forwarding on the router, and configured my firewall (UFW) properly. The first time I launched it it was green. I think my ISP does something sketchy with the modem firmware's DHCP settings to limit connections on P2P software, so maybe that's what's preventing the green. Who knows.
For some reason I can't get it to launch via a desktop shortcut; have to use the terminal every time. I tried different formats for the command, still nothing - the term opens for a sec and closes. Any suggestions? I'm a linux n00b (still, after using it 7 years) so maybe I missed something. I checked "Start in terminal" and command is python $HOME/PyBitmessage/src/bitmessagemain.py (same command I use directly in terminal.) xterm starts for a second then quits, with no visible text.
I was skimming and read part of this as "because some Windows 3.1 users have reported...."
And I was like
My connection light is consistently yellow. I did enable port forwarding on the router, and configured my firewall (UFW) properly. The first time I launched it it was green. I think my ISP does something sketchy with the modem firmware's DHCP settings to limit connections on P2P software, so maybe that's what's preventing the green. Who knows.
For some reason I can't get it to launch via a desktop shortcut; have to use the terminal every time. I tried different formats for the command, still nothing - the term opens for a sec and closes. Any suggestions? I'm a linux n00b (still, after using it 7 years) so maybe I missed something. I checked "Start in terminal" and command is python $HOME/PyBitmessage/src/bitmessagemain.py (same command I use directly in terminal.) xterm starts for a second then quits, with no visible text.
I have reverted the EXE on the website back to the prior version (0.3.1) because some Windows 7 (and Windows server) users have reported having an issue sending messages with the current version.
I was skimming and read part of this as "because some Windows 3.1 users have reported...."
And I was like
June 11, 2013, 08:14:25 PM
Bitmessage is now available for Gentoo users via the Bitcoin overlay:
https://gitorious.org/bitcoin/gentoo/commit/783046a4bf84b908ce0b30e2f8f0ed845ba89e09
https://gitorious.org/bitcoin/gentoo/commit/783046a4bf84b908ce0b30e2f8f0ed845ba89e09
June 09, 2013, 04:52:01 AM
v0.3.3
For the lazy people, latest version at
https://bitmessage.org/download/windows/Bitmessage.exe
:bow: And thanks again, this version seems really fine - started up just nicely and runs so smooth that I will let it run 24/7
June 07, 2013, 07:30:30 PM
v0.3.3
Remove inbox item from GUI when using API command trashMessage
Add missing trailing semicolons to pybitmessage.desktop
Ensure $(DESTDIR)/usr/bin exists
Update Makefile to correct sandbox violations when built via Portage (Gentoo)
Fix message authentication bug
Remove inbox item from GUI when using API command trashMessage
Add missing trailing semicolons to pybitmessage.desktop
Ensure $(DESTDIR)/usr/bin exists
Update Makefile to correct sandbox violations when built via Portage (Gentoo)
Fix message authentication bug
Jump to: