profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jcayzac/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.
Julien Cayzac jcayzac @rakutentech @rakutenlabs Japan Software engineer & Physics nerd

jcayzac/armv7-functions 17

Implementation of various math, img processing, etc functions for ARMv7 and NEON

jcayzac/F9-Corner-Detection-Library 15

A faster re-implementation of the FAST-9 algorithm (C++, with C bindings available)

jcayzac/androido3d 6

Port of the O3D engine to iOS/Android, with object selection, binary format, etc…

jcayzac/dotfiles 6

dotfiles

jcayzac/ios-overlay 2

iOS SDK library overlay: a repository of static libraries for iOS (iphone, ipad, ipod touch devices)

jcayzac/boost-minidom 1

Lightweight DOM implementation in C++

jcayzac/CDN-GAE 1

Source and deployment scripts for uploading to GAE

jcayzac/awesome-docsify 0

💖 A curated list of awesome things related to docsify

jcayzac/CDN-GAE-Example 0

Example application repository for CDN-GAE

jcayzac/cocoapods-keys 0

A key value store for storing per-developer environment and application keys

GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent

create barnchjcayzac/home

branch : main

created branch time in a day

created repositoryjcayzac/home

🏡

created time in a day

issue closedgitpod-io/gitpod

gitpod requests access to all my github repos

Bug description

GitPod requests access to all my GitHub repos, not just the repo(s) I want to use with GitPod.

Steps to reproduce

  • Add your repo after gitpod.io/# and launch.
  • GitHub asks to grant access to all repos.

Expected behavior

GitHub asks to grant access to that repo only, or to filter which repos can be accessed. I know this is supported, because I just went through this exact flow for enabling the LogSeq app.

Example repository

No response

Anything else?

No response

closed time in 2 days

jcayzac

issue commentgitpod-io/gitpod

gitpod requests access to all my github repos

Thanks for the long explainer.

jcayzac

comment created time in 2 days

startedBoostIO/BoostNote-App

started time in 2 days

issue openedgitpod-io/gitpod

gitpod requests access to all my github repos

Bug description

GitPod requests access to all my GitHub repos, not just the repo(s) I want to use with GitPod.

Steps to reproduce

  • Add your repo after gitpod.io/# and launch.
  • GitHub asks to grant access to all repos.

Expected behavior

GitHub asks to grant access to that repo only, or to filter which repos can be accessed. I know this is supported, because I just went through this exact flow for enabling the LogSeq app.

Example repository

No response

Anything else?

No response

created time in 2 days

startedathensresearch/athens

started time in 3 days

startedfoambubble/foam

started time in 3 days

issue commentw3c/manifest-app-info

Developer information?

Just a comment on the URL format:

Our platform enforces absolute URLs for simplicity, because we actually open these links in the default browser and not in our super app.

Relative links are of course great, but I think it should be explicitly mentioned that absolute URLs are supported as well, and that they are not affected by the scope field —company policy pages are rarely located in the same space as a web app.

jcayzac

comment created time in 8 days

issue commentw3c/manifest-app-info

Developer information?

publisher and policies look good to me 👍🏼

jcayzac

comment created time in 8 days

issue commentmicrosoft/TypeScript

Allow tsconfig.yaml in addition to tsconfig.json

While I like YAML, I also like keeping things simple. If we have to support more formats then anything reading content from tsconfig is going to need another layer of abstraction / more code.

This is typically something that should be abstracted for you by an import.meta.

dradetsky

comment created time in 8 days

startedleils/leils.github.io

started time in 14 days

issue commentw3c/manifest-app-info

Request for additional categories

Our platform also has the following categories:

  • beauty
  • car
  • dating
  • developer this is the same as development in Filip's message.
  • events
  • graphics this is the same as design in Filip's message.
  • parenting
  • pets
  • reference agree with Filip. Dictionary apps, wikis, interactive encyclopedias etc aren't books.

Also, from the existing list, I'm not sure exactly what's the difference between donations and fundraising.

filips123

comment created time in 15 days

issue commentw3c/manifest-app-info

Developer information?

@aarongustafson Thanks for moving the issue. I didn't know there was a proposal already for supplemental app information. I just read the draft and liked what I saw a lot. Thanks for writing it.

Regarding your questions, and the factors that guided our current implementation above:

Current popular distribution channels for apps (Apple App Store, Google Play Store, etc) don't have a distinction between developer*, publisher or seller, and the terms there often seem interchangeable. Support/privacy/TOS links are also directly relevant to the app itself, not much so to the larger entity who published it. Only the "developer website" links to the organization.

Functionally, I think this maps well to the Service and Organization schemas I linked to in my original message, but we wanted to avoid the complexity of those schema by keeping only a subset of the most common information. The discussions around these schemas in https://github.com/schemaorg/schemaorg are very interesting to read.

Our implementation also packages this information into an object field, rather than spreading the fields at the top level of the manifest. This was both to avoid collisions with other extensions of the web manifest, and to make the data better structured. But maybe a single object isn't the best option after all.


* The developer information, when talking about the people who actually wrote the code, is usually not exposed by the various app stores. On the web, agencies use humans.txt for this.

jcayzac

comment created time in 15 days

issue openedw3c/manifest-app-info

Developer information?

Hi,

Rakuten has started to add support for third-party merchant websites in its mobile payment application, based on PWA. The catalogue of web apps you can "install" and use in our "super app" thus gets all the app's metadata from its web manifest.

When a user launches a 3rd-party app the first time, a dialog is shown to present some information about it: name of the developer with an optional URL, as well as links to the app's privacy policy, terms of use and support site. This information is also available from the web view menu once the web app is opened.

Although a few schemas could be used, for instance Organization or Service, they are quite complex. Moreover, JSON-LD seems out of place in a manifest, and the schemas too obscure for us to expect them be used in merchants' web apps either.

Our current implementation thus takes inspiration from Kai OS webapp manifest, which feels more "idiomatic":

"developer"

  • Type: Object
  • Mandatory: No

Developer information. Use this to provide information about your company and your service to end-users. The recognized keys are shown below, and most are optional.

Key Description
name (Mandatory) If you provide a developer object, it must at least contain the name of your company.
url Absolute URL of your company's main website (optional).
privacy_policy_url Absolute URL of the page detailing your company's privacy policy (optional).
terms_of_service_url Absolute URL of the page detailing your service's terms and conditions (optional).
support_url Absolute URL of a page with methods for end-users to contact you for support (optional).

Although our user agent is a super app, we think this metadata would also have value in a web manifest for web browsers. Without this, discovering the information relies on parsing the HTML DOM and looking for many complex schemas with a lot of fragmentation, with no easily predicable behavior.

created time in 15 days

issue commentw3c/manifest

Developer information?

@tomayac unfortunately it's not public yet. I copy-pasted the part relevant to the "developer" field above.

jcayzac

comment created time in 15 days

issue openedw3c/manifest

Developer information?

Hi,

Rakuten has started to add support for third-party merchant websites in its mobile payment application, based on PWA. The catalogue of web apps you can "install" and use in our "super app" thus gets all the app's metadata from its web manifest.

When a user launches a 3rd-party app the first time, a dialog is show to present some information about it: name of the developer with an optional URL, as well as links to the app's privacy policy, terms of use and support site. This information is also available from the web view menu once the web app is opened.

Although a few schemas could be used, for instance Organization or Service, they are quite complex. Moreover, JSON-LD seems out of place in a manifest, and the schemas too obscure for us to expect them be used in merchants' web apps either.

Our current implementation thus takes inspiration from Kai OS webapp manifest, which feels more "idiomatic":

"developer"

  • Type: Object
  • Mandatory: No

Developer information. Use this to provide information about your company and your service to end-users. The recognized keys are show below, and most are optional.

Key Description
name (Mandatory) If you provide a developer object, it must at least contain the name of your company.
url Absolute URL of your company's main website (optional).
privacy_policy_url Absolute URL of the page detailing your company's privacy policy (optional).
terms_of_service_url Absolute URL of the page detailing your service's terms and conditions (optional).
support_url Absolute URL of a page with methods for end-users to contact you for support (optional).

Although our user agent is a super app, we think this metadata would also have value in a web manifest for web browsers. Without this, discovering the information relies on parsing the HTML DOM and looking for many complex schemas with a lot of fragmentation, with no easily predicable behavior.

created time in 16 days

startedadr/madr

started time in 21 days

issue closedvolta-cli/volta

[BUG] Updating node doesn't update npm's target dir for binaries

Until now my configuration was:

  "volta": {
    "node": "16.5.0",
    "npm": "7.21.0"
  }

…and npm happily reported:

$ npm bin -g
/Users/julien.cayzac/.volta/tools/image/node/16.5.0/bin

Now I just updated to a more recent version of node:

   "volta": {
-    "node": "16.5.0",
+    "node": "16.7.0",
     "npm": "7.21.0"
   }
$ node --version
v16.7.0

However, npm now makes me sad:

$ npm bin -g
/Users/julien.cayzac/.volta/tools/image/node/16.5.0/bin

closed time in 22 days

jcayzac