@unwriter is on PowPing!

PowPing is a place where you can earn Bitcoin simply by socializing, for FREE.
Never tried Bitcoin? It's OK! Just come, socialize, and earn Bitcoin.
Check out unwriter's activities
Total Economy: 1.17 USD
Now you can switch back and forth between "Instant" and "Strict" modes. There are pros and cons for each method. The "strict" mode is the original approach, where it lets you explicitly approve every action through a wallet popup, giving you control over signed data. This means you have to swipe for every post, and swipe twice for every time you tip someone. The "instant" mode lets you post instantly without this step, providing convenience. You can always switch back and forth easily. Try it at https://powping.com/settings
vicarcalsado tipped:
0.58 USD
1 year ago
esryix tipped:
0.18 USD
1 year ago
vegardwikeby tipped:
0.02 USD
1 year ago
jasmr tipped:
0.4 USD
1 year ago
I am happy to use strict mode. Instant still not working in either Brave (with shields down) on Win10 and Chromium Edge browser on Win10 - haven't tried it on Linux yet...
hojarasca replied:
Hi, jasmr. My name is Miguel, I'm a developer at Money Button :). Can you describe how it fails? In the meantime I'm going to try edge and chrome in windows. Thanks in advance.
Nothing bits choice, specially when each option adapts to what you need, when you need it
Instant mode still not working for me, I'm using Chrome Version 84.0.4147.89 (Official Build) (64-bit). I tried switching modes back and forth too
unwriter replied:
try logging out completely and log back in
cryptofu replied:
I tried that and switching modes, then logging back in. Instant still not working. Are there any setting I can try on Moneybutton too? I couldn't see any
unwriter replied:
Can you look inside the browser console if you know how to do it? If you can share what error message you’re seeing inside, that would be helpful in diagnosing. Btw, is this just instant mode not working? Or is strict mode also not working?
cryptofu replied:
@unwriter I sent you a baemail with the console output and errors. Just instant is not working, strict is working. Maybe it's conflicting with Metamask in some way. I tried logging into Metamask and doing an instant post but that didn't work either.
unwriter replied:
hmm i can't see your mail on baemail
hojarascadev replied:
Hi,@cryptofu . My name is Miguel, I'm a developer at Money Button. Can you describe how it fails, please?. Thanks in advance, and sorry for the inconvenience.
cryptofu replied:
I sent it using the messaging on here which in turn went via baemail to 644@moneybutton.com
cryptofu replied:
A cookie associated with a cross-site resource at http://unpkg.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592'>https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032'>https://www.chromestatus.com/feature/5633521622188032. DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME (index):1 A cookie associated with a cross-site resource at http://www.moneybutton.com/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032. (index):5760 id #nav-search DevTools failed to load SourceMap: Could not load content for https://unpkg.com/@popperjs/popper.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE DevTools failed to load SourceMap: Could not load content for https://unpkg.com/tippy-bundle.umd.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE (index):5833 Settings = {wallet: {…}} sign.js:245 sessionToken = null inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change. For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange'>https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange Set 'ethereum.autoRefreshOnNetworkChange' to 'false' to silence this warning. (anonymous) @ inpage.js:1 setTimeout (async) t.exports @ inpage.js:1 initProvider @ inpage.js:1 (anonymous) @ inpage.js:1 1../lib/auto-reload.js @ inpage.js:1 i @ inpage.js:1 e @ inpage.js:1 (anonymous) @ inpage.js:1 (anonymous) @ contentscript.js:1 1.@babel/runtime/helpers/interopRequireDefault @ contentscript.js:1 i @ contentscript.js:1 e @ contentscript.js:1 (anonymous) @ contentscript.js:1 (index):5880 text = test sign.js:143 signing undefined sign.js:154 got hash DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change. For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange Set 'ethereum.autoRefreshOnNetworkChange' to 'false' to silence this warning. (anonymous) @ VM151 inpage.js:1 setTimeout (async) t.exports @ VM151 inpage.js:1 initProvider @ VM151 inpage.js:1 (anonymous) @ VM151 inpage.js:1 1../lib/auto-reload.js @ VM151 inpage.js:1 i @ VM151 inpage.js:1 e @ VM151 inpage.js:1 (anonymous) @ VM151 inpage.js:1 (anonymous) @ VM150 contentscript.js:1 1.@babel/runtime/helpers/interopRequireDefault @ VM150 contentscript.js:1 i @ VM150 contentscript.js:1 e @ VM150 contentscript.js:1 (anonymous) @ VM150 contentscript.js:1 sign.js:189 error {reason: "invalid-app-domain", data: {…}} 2 Issues are as follows Indicate whether to send a cookie in a cross-site request by specifying its SameSite attribute Because a cookie's SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevent the cookie from being sent in a cross-site request in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes of the cookie: Specify SameSite=None and Secure if the cookie should be sent in cross-site requests. This enables third-party use. Specify SameSite=Strict or SameSite=Lax if the cookie should not be sent in cross-site requests AFFECTED RESOURCES 3 cookies Name Domain & Path _ga .unpkg.com/ _gid .unpkg.com/ AWSALB www.moneybutton.com/ 25 requests core@2 core@2.4.4 popper.min.js tippy.js@6 tippy.js@6.2.5 tippy-bundle.umd.min.js autosize autosize@4.0.2 autosize.js moneybutton.js bitpacket bitpacket@0.0.18 bitpacket.min.js imb-permission-grant user_identity 7492 currency currency client_identifier=f7b46437bc9d72b82eabd9e435081793 white-isologo.svg permissions.png pay_blue.svg sign-in_yellow.svg lock_black.svg unlock_salmon.svg Learn more: SameSite cookies explained Indicate whether a cookie is intended to be set in cross-site context by specifying its SameSite attribute Because a cookie's SameSite attribute was not set or is invalid, it defaults to SameSite=Lax, which will prevents the cookie from being set in a cross-site context in a future version of the browser. This behavior protects user data from accidentally leaking to third parties and cross-site request forgery. Resolve this issue by updating the attributes of the cookie: Specify SameSite=None and Secure if the cookie is intended to be set in cross-site contexts. Note that only cookies sent over HTTPS may use the Secure attribute. Specify SameSite=Strict or SameSite=Lax if the cookie should not be set by cross-site requests AFFECTED RESOURCES 1 cookie Name Domain & Path AWSALB www.moneybutton.com/ 7 requests moneybutton.js imb-permission-grant user_identity 7492 currency currency client_identifier=f7b46437bc9d72b82eabd9e435081793 Learn more: SameSite cookies explained
It is better to have options. Thanks sir for a valuable work
nice
Nice
You can switch modes by clicking the "change" button at the top. Also, if you're having trouble posting in instant mode, try switching to strict mode and then back to instant mode, and retry. If that doesn't work, let me know. Or you can also keep using the strict mode. As mentioned, there is no absolutely superior method, there are tradeoffs.