rojoroboto

7 ms·

1.
by rojoroboto 7mo ago
I bet that the author would really get a kick out of the T2 Tile Project.
2.
Demanufacture(dmnfctr.xyz)
3 points by rojoroboto 7mo ago|0 comments
3.
by rojoroboto 3y ago
The last time I used scuttlebutt was at chaos computer camp in 2019. It was neat and peculiar.
4.
SXSW 2024 Vote: Unconventional Tinkering: Learning, Building, & Sharing Joy(panelpicker.sxsw.com)
1 points by rojoroboto 3y ago|0 comments
5.
by rojoroboto 3y ago
He was forced there by our government. He was trying to get to Ecuador and wasn't given passage.
6.
How I DOSed This Newsletter(functionallyimperative.com)
1 points by rojoroboto 3y ago|0 comments
7.
Coin flips and most significant bits(funcimp.biz)
1 points by rojoroboto 3y ago|0 comments
8.
Coin flips and most significant bits(funcimp.biz)
2 points by rojoroboto 3y ago|0 comments
9.
by rojoroboto 5y ago
this is my favorite comment.
10.
by rojoroboto 5y ago
This article isn’t about reducing the cost of egress though, its about giving a discount when you peer with other partners. Its a very self serving argument.
11.
by rojoroboto 5y ago
This blog post is pretty disappointing. While true that AWS's egress can be costly, it is interesting that this article makes no mention of the fact that "non-partnership egress" on GCP is actually more expensive than AWS and
12.
cgi-bin, ftw (part 1)(youtube.com)
2 points by rojoroboto 5y ago|0 comments
13.
Startup Stock Options: How Did a Good Deal Go Bad?(writing.maxrosett.com)
4 points by rojoroboto 7y ago|0 comments
14.
by rojoroboto 7y ago
> So the number of messages you can send is precisely the number of keys that you generate at the start? How many is that? Bingo. The demo only generates 10K keys per participant, but 100k keys in storage takes less than 200ms to generat
15.
by rojoroboto 7y ago
oh. I love these questions. Handshake author here. Handshake provides a way for Alice and Bob to generate a large pool of one-time pre-shared keys as well as a set of one-time lookup hashes to go with these keys. Both the lookup hashes and
16.
by rojoroboto 7y ago
for the mobile app, the plan is to use QR codes + cameras, but its just byte blobs, so other transmission methods could be used.
17.
by rojoroboto 7y ago
The mobile app has some early proof-of-concept drawings and code, but that part hasn't been built yet. Right now its just core library in go with a simplified CLI interface and the ability for the code to compile to gomobile. The plan
18.
Puzzle Drawers(incoherency.co.uk)
86 points by rojoroboto 8y ago|9 comments
19.
by rojoroboto 8y ago
Thanks! We moved down here for the adventure of it, its been a rewarding experience for sure. Yep, I work part time for a couple of clients. Its a weird mix of data pipelining, systems architecture, orchestration, and site reliability work.
20.
by rojoroboto 8y ago
This is a fascinating question. I’ll have to think about that one and see if I can figure out the root of it.
21.
by rojoroboto 8y ago
yeah, the sleep difference is a big one, for sure. That one became a lot more evident in the recounting of the last year. I hope this post didn’t come off as prescriptive. That wasn’t my goal. It is meant to be about my path down not tracki
22.
by rojoroboto 8y ago
I’m fine. My daughter sleeps on her own through the night (sleep training. it works.) and wakes up around 7am. Almost always after we do. If this is, in fact, a few weeks before a mental breakdown, it would be quite a suprise. I’ll be sure
23.
by rojoroboto 8y ago
I've participated in career days before and it was a lot of fun. The big thing to remember is: keep things concrete. Use stories and visual aids with concrete examples. To really keep their attention, a presentation or interactive boot
24.
by rojoroboto 8y ago
This addresses the checkin aspect of killcord but it doesn't address the payload address broadcasting and decrytion key publication aspect of killcord. I am in the early stages of building a "providers" abstraction for killco
25.
by rojoroboto 8y ago
Right. The decryption keys aren't on the blockchain until they are "published". If all publishers are compromised or shut off before that happens, the killcord project has been terminated.
26.
by rojoroboto 8y ago
This is true. I'm working with a friend who is a copy writer to help make the landing page clearer and more helpful.
27.
by rojoroboto 8y ago
The purpose of killcord + ethereum for public disclosures is that leaning on ethereum as an API backend ties itself to the fact that taking down the entire ethereum network is difficult and running your own backend resiliently is hard. That
28.
by rojoroboto 8y ago
neat. Yeah, I picked symmetric encryption for the payload due to its relative simplicity, speed, and resiliency.
29.
by rojoroboto 8y ago
Yes. In the current form, If someone gets the project owner config file they could continue to check-in indefinitely. I've been toying with the idea of optionally encrypted the owner config with a passphrase to mitigate this. It would
30.
by rojoroboto 8y ago
This is left up to the killcord project owner to set the publisher threshold. If the project owner is concerned about congestion the owner should increase the time allotted to the threshold.

More ›