anoMsg - Anonymous Message

[Lethos]

Just put up a quick idea out there to see if anyone in the community likes or has a use for this kind of thing.

http://anomsg.lethosdesigns.com/

It's just a bit of fun, but if you have any useful feedback I'll be glad to hear it.

Enjoy, stay anom.

Leave a "code" of your message if you really want to be cryptic, just remember only one person will see it.

[Lethos]

I guess people are using it. The next auto index increment has definitely gone up a lot.
Well I'll respect people wanting to stay anom and keep adding the features I'd planned.

[Severian]

Great service! Will use.

Spelling error in the bottom box at left: "anonmity" should be "anonymity".

[Lethos]

Great service! Will use.

Spelling error in the bottom box at left: "anonmity" should be "anonymity".

Thanks for the feedback.
I'll correct that.

[Lethos]

Submitted messages can now be received by URL as I first intended to be done.

So their is now too options;
The first implementation which was just a hashcode to submit to the site.
The second, allows you to just use a URL for ease.

[Chang Hum]

Looks good there's something similar but for relayed online chat here: https://crypto.cat/

[Lethos]

Looks good there's something similar but for relayed online chat here: https://crypto.cat/

While interesting and one could say similar, not really the place be advertising another service.

[Chang Hum]

Really sorry mate, I misunderstood what you meant by "it was an idea that was a bit of fun" and "any feedback" on an open forum. Again sorry for showing you something similar to your idea on an open forum where you are asking for feedback!!!

[gbl08ma]

Well, I tried it, it's interesting but what about an option to specify how many times the message can be viewed before it is destroyed?

http://anomsg.lethosdesigns.com/rec.php?rec=1&r=6jzjeIiqi7eusam

[Lethos]

Well, I tried it, it's interesting but what about an option to specify how many times the message can be viewed before it is destroyed?

http://anomsg.lethosdesigns.com/rec.php?rec=1&r=6jzjeIiqi7eusam

I can consider that an option. Wouldn't be too hard, to me the default would still be 1.
As it would require some work, If another agrees this is a good addition, I will go ahead with implementing it.

[Lethos]

I got some anom feedback. Not use to this.

They liked the idea, they also like your link service, so I merged the services a little.
I know the mods don't like short links, so I won't use that as an example here.

Messages can be left now with a X number of hits before they expire.
If you do bulk less than 5, it works exactly as before, if you ask it to expire after more than 5 hits, it will only provide a tny.im link.
That link has to be paid for first (the sender or receiver does not matter).

http://anomsg.lethosdesigns.com/sub-bulk.php

Pretty sure I've ironed out all the bugs, but until I do, it's run from a separate page and made the fee just 0.0001 btc (I think).

[gbl08ma]

First of all, thanks for choosing tny.im and its internet toll service. Unlike what people said in the announcement thread in this forum, it's actually proving useful for some people.

Also, looks like you learned to use the API on your own, which is great. Tell me if you need any help.

I really should automate payouts from the internet toll service, as now they're done manually. Perhaps some kind of page where people insert the Bitcoin address they used when they created the link(s), and then they're able to see how much is left to pay out and can click a button to make the transaction (w/ transaction fees deducted from their earnings, of course).

[Lethos]

First of all, thanks for choosing tny.im and its internet toll service. Unlike what people said in the announcement thread in this forum, it's actually proving useful for some people.

Also, looks like you learned to use the API on your own, which is great. Tell me if you need any help.

I really should automate payouts from the internet toll service, as now they're done manually. Perhaps some kind of page where people insert the Bitcoin address they used when they created the link(s), and then they're able to see how much is left to pay out and can click a button to make the transaction (w/ transaction fees deducted from their earnings, of course).

Yeah the API was not too hard to figure out, the api example could do with an update though.  At least my code my prove as a good example.

Automation is nice when it works, just take your time to make sure it's secure. There is a small pool that has a small auto-payout system and it has no registration like your service. How he automates it works out quiet well. http://hhtt.1209k.com/

Payouts will occur based on the following rules:
If the balance for an address is greater than 0.25 BTC and the last payout was more than 24 hours ago, a payout is done.
If the balance for an address is greater than 0.01 BTC and the last payout was more than 3 days ago, a payout is done.
Payouts are automatic and cannot be requested. These rules are run at the start of each hour.

I get paid about the same time every day, because I always fill the min payout for a 24 hour payout. Something to consider.

[gbl08ma]

I was thinking about not doing it automatically, but have the user manually request a payout only if the earnings are higher than a certain amount (because of transaction fees). I also see that blockchain.info changed the merchant API and deprecated some of the methods I used, so I'll need to completely rework the internet toll system (also, I'll need one more database on my side because now blockchain.info wants a single address for everything, and now I'm creating one address per short link per visitor).

[Lethos]

I was thinking about not doing it automatically, but have the user manually request a payout only if the earnings are higher than a certain amount (because of transaction fees). I also see that blockchain.info changed the merchant API and deprecated some of the methods I used, so I'll need to completely rework the internet toll system (also, I'll need one more database on my side because now blockchain.info wants a single address for everything, and now I'm creating one address per short link per visitor).

Probably a good choice until you reworked it to the changes already in play.

[Lethos]

Made some small adjustments on the URL used with the tny.im url service.

Instead of relying it to give me the next available url, It should be more random, but longer. Usually 4 or 5 characters.
This does not effect any previously used urls of course.