Smitty

@mvandeberg Why was this closed? It doesn't look like this is supported. (and it was transfered to the right repo)

Are you sure you’re using your active key (*not* your signing key, posting key, or memo key) in the first argument to the updateWitness function? What code are you trying?

Does it work when you run JSON.stringify on the owner, active, and posting authorities?

It might be a problem with the default Steem WebSocket. Try putting this line before you do anything on the Steem network. ``` steem.api.setOptions({ url: 'wss://node.steem.ws' }); ```

I ran a tool to check for this. This also happens with: ``` node-fetch co-request cheerio date-names pluralizers immutable ```

PostgreSQL 15 is released! 🎉 I updated the PR so that it runs PostgreSQL 15 in CI now that APT packages are available. I've also removed the code that used...

> Alternatively, doing nothing here would push folks not to glob import pg_sys, which is kind of a good thing... I suppose that kind of change might be better done...

Any update on when we might be able to get this PR in?

As you're likely aware, [this was intentional](https://github.com/steemit/steem/commit/a101bd8c31df18a4f0ca7b107491a8e2eacb6c0b#diff-5f5356c18939f3b2ce7f3e74ab944614R67).

@us3r01 Steemit uses [this list](https://github.com/steemit/condenser/blob/master/src/app/utils/GDPRUserList.js) for determining which accounts to hide. of course other frontends have their own lists.