Weekly Sync - 09 April 2024

[github-actions[bot]]

Please add agenda items below and give your weekly update in a comment. Thank you!

Agenda

• @Tymmmy : Introduction of our new BreakPointIt colleague Arpi :)
• @sabineschaller : reducing default max packet size
• @sabineschaller & @BlairCurrey : redis going source available
  • https://redis.io/blog/redis-adopts-dual-source-available-licensing/
  • https://lwn.net/Articles/966133/
  • https://news.ycombinator.com/item?id=39772562
• @beniaminmunteanu : graphql codegen max-Depth issues due to gqlArmor -> ignoreIntrospection: true

Discussion

1. Timea introduced Arpi from Breakpoint

2. Reducing Default Max Packet Size

• Currently the default is set to the largest possible bigint value.
• There was discussion on whether there is a need to reduce it to lower network risks.
• However, packet loss is not an immediate concern, since all current peering plans will be direct peering relationships. In this case lowering max packet size is not a big issue.
• Also maxPacketSize is configurable.
• Suggestion to keep the current settings on the radar and revisit if the network grows and peering becomes more common.

3. Redis Going Source Available

• Redis announced a change in its licensing model, moving from BSD to a source-available license with restrictions against competitive offerings.
• The change is unlikely to affect the Rafiki project directly.
• There is also uncertainty if this change will happen due to concerns in the community and licensing issues.
• There was also discussion about whether we need Redis at all? On the one hand this hinges on whether we need to support STREAM receipts. But on the other hand we have in-memory functionality that we might still want to port over to Redis (e.g. Koa sessions in auth, the idempotency key). So we may well use Redis more in the future.
• Suggestion to just use Postgres if we do have a problem with Redis. See https://www.amazingcto.com/postgres-for-everything/

4. GraphQL Codegen Max-Depth Issues

• Issues encountered while updating Rafiki money to alpha8 due to GraphQL Codegen tool's inability to handle deep queries because of gqlArmor settings.
• Problem with generating GraphQL schemas due to the addition of graphql amour, causing blocking of deep queries.
• Resolution by setting ignoreIntrospection: true, raising questions about potential security concerns.
• Discussion on the limited impact due to the admin API being a private interface, not affecting integrators.
• Points were raised about the value of considering the developer experience when it comes to using private apis with graphql. Exposing the depth makes things much easier.

[BlairCurrey]

• working on making quote step optional. have open payments changes and most of rafiki changes roughed out

[mkurapov]

• Ready for review: feat(backend): adding OpenPaymentsServerRouteError #2635
• Will focus on adding changes to Open Payments SDK in preparation for use in the web monetization manfiest V3

[njlie]

• Finished code changes for Admin API Security using signatures & shared secrets
  • Just need to update Bruno collection for the branch

[Tymmmy]

• Onboarding process planning, and meetings
• Working on ILPay v1

[beniaminmunteanu]

Local payments tracking PR
Testnet discussions
Onboarding
Telemetry article review

[JoblersTune]

Completed telemetry blog post.
Have a PR in to use Kratos to secure the Admin UI. Almost through the review process.