Replies: 5 comments 8 replies
-
|
For FAIR Beacon: Summarize Slack discussion with @afragen @costdev @namithj @jdevalk concerning 403 Errors and potentially caching zip files in Beacon. Add discussion of caching image assets as well due to potential PI leakage with hotlinking. |
Beta Was this translation helpful? Give feedback.
-
|
For FAIR Connect & Beacon: (from Slack thread) propose we deprecate sha256 now in favour of sha384 or better (in addition to Ed25519). While sha256 is still widely used, it's gradually falling out of favour with stronger options being readily available. The FAIR Protocol docs call for supporting sha256, but security recommendations suggest we don't. We're starting fresh with no burden of backward compatibility, so it makes sense to start high and avoid having to deprecate later. |
Beta Was this translation helpful? Give feedback.
-
|
Fair Onboarding Github Action
|
Beta Was this translation helpful? Give feedback.
-
|
1.2.1?? |
Beta Was this translation helpful? Give feedback.
-
|
AI-generated notes: GitHub Asset Caching & Rate Limiting Solutions
WordPress Plugin Metadata & Protocol Updates
Infrastructure & Deployment Improvements
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Meeting Purpose: Deep-dive, hands-on technical work & implementation for FAIR.
Audience: All technical contributors (not just committee members).
Please add agenda items as comments below and up-vote on the items you'd like to discuss.
Meeting details
How to join
This call is open to anyone, but note that you need to have a profile/account at OpenProfile.dev to join the call.
Reminders
FAIR is part of the Linux Foundation. Meeting attendees are subject to both the Code of Conduct and the LF Antitrust Policy.
This meeting is recorded and publicly available via your OpenProfile.dev account.
Beta Was this translation helpful? Give feedback.
All reactions