New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitmessage support #65

Open
HelloZeroNet opened this Issue Mar 17, 2015 · 17 comments

Comments

Projects
None yet
5 participants
@HelloZeroNet
Owner

HelloZeroNet commented Mar 17, 2015

Send / Receive messages using local client XMLRPC

@PeterSurda

This comment has been minimized.

PeterSurda commented Mar 7, 2017

I have a prototype ready. It's a plugin that adds a new websocket call to send a message. However I'm not familiar with ZeroNet so I have some questions.

  • Where should ZeroNet store the configuration for the Bitmessage API (like the username/password)?

  • Where should users and/or sites publish their Bitmessage addresses? You can't construct them from the existing ZeroNet identifiers, because each Bitmessage address contains two keypairs rather than one. I tried using site_data, but I don't think that I'm doing it correctly.

Let me know.

@kamikazi3728

This comment has been minimized.

kamikazi3728 commented Mar 7, 2017

@PeterSurda

I also have a partial prototype, and may be able to help with some of your questions.

As for the API configuration, I think could be as simple as including the settings in users.json

For the publishing of addresses, my method just added a zeronet identifier or two. That way it would be much more accessible to those publishing sites.

I do believe I found a way to construct both keypairs from the existing identifiers, but I'm trying to work out a few kinks with that.

If you would be open to collaborating on this with me then feel free to contact me/reply to this thread and we'll work something out.

@PeterSurda

This comment has been minimized.

PeterSurda commented Mar 7, 2017

@kamikazi3728 Sure, a collaboration may produce a better result.

As for the API configuration, I think could be as simple as including the settings in users.json

I'm not sure how to do that but will try.

For the publishing of addresses, my method just added a zeronet identifier or two. That way it would be much more accessible to those publishing sites.

Hmm then I will have to add the functionality to add an address from a private key to the Bitmessage API. Also, it will stop working when forward secrecy is implemented.

@PeterSurda

This comment has been minimized.

PeterSurda commented Mar 7, 2017

As for the API configuration, I think could be as simple as including the settings in users.json

I don't see a method for adding a custom variable into users.json. What I ended up doing instead was adding new parameters using the ConfigParser interface, so you can specify them both in the zeronet.conf as well as in the command line. That seems to make more sense and it works too.

Still figuring out how to allow users/sites to specify their bitmessage addresses.

@kamikazi3728

This comment has been minimized.

kamikazi3728 commented Mar 8, 2017

Just so we don't clutter up this thread, we could move the conversation into one of our branches, it might be better to get a working model going and just use this thread to get any extra input we might need.
I think working in your branch rather than mine might be best, I haven't committed any of my changes yet, so they would be easy to port over to yours if needed.

@PeterSurda

This comment has been minimized.

PeterSurda commented Mar 8, 2017

Ok I gave you access to my repo.

@DaniellMesquita

This comment has been minimized.

Contributor

DaniellMesquita commented Aug 8, 2017

@HelloZeroNet, it wasn't already implemented?

@PeterSurda

This comment has been minimized.

PeterSurda commented Aug 8, 2017

I made a pull request, #852 , after commenting here, and got no feedback whatsoever.

@HelloZeroNet

This comment has been minimized.

Owner

HelloZeroNet commented Aug 8, 2017

Yes, sorry, I forgot about it. I will check it soon

@PeterSurda

This comment has been minimized.

PeterSurda commented Aug 8, 2017

no prob

@Thunder33345

This comment has been minimized.

Contributor

Thunder33345 commented Nov 10, 2018

sorry for bumping but:
https://zeronet.io/docs/help_zeronet/donate/#bitmessage-support
the funding is done so what's the status on this?
especially now there's also peermsg(not saying peermsg can interact with bitmsg network)

@PeterSurda

This comment has been minimized.

PeterSurda commented Nov 10, 2018

I got no feedback on my PR. I don't know the scope of task. If I at least had that, I could get one of the developers to finish it.

@DaniellMesquita

This comment has been minimized.

Contributor

DaniellMesquita commented Nov 10, 2018

@PeterSurda

I got no feedback on my PR. I don't know the scope of task. If I at least had that, I could get one of the developers to finish it.

Do you know that @shortcutme likes too much to left pull requests open?
Anything big that is implemented on ZeroNet, he doesn't review/finish implementation, but he want credit for everything big on ZeroNet (not good behavior for open-source)

@DaniellMesquita

This comment has been minimized.

Contributor

DaniellMesquita commented Nov 10, 2018

If a thing that he tags as "easy" is not implemented, so think about what he says is near "impossible", like i2p (that ironically means impossible2possible).

Also, @shortcutme said on ZeroMe that will make donations more clear and with bounties, but nothing done about it

@PeterSurda

This comment has been minimized.

PeterSurda commented Nov 10, 2018

It's not easy to manage an open source project. Maybe they should hire someone to assist.

@DaniellMesquita

This comment has been minimized.

Contributor

DaniellMesquita commented Nov 10, 2018

It's not easy to manage an open source project. Maybe they should hire someone to assist.

Suggested here: #1652

@Thunder33345

This comment has been minimized.

Contributor

Thunder33345 commented Nov 10, 2018

seriously quit the flaming nofish part and bring that somewhere else...
some of your points may be valid, but this is not the place for gossip and slander

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment