OneDeuxTriSeiGo

5 ms·

31.
by OneDeuxTriSeiGo 2mo ago
Yeah safety critical software needs to avoid high UI density for the interface itself. For diagnostics and monitoring or general stats you can still do high density but the actual "action space" needs to be kept as low density as
32.
by OneDeuxTriSeiGo 2mo ago
FWIW if you listen to Signals and Threads (the Jane Street podcast) they talk about this. They have dedicated UX designers who do relatively little code but focus entirely on making the UX as optimal for the traders as possible and one of t
33.
by OneDeuxTriSeiGo 2mo ago
The first five links (i.e. not the book) are each only a few printed pages worth of text each or less. All together they are equivalent to like a single chapter of text in a book. It really won't take hours. You probably read more than
34.
by OneDeuxTriSeiGo 2mo ago
It's not recommended because you can just use the --autosquash flag. No reason to make it the default. especially since if you are rebasing you may want to rebase your changes from one branch to another (i.e. move to top of main or fro
35.
by OneDeuxTriSeiGo 2mo ago
Git has been re-designing their tooling over the last few years. Nowadays there exist really pleasant, easy to use versions of the main tools. switch and restore replaced checkout. history is being developed to replace rebase for most commo
36.
by OneDeuxTriSeiGo 2mo ago
Have you ever read any of the introductory material that the git project itself maintains for teaching how to use the tool? - https://git-scm.com/docs/gittutorial - https://git-scm.com/docs/gitever
37.
by OneDeuxTriSeiGo 2mo ago
Understanding git rebase is important. You aren't expected to rebase mainline branches regularly but if your team operates on a merge/patchset workflow and isn't just squashing everything down onto main each PR you need to un
38.
by OneDeuxTriSeiGo 2mo ago
For github itself the answer is "contact them if you think you pushed a secret". For git. You can run `git maintenance run` or the legacy command `git gc`.
39.
by OneDeuxTriSeiGo 3mo ago
oh nice is there a tracking issue for this somewhere? I've taken a peek at the issues in the org on github but i didn't see one off the bat (mainly because there's a ton of other SMS related issues that pop up from history)
40.
by OneDeuxTriSeiGo 3mo ago
Tbh I have no idea. I kept up with it on the GrapheneOS discord and I think GOS put out bluesky/mastodon posts about it at one point. > What's left in terms of meaningful technical barriers, that would prevent this all from bei
41.
by OneDeuxTriSeiGo 3mo ago
So the issue with RCS is that google just this last year made the move from their internal implementation of E2EE for RCS to the standard implementation based on MLS (now that the standard impl is actually viable). They did this quietly in
42.
by OneDeuxTriSeiGo 3mo ago
Kagi nowadays has a feature called "SlopStop" that you can opt into. It's basically a global block list for LLM generated websites, etc that is shared across all users who opt into and anyone can report sites/content to
43.
by OneDeuxTriSeiGo 3mo ago
fwiw tangled itself is also an appview and they are gradually working on rebuilding it around their new XRPC oriented appview called bobbin. The appeal of bobbin is it's fully stateless and pretty lightweight. IIRC you can run all the
44.
by OneDeuxTriSeiGo 3mo ago
That's the advantage of picking a theme. So the project is called tangled. So everything is string/web themed. Knots, spindles, bobbins, etc
45.
by OneDeuxTriSeiGo 3mo ago
I'm not sure what's been published but as someone who plays with tangled as a hobby the immediate monetisation paths I could see are: - Charging to bypass the (admittedly very reasonable) rate limits on the main appview - Providin
46.
by OneDeuxTriSeiGo 3mo ago
It absolutely is. Mastodon has rate limits and administrators have to manage and adjust them as necessary for their instances. You probably just don't notice it as a user or as the operator of a small instance which to be fair is exact
47.
by OneDeuxTriSeiGo 3mo ago
It's not that they didn't warn bluesky specifically. It's that they didn't warn relay operators in general. And IIRC they just needed to coordinate with a single relay operator who is reasonably trusted (ex blacksky or e
48.
by OneDeuxTriSeiGo 3mo ago
Technically it has moved (last year actually) but it just doesn't really look all that different in the day to day. https://atproto.com/blog/plc-directory-org
49.
by OneDeuxTriSeiGo 3mo ago
The distinction really kinda depends on the situation. FDEs have been around for a long time in the defense contractor space and Palantir picked up the term, broadening the meaning a decent bit. Then it spread to the rest of the software&#x
50.
by OneDeuxTriSeiGo 3mo ago
Yeah definitely but tbh a one-off expense at that scale while unfortunate isn't really lethal. And tbh if you are performing ops at a scale where that level of expense is present it's nobody's fault but your own if your orche
51.
by OneDeuxTriSeiGo 3mo ago
That shouldn't be the case? When a negative leap second is applied it just means that 23:59:59 is skipped. The seconds go 56 57 58 0 1 2 3. vs a positive leap second where time goes 56 57 58 59 60 0 1 2 3. So if you are billed by time
52.
by OneDeuxTriSeiGo 3mo ago
This is also something where how you interact with the IRS really really depends on your initial interactions. If the IRS comes to you and says "your taxes are wrong you owe X amount" and you immediately turn around and prepare to
53.
by OneDeuxTriSeiGo 3mo ago
That's a leadership failure not a technical failure. If you can't dig your heels in and force time to tidy up technical debt then you need to find someone who can and let them take over as PM.
54.
by OneDeuxTriSeiGo 3mo ago
DKIM2 and DMARCbis are actually the opposite of this. They are long awaited fixes of brittle and often broken systems that are designed to now make providing secure email easier rather than harder. They both have fairly clean migration path
55.
by OneDeuxTriSeiGo 3mo ago
NGL I'd argue there's a certain appeal to "use AI to prototype a feature as fast as possible and focus your engineer hours on building a comprehensive testing and fuzzing plan" followed by a "remove and review every
56.
by OneDeuxTriSeiGo 3mo ago
Hot melt ink/solid ink has a laundry list of problems that complicate it. - A single ink clog can destroy a printhead. - partial clogs can result in ugly messes with ink smeared all over the pages and the assembly further smearing on l
57.
by OneDeuxTriSeiGo 3mo ago
It's incredibly childish of people on this site that within minutes of you posting people are trying to downvote you for saying "don't say slurs". NGL I can't imagine casually throwing slurs around having been accep
58.
by OneDeuxTriSeiGo 3mo ago
It's not literally IPFS but atproto/bluesky is using most of the bones of IPFS (IPLD) to do their entire data propagation and event broadcasting. And tbh it shouldn't be terribly difficult to extend the existing infra to supp
59.
by OneDeuxTriSeiGo 4mo ago
> The purpose of signing your emails or commits is to provide a good indicator that it actually came from you, not someone who managed to get access to your email account at the time. This is true and it's still true in the ATProto
60.
by OneDeuxTriSeiGo 4mo ago
Kind of. Your PDS can impersonate you but you can have higher ranked "recovery keys" that can undo/recover all the damage. Socially whether you can explain off that your PDS acted maliciously or that it was hacked or whatever

More ›