it looks like we may have accidentally failed to bump rate-limits on the primary bluesky relay, causing a bunch of (legitimate) accounts to not have events get processed.
those limits have been bumped way up, and I will follow up soon to ensure this sort of thing doesn't happen again.
I wish I had elaborate costumes for certain types of programming.
like, oh, newbold is wearing that traditional samurai outfit at his desk again, I guess he's resolving a big merge conflict
last night was "Devil May Caraway" and it was banger
@retr0.id wait does this work well?
if so changes my vibe on USB C a bit. can you do power? what kind of transfer speed?
GitHub - AnasMalas/pcb-edge-us...
(doesn't get "rejected at relay" or anything, just treated as lexicon-non-compliant, so appviews would ignore)
the reason for the future thing is that the sensitive are that once a message is validated, no message with an earlier TID will be accepted. we didn't want an accidental message from 200 years in the future to pseudo-break the account
a future TID is still a totally valid TID for what it is worth, was just sitting that some library might be strict in that peculiar way
but I suspect it will be a fork, new project, or maybe open sourcing of an existing project (eg, something might emerge from ROOST). TBC I think Bluesky can/should/will develop or fund this work.
but it is in contrast to, for example, the PDS reference implementation
the main reason for that is that Ozone has long since passed over a threshold in to "enterprise software" territory, out of "community open source".
the community does desperately need a "community open source" solution in this space...