We had the same issue many years ago with the reactiflux community. We ended up moving to discord and that was the best decision ever. Discord has been an extremely welcoming place for all these kind of communities.
Readit Newsvjeux commented on Slack has raised our charges by $195k per year mahadk.com/posts/slack... · Posted by u/JustSkyfall
And ("vanilla") tldraw supports subpixel font rendering, unlike most of their competition (for example excalidraw or Miro).
We actually intentionally round it to the nearest pixel in excalidraw because otherwise the font tends to be blurry. We may want to reconsider.
Love the illustrations, really great usage of excalidraw!
vjeux commented on Leveraging AI for efficient incident response engineering.fb.com/2024/0... · Posted by u/Amaresh
Im really interested in the implied restriction/focus on “code changes.”
IME a very very large number of impacting incidents arent strictly tied to “a” code change, if any at all. It _feels_ like theres an implied solution to tying running version back to deployment rev, to deployment artifacts, and vcs.
Boundary conditions and state changes in the distributed system were the biggest bug bear I ran in to at AWS. Then below that were all of the “infra” style failures like network faults, latency, API quota exhaustion, etc. And for all the cloudformation/cdk/terraform in the world its non trivial to really discover those effects and tie them to a “code change.” Totally ignoring older tools that may be managed via CLI or the ol’ point and click.
From my experience, the vast majority of reliability issues at Meta come from 3 areas:
- Code changes
- Configuration changes (this includes the equivalent of server topology changes like cloudformation, quota changes)
- Experimentation rollout changes
There has been issues that are external (like user behavior change for new year / world cup final, physical connection between datacenters being severed…) but they tend to be a lot less frequent.
All the 3 big buckets are tied to a single trackable change with an id so this leads to the ability to do those kind of automated root cause analysis at scale.
Now, Meta is mostly a closed loop where all the infra and product is controlled as one entity so those results may not be applicable outside.
excalidraw.com is a PWA, but not unsure how helpful it’s going to be as comparison. As mentioned in the comments, success is likely more due to the usefulness of the app rather than the tech used. vjeuxx@gmail.com if you wanna chat.
Thank you so much for working on this! I strongly believe that we need as a community to invest in an open source video editor based on the web using WebCodec. I did a talk last year to beg people to work on it! https://youtu.be/0cb0Bq4gLPo?si=7sPcAuH_9CDzM4xg
Let me know if I can be of any help. vjeuxx@gmail.com
It is. But I noticed something weird. If your prompt is “A cartoon of XYZ” and press enter the preview will be a cartoon but the other images will be weird realistic ones.
The preview is using a different faster model so you're not going to get the exact same styles of responses from the larger slower one. If you have ideas on how to make the user experience better based on those constraints please let us know!
Yeah, there's no way I'm signing up to FB just to try this. The output is surprisingly good so far. And it's fast, and feels lightweight. If someone from Meta is reading this, do please add the stylesheet to "print to PDF". I suggested it to my friends at OpenAI but the suggestion got ignored. This would be a rather obviously useful feature.
Thanks for the suggestion, will look into implementing it!