Steemer app update RC 3

hispeedimagins(62)

Published in

#utopian-io

Words

699

Reading

4 min

Listen

Play

Banner by @ggcarlosr :)

Repository

https://github.com/hispeedimagins/steem

New Features

Add/Edit/Remove beneficiaries?

Now you can add new beneficiaries to your post or remove all. What's more set them up for custom behavior. Like add tags to them so they will automatically enable itself without you moving your finger. Or just simple make them default for all posts. Even change it for one time behaviour. This is the first in any app for steemit.

Why?

Because after much thought on the suggestion of @codingdefined it became apparent that steem needed an app where there is not such thing as a beneficiary. So more users will use it without it eating into their precious rewards.

How did you implement it/them?
https://github.com/hispeedimagins/steem/commit/5eba9696fd9c304498aac010c4d4c6b4eb7fb5e1

First off, I created a db to save all the new beneficiaries added.
Created a page to add them easily. It can be instantiated from anywhere.
Created the view from a bottomsheet layout so the user does not have to navigate to another page and yet has minimal impact memory.
Created the functions for easily activating all the beneficiaries based on tag.
Created the logic for one off stop if you wish and also to easily disable developers as beneficiaries.
Created the logic to edit them without the need for a different page.
Added 3 beneficiaries as default. @steemj, @hispeedimagins and @utopian-io if the tag is applicable.
Created a handy button to disable developers as beneficiaries for comments as well.
Made all the ui compatible with dark and light themes.

by default they remain active.

Notifications enabled/disabled

Added the setting to enable or disable notifications. Requested by @holger80. Sorry for the tag hehe.
How did you implement it/them?

Created a new class to be called for adding or removing a firebase job.
https://github.com/hispeedimagins/steem/commit/4ebd7b188fda335568e44261b9a295fc4a0a5ba9
Listen to settings changes and then call the relevant method.
https://github.com/hispeedimagins/steem/commit/4641cccea4890fc6ce39df47c4a8632e4775a952

Bug Fixes

Steemit images stopped uploading?
On uploading an image it would return a blank url. The same code worked a month ago. On debug the error was vague.
500 internal server error.
Made multiple changes to everything with no avail.
Decided to download the image hoster souce and see what was wrong.
Provide links to related issues on GitHub, that you fixed, if applicable.
What was the solution?

Download source https://github.com/steemit/imagehoster
If you have windows and plan to use wsl and ubuntu then uninstall avira antivirus. Also install the development toolkit from node, the command will be on their site.
You will need to find the library sharp because it returns 500 from the server.
If you face any error like "lock file locked or something" you can try to delete the lockfile and redo the command. It should work.
It should be running.

Since I have to access this local server via me test device and emulator I had to run these commands

netsh http add urlacl url=http://localhost:8800/ user="NT AUTHORITY\INTERACTIVE"
netsh http add urlacl url=http://*:8800/ user="NT AUTHORITY\INTERACTIVE"

These basically open the port number you require.

netsh advfirewall firewall add rule name="IISExpressWeb" dir=in protocol=tcp localport=5555 profile=private remoteip=localsubnet action=allow

Then this for allowing requests via your firewall.

After all this the real error presented itself.

RangeError: recovery should have value between -1 and 4
at Signature.recover (/mnt/f/imagehoster-master/node_modules/dsteem/lib/crypto.js:271:40)
at uploadHandler (/mnt/f/imagehoster-master/src/upload.ts:122:33)
at process._tickCallback (internal/process/next_tick.js:68:7)

Tried several methods, ways, tried canonical signatures.

Went through source code

The fix?
https://github.com/hispeedimagins/steem/commit/90ad3ff9f704cced9474a0355bd23b809a403eb6

i += 4; // compressed
i += 27; // compact // 24 or 27 :( forcing odd-y 2nd key candidate)

Steem does not check for compressed while making the header byte after making a recoverable key. I was. Seems small right? My code successfully signs all other requests.

Feels so crazy after going through all that for a stupid number.