profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/waldyrious/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Waldir Pimenta waldyrious @feedzai Braga, Portugal https://zmoazeni.github.io/gitspective/#/timeline/waldyrious I'm a big fan of open content, open source, intrinsically-motivated work and collaboration over competition. Wikipedian, anarchist and basic income supporter.

tldr-pages/tldr 35579

📚 Collaborative cheatsheets for console commands

lukasz-madon/awesome-remote-job 21070

A curated list of awesome remote jobs and resources. Inspired by https://github.com/vinta/awesome-python

alerque/libertinus 592

The Libertinus font family

tldr-pages/tldr-python-client 372

Python command-line client for tldr pages

HatScripts/circle-flags 244

A collection of 300+ minimal circular SVG country flags

hamstar/Wikimate 57

A MediaWiki API wrapper for PHP based wikibots that [shouldn't] be confusing to use

tldr-pages/tldr-pages.github.io 44

The website for the tldr pages project

dissemin/oabot 31

Adding links to full text in Wikipedia references

JuliaMath/Tau.jl 28

A Julia module providing the definition of the circle constant Tau (2π)

edgurgel/tldr_elixir_client 14

Elixir command line client for tldr

Pull request review commentuphold/docs

Update webhooks doc

 That header is built by signing the request body with the previously provided se       }     }   },+  "retries": 0,+  "type": "card:updated",   "userId": "e5b23ad5-6c1e-44d0-a49d-a080135fc083" }- ``` -Returns the card details and context whenever a card has changed its `available` or `balance`, i.e. whenever it sends or receives a transaction.-The context includes the id of that transaction.- This webhook returns the following payload:  Parameter | Description ----------|--------------------------------------- id        | The id of the updated card.-context   | a JSON object with additional context.+context   | A JSON object with additional context.  The additional context includes the following details:  Parameter   | Description ------------|------------------------------------------------------------------------ transaction | A JSON object with the id of the transaction that triggered the update.++It returns the card details and context whenever a card has changed its `available` or `balance`, i.e. whenever it sends or receives a transaction.+The context includes the id of that transaction.++## Oauth authorization revoked++This webhook is triggered when a user that had previously authorized your app decides to remove said authorization. When this happens, you'll receive a request informing you of which user has removed the authorization. To subscribe to these updates, you'll need to configure a webhook with the "OAuth Authorization Revoked" scope.++> The following is a `oauth-authorization:revoked` webhook payload example:++```json+{+  "createdAt": "2018-05-03T12:25:21.809Z",+  "id": "c4db98e4-c9e1-46dc-a927-17a26fb9772c",+  "payload": {+    "id": "758d3c93-5f00-46dd-a1b3-facdc215e09b"+  },+  "retries": 0,+  "type": "oauth-authorization:revoked",+  "userId": "e5b23ad5-6c1e-44d0-a49d-a080135fc083"+}+```++This webhook returns the following payload:++Parameter | Description+----------|---------------------------------------+id        | The id of the authorization.++It returns the `id` of the authorization that was revoked.++## Transaction status++When you create a transaction, the first set of validations is run and you'll get an error if the transaction request is not valid. Otherwise, the request is completed successfully and the response body will contain a `status` property with value `processing`. In the meantime, we perform another set of validations that can lead to a transaction's `status` becoming `failed` or `completed`. This asynchronous behavior can be handled by subscribing to a webhook with the "Transaction Status Updated" scope, which will allow you to receive updates whenever a transaction created by your user changes its `status`.

Maybe "created by your application" would be more accurate?

hitmanmcc

comment created time in 2 days

PullRequestReviewEvent

Pull request review commentuphold/docs

Update webhooks doc

 That header is built by signing the request body with the previously provided se       }     }   },+  "retries": 0,+  "type": "card:updated",   "userId": "e5b23ad5-6c1e-44d0-a49d-a080135fc083" }- ``` -Returns the card details and context whenever a card has changed its `available` or `balance`, i.e. whenever it sends or receives a transaction.-The context includes the id of that transaction.- This webhook returns the following payload:  Parameter | Description ----------|--------------------------------------- id        | The id of the updated card.-context   | a JSON object with additional context.+context   | A JSON object with additional context.  The additional context includes the following details:  Parameter   | Description ------------|------------------------------------------------------------------------ transaction | A JSON object with the id of the transaction that triggered the update.++It returns the card details and context whenever a card has changed its `available` or `balance`, i.e. whenever it sends or receives a transaction.+The context includes the id of that transaction.++## Oauth authorization revoked++This webhook is triggered when a user that had previously authorized your app decides to remove said authorization. When this happens, you'll receive a request informing you of which user has removed the authorization. To subscribe to these updates, you'll need to configure a webhook with the "OAuth Authorization Revoked" scope.++> The following is a `oauth-authorization:revoked` webhook payload example:++```json+{+  "createdAt": "2018-05-03T12:25:21.809Z",+  "id": "c4db98e4-c9e1-46dc-a927-17a26fb9772c",+  "payload": {+    "id": "758d3c93-5f00-46dd-a1b3-facdc215e09b"+  },+  "retries": 0,+  "type": "oauth-authorization:revoked",+  "userId": "e5b23ad5-6c1e-44d0-a49d-a080135fc083"+}+```++This webhook returns the following payload:++Parameter | Description+----------|---------------------------------------+id        | The id of the authorization.++It returns the `id` of the authorization that was revoked.++## Transaction status++When you create a transaction, the first set of validations is run and you'll get an error if the transaction request is not valid. Otherwise, the request is completed successfully and the response body will contain a `status` property with value `processing`. In the meantime, we perform another set of validations that can lead to a transaction's `status` becoming `failed` or `completed`. This asynchronous behavior can be handled by subscribing to a webhook with the "Transaction Status Updated" scope, which will allow you to receive updates whenever a transaction created by your user changes its `status`.++> The following is a `transaction:status:updated` webhook payload example:++```json+{+  "createdAt": "2018-05-03T12:25:21.809Z",+  "id": "c4db98e4-c9e1-46dc-a927-17a26fb9772c",+  "payload": {+    "id": "c4a77706-7b3a-4b8b-968b-4190038d37e8",+    "status":  "waiting|cancelled|failed|completed"+  },+  "retries": 0,+  "type": "transaction:status:updated",+  "userId": "e5b23ad5-6c1e-44d0-a49d-a080135fc083"+}+```++This webhook returns the following payload:++Parameter | Description+----------|-------------------------------------------------------------------------+id        | The id of the transaction.+status    | A string with the transaction status that triggered the hook.+|         | Possible values are: `cancelled` \| `completed` \| `failed` \| `waiting`++It returns the `id` of the created transaction, along with it's current `status`.
It returns the `id` of the created transaction, along with its current `status`.
hitmanmcc

comment created time in 2 days

PullRequestReviewEvent

Pull request review commentuphold/docs

Update webhooks doc

 type      | Type of the notification (e.g. `card:updated`). payload   | JSON with the actual model data being sent by the webhook. userId    | Unique identifier of the Uphold user that owns the resource. +In addition, the request also includes a signature header, that can be used to verify that the request body has not been tampered with.+That header is generated by signing the request body with the previously provided secret, using the SHA512 algorithm.+ > Example of signature header:  ``` sha512=040518ad86dd4bea08ba6d23240f53a9f35175bcb3c548e83f33acc792aabcafe29954f92b0e1d6ede9192c851b3ba0768f760f516e168c7b318a17d2714bf52 ``` -In addition, the request also includes a signature header, that can be used to verify the request body has not been tampered with.-That header is built by signing the request body with the previously provided secret, using the SHA512 algorithm.+## Card updated -## Card Updated+If you want to track whenever a given card's balance changes, you can use the "Card Updated" scope. This is useful when you want to perform actions regarding the user's total balance or the balance of a specific card, so that you can act accordingly.

I'd recommend either "track changes to a given card's balance" or "be notified whenever a given card's balance changes". Although the meaning of "track" and "be notified" is similar, they're not exactly synonyms, and thus they require slightly different sentence structures.

hitmanmcc

comment created time in 2 days

PullRequestReviewEvent

push eventwaldyrious/parquet-site

Waldir Pimenta

commit sha 58d1f7600dd69053b2ccaeb58c038dce343003f2

documentation/latest: fix typo, adjust formatting

view details

push time in 2 days

issue commentcli/cli

`gh extension list` is very slow

Hey @samcoe — I have had the chance to test gh 2.1.0, but even with this check for updates now done concurrently, it is still taking me several seconds to see the output (even more than before, ironically — although of course network latency variations will affect the results). As the original reporter, I would not consider this issue resolved until the times are much closer to a plain listing of ~/.local/share/gh/extensions/. Please reopen the issue.

waldyrious

comment created time in 3 days

delete branch waldyrious/website

delete branch : read-more-links

delete time in 3 days

startednodeca/unhomoglyph

started time in 3 days

issue commentelementary/website

Incorrect encoding in OEM page

Unfortunately I forgot to note the exact version of the Brave browser where I experienced the bug, but in any case I doubt it was an issue with the browser that was fixed with an update, because as I mentioned in my previous comment, simply reloading the page, without updating the browser, made the issue go away. (Unless it was an intermittent bug that they fixed in the 1.30.89 release?)

waldyrious

comment created time in 6 days

issue openedrefined-github/refined-github

Incorrect vertical alignment for real names in show-names feature

Please ensure:

  • [X] The bug is caused by Refined GitHub. It doesn't happen if I disable the extension.

Include in this issue:

  • [X] Screenshots/video/gif demonstrating the bug, if it’s visual
  • [ ] Console errors, if any

Description

Real names are vertically misaligned in the header of inline comments in PRs. This does not happen in non-comment updates, nor in headers of non-inline comments.

Screenshot (of the example URL given below):

Screenshot from 2021-10-15 11-02-31

Example URL

https://github.com/pcottle/learnGitBranching/pull/824#discussion_r616113222

Browser(s) used

Firefox 93

created time in 9 days

pull request commentpcottle/learnGitBranching

Fix main main reference

For context, this was pointed out by @ElLutzo here.

pcottle

comment created time in 9 days

CommitCommentEvent

startedalpinejs/alpine

started time in 9 days

PR opened vuejs/petite-vue

docs: add links for context; small wording fixes

Just a handful of small improvements to the README.

+2 -2

0 comment

1 changed file

pr created time in 9 days

push eventwaldyrious/petite-vue

Waldir Pimenta

commit sha c4a90c2f393bc46d6dd6f4eab7adf0df95e787b4

docs: add links for context; small wording fixes

view details

push time in 9 days

fork waldyrious/petite-vue

6kb subset of Vue optimized for progressive enhancement

fork in 9 days

startedvuejs/petite-vue

started time in 9 days

delete branch waldyrious/git-fame

delete branch : hyphen

delete time in 9 days

issue commentlesspass/lesspass

kinda strange how newest version on web stores is 9.4 meanwhile latest on github is 9.1.9

where did you see the version 9.1.9?

I believe they may be referring to https://github.com/lesspass/lesspass/releases. The last tag shown there (at the time I'm writing this) is indeed 9.1.9:

Screenshot from 2021-10-13 11-52-21

The discrepancy refer to appears to be in contrast with the version of the web extension:

https://github.com/lesspass/lesspass/blob/5d3336c92c397c41c808455ebfdb08b2f1bee2d0/packages/lesspass-web-extension/package.json#L4

Since the versions for different packages within the repository appear to be bumped independently from each other, perhaps there could be a system of git tags prefixed (or suffixed) by the appropriate package name, e.g. lesspass-web-extension-9.4.1 or 9.4.1+lesspass-web-extension. The latter should be semver-compatible AFAIK.

Assuming there's an automated process that generates the "Auto build for lesspass-web-extension" commits (e.g. 2aba4a560d2385344742cd12f28efda14f9fc21a, 3b1699234a65812188be2a219c72f9558a2e1720, d394c15a537221849d7a40d94a4e42ea983c4d38) maybe it could be extended to also generate a tag for the git commit.

D0nnieD4rk0

comment created time in 11 days

pull request commenttldr-pages/tldr-lint

Add tldr-pages as copyright holder in License

but not sure if there's a good email address to put for the tldr org, and just leave that blank.

Just dropping by to note that there's a mailing list, tldr-pages@googlegroups.com, that could be used for this purpose. It never got much (well, any) traction, and the list of enrolled people hasn't been kept up to date with tldr-pages org members, but we could certainly sync them and use it for this purpose.

MasterOdin

comment created time in 11 days

issue commentjfoclpf/geoptapi

Agregar por distrito

Não deveria ser /distritos, para consistência com os níveis abaixo?

jfoclpf

comment created time in 13 days

push eventwikimedia-portugal/areas-protegidas-pt

Waldir Pimenta

commit sha 3dd8cfd9fa9215b752ac9b27b00b90baf9a54c1b

Escape article titles for link labels

view details

Waldir Pimenta

commit sha 5ca55ebf9d5e9c3865fea5c1806392b04848574e

Add script-generated HTML files for all contintental districts

view details

push time in 13 days

issue commentbrave/brave-browser

Emoji not displaying on Kubuntu 19.04 stable

I actually still see this issue, e.g. in Gmail when labeling a conversation:

Brave Firefox
Brave screenshot Firefox screenshot

Interestingly, once the conversation is labeled (and in the labels listed in the sidebar), the emoji appear correctly. They only show up weirdly in the labeling dialog. Not sure what's going on there.

Mitsunee

comment created time in 16 days

PullRequestReviewEvent

Pull request review commentdavidraviv/gh-clean-branches

add force flag

 gh extension install davidraviv/gh-clean-branches ## Usage Execute it inside a git repo folder: ```bash-gh clean-branches [--dry-run]+gh clean-branches [--dry-run] [--force] ``` Use the `--dry-run` flag to see the list of branches to be deleted before actually deleting them.+Use the `--force` flag to toggle the `-D` command and force a branch to be deleted regardless if upstream changes have local changes.

Did you perhaps mean "if upstream branches have local changes"?

rizowski

comment created time in 16 days

issue commentdenoland/rusty_v8

Add support for ICU

done.

Just for the record, it appears that the main PR for this was https://github.com/denoland/rusty_v8/pull/603.

kitsonk

comment created time in 16 days