Welcome, Guest. Please login or register.

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dokument

Pages: [1] 2 3 ... 33
1
General Discussion / Indefinite break.
« on: August 07, 2014, 02:54:03 PM »
I've been taking a break from bitmessage a bit recently and am not sure if I will be able to jump back in. All of my hosted echo servers and mailing lists will be down due to this. I'm not sure yet but I might take down the statistics page as well. You can find all my projects on github.

Good luck to Bitmessage and everyone involved.

2
General Discussion / Re: Having trouble connecting
« on: March 13, 2014, 05:42:37 PM »
If anyone runs Bitmessage regularly and has a static IP, I could add it to the list of bootstrap nodes. This doesn't tax the node too heavily; mine tends to have ~80 connections and it would help mitigate these kind of bootstrapping problems.

I am currently gathering node information. The longer it runs, the more data it will gather. Currently I have a list of about 100 ip's that are always on bitmessage (at least once a day).  Still working on making the data public but you can see some older data here http://bitmessage.adammelton.com/api/ip/ which will be updated automatically in the near future.

Thanks,
.dok

3
It's not just you. No, it isn't normal. Hard to tell if it is spam or just someone (individual or group) messing around.

http://bitmessage.adammelton.com/

4
General Discussion / Re: Proposing some API changes
« on: February 28, 2014, 11:49:37 AM »
I second these suggestions.

.dok

5
But couldn't the identification be used to identify you?

Why not just be able to have someone else do the PoW for you? Then you are only spending processing power on encrypting the message.

.dok

6
General Discussion / General Mailing List Update
« on: February 18, 2014, 12:51:25 PM »
Just letting everyone know that I am upgrading the General mailing list to the newer address scheme. The old address will continue to work but I will eventually phase it out.

I updated the Address Directory to show the new General Mailing list address.

The new address is: BM-oowmchsQvK7FBkTxwXErcF3acitN4tWGQ




FYI I am also upgrading [Bitmessage] to a new address and renaming it [Whitelisted] since that makes more sense.
The new address for it is: BM-2cU2PyNbSqQS64MXyYqmiTjSSQ8wohJxyZ but you have to be whitelisted to use it. For an invitation, message me asking for an invitation with the address that you want to be whitelisted.

Thanks,
.dok

7
So I have bitmessage.adammelton.com up and running now. It is the replacement for vps1.adammelton.com with updated graphs, heatmaps and country rankings, and an API for you all to use :)

It is pretty basic and lightweight, but it is supposed to be. Let me know if you see anything that is wrong or if anything breaks. Feedback is welcome.

There are some instructions on the API page, if you plan on using that. It also has a few code examples. In the near future I plan on include the country information/inventory size/etc.

Thanks,
.dok

8
Sorry for my absence over the last 6 months or so. I was down to checking in only periodically due the involvement at a new job (yay employment). I'll try to catch up as quickly as possible with the new features/etc.

I am almost ready to launch my replacement for my current stats page vps1.adammelton.com and hopefully some of you will find it useful. The update includes an api for retrieving stats, feel free to use it however you wish.

One part will be daily heatmaps of Bitmessage user IP addresses. Here is a current heatmap of about 8k IP addresses.

Thanks,
.dok


9
General Discussion / Re: [PHP] Bitmessage PHP class
« on: January 20, 2014, 10:33:45 PM »
Awesome!

Thanks

10
General Discussion / bitmessage.adammelton.com now points to stats as well.
« on: December 12, 2013, 10:05:16 AM »
bitmessage.adammelton.com now points to the same host as vps1.adammelton.com which shows some statistics.

Thanks,
.dok

11
General Discussion / Re: Website back online
« on: November 21, 2013, 06:42:27 PM »
No worries. Glad it was resolved.

.dok

12
Sorry for being out of the loop lately guys. I have had a lot going on. I just got the echo servers back online as well as the mailing lists.

Primary Echo: BM-orkCbppXWSqPpAxnz6jnfTZ2djb5pJKDb
Developer Echo: BM-omXeTjutKWmYgQJjmoZjAG3u3NmaLEdZK

General Mailing List: BM-oowmchsQvK7FBkTxwXErcF3acitN4tWGQ
Bitmessage (Whitelisted) Mailing List: BM-2D7c8rKoDFDMcGgRNs2B7GXejHEnjWgL6A

Sincerely,
.dok

13
General Discussion / Re: Headless/Daemon Client
« on: August 29, 2013, 01:01:13 PM »
Quote
Thanks for taking the time to make this daemon.
I tried to get it running today but unfortunately I am getting API connection test has: FAILED

Here is my keys.date file .. 
Worth mentioning is when I installed the daemon, during the config file setup, it left my 'apiport' blank, which resulted in an error, so I added in a port but still no good.
What OS? Did you restart bitmessage after doing the configuration?


Quote
I tried running the daemon with a simple; ' ./PyBitmessage/src/daemon.py ',  'apiTest' results in the error..
daemon does not support command line arguments. Instead, run daemon and enter your commands there.

Let me know if that works.

Thanks,
.dok

14
General Discussion / Re: Preventing everyone from receiving everything
« on: August 29, 2013, 12:55:43 PM »
Bitmessage is only able to accomplish what it does by using the everyone gets everything system. If you are in need of a different system, go make/find it because without EGE, Bitmessage is just another encrypted messenger.

Identities are easy to make, it is encouraged to change your identity(ies) often. If there is a flaw with the current methods, then yes, all past messages are at risk. However, this is beneficial in the fact that it points out our reliance on the encryption standards being used. Bitmessage does not rely on obfuscation. It might be nice to say that the attacker would have to get our data, then decrypt it, in order to access our information, but if your encryption methods have no flaws, there is no need to try to hide your data. I guess what I am trying to say is that Bitmessage encourages good practices and good encryption standards.

In order to make messages "targeted at the intended recipient" you would have to lose a lot of the built-in anonymity.

Also, Using Bitmessage through Tor is great, but it will be even better when you can use Bitmessage on Tor.

.dok

15
General Discussion / Re: Proposal: Message rate limitation
« on: August 25, 2013, 02:00:34 PM »
Quote
So .dok, what do we need to get this implemented and merged into the master branch?

:P well we haven't even decided what we want to do yet.

Pages: [1] 2 3 ... 33