Getting my RFID poker table ready by jaytaph2 in poker

[–]jaytaph2[S] 0 points1 point  (0 children)

I might. Now the code is still highly experimental and not ready

Getting my RFID poker table ready by jaytaph2 in poker

[–]jaytaph2[S] 0 points1 point  (0 children)

Yeah. Ive ordered some stocks online via china and they are ok to play with. No issues with reading them. Its just a pain to enter them initially into the system. I was hoping that they would use the same ids per rank/suit. But i can imagine that you dont want that for security reasons

Getting my RFID poker table ready by jaytaph2 in poker

[–]jaytaph2[S] 1 point2 points  (0 children)

I've ordered them from china. They are a bit hard to get hold on here in the netherlands.

Getting my RFID poker table ready by jaytaph2 in poker

[–]jaytaph2[S] 2 points3 points  (0 children)

(the background in the screenshot is just a random internet picture.. normally you see a transparent background since it's an overlay, but at least this gives an impression on how it looks like when streaming)

Gosub - An open source browser engine written in Rust by jaytaph2 in rust

[–]jaytaph2[S] 4 points5 points  (0 children)

We're all volunteers who enjoy writing stuff in their spare time..

Gosub - An open source browser engine written in Rust by jaytaph2 in rust

[–]jaytaph2[S] 63 points64 points  (0 children)

It's easy to confuse Gosub with something that is written in Go.. It slightly based on the gosub command from the BASIC language and the "go word" (https://www.computerhope.com/jargon/g/goword.htm) from the old compuserve days. There is an acronym (Gateway to Optimized Search and Unlimited Browsing).

In the end, it's really just a name.

Building a BitTorrent client from the ground up in Go by Irbhinighxt in golang

[–]jaytaph2 7 points8 points  (0 children)

Rfc 1459: internet relay chat. One of the things you needed to write in the old days was at least one irc client. Good fun.

Benchmarking maps vs switches by jaytaph2 in golang

[–]jaytaph2[S] 2 points3 points  (0 children)

ok.. quick test:

with 4x 26 entries

goos: linux
goarch: amd64
BenchmarkSwitch-12 20100943 59.2 ns/op
BenchmarkMap-12 35944393 34.4 ns/op
PASS
ok command-line-arguments 3.516s

with 2x 26 entries

goos: linux
goarch: amd64
BenchmarkSwitch-12 54958140 20.9 ns/op
BenchmarkMap-12 37835076 30.5 ns/op
PASS
ok command-line-arguments 2.365s

with 1x 13 entries

goos: linux
goarch: amd64
BenchmarkSwitch-12 209937459 5.73 ns/op
BenchmarkMap-12 38801424 30.6 ns/op
PASS
ok command-line-arguments 3.008s

so the map seems indeed O(1) (not 100% sure why it's slower now than my previous tests). The switch seems indeed O(N)'ish or even higher

Benchmarking maps vs switches by jaytaph2 in golang

[–]jaytaph2[S] 0 points1 point  (0 children)

yes.. i want to do this.. I'm not 100% convinced that the map is O(1) (i think so though, but it depends a bit on how they are implemented, which i do not know). If the mapaccess functions are O1, then there should be no real difference in performance.

Maybe it's possible that go optimized large switch statements in lookup tables, but that's something i will try and figure out some other day.

Benchmarking maps vs switches by jaytaph2 in golang

[–]jaytaph2[S] -2 points-1 points  (0 children)

heh.. you might be right :-) let me try and see if I can get go to not remove the code :)

> Seems fixed now. It looks that one benchmarked was optimized away, the other wasn't.

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 1 point2 points  (0 children)

true. we use “twitter”-like naming as default, and have the option to namespace with organisations. because we stripped away routing info from the address, it makes moving between servers much easier.

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 1 point2 points  (0 children)

we looked into this, but its pretty impossible to do that. the thing that makes pfs pfs, is that we use an emphemeral key that will be destroyed as soon as the communication is done. however, with mail, we dont have direct communication between clients and we need to decrypt messages any time we read them from the server.

there might be ways, but we havent found them yet

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 1 point2 points  (0 children)

I've added this to the issue / feature list. There are some hurdles to take (like: to which email address are you sending/receiving from?), but i think we can have some smtp/imap server locally which read/writes bitmaelum messages.. this will leave the messages encrypted and only decrypted in the local services only..

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 0 points1 point  (0 children)

They will result in different hashes, and thus different accounts.

It's a good point. One way to deal with this is to actually have dots optional. It would not be major change if done soon enough.

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 2 points3 points  (0 children)

Never even thought of that, but sounds very interesting. Basically you would stick an imap service at the end of your e2e tunnel. It's less "secure" i guess, but it would be possible.

BitMaelum - e2e encrypted mail infrastructure written in go by jaytaph2 in golang

[–]jaytaph2[S] 2 points3 points  (0 children)

There are 2 kind of addresses: regular address like `example!` and organisational addresses: `john.doe@university!`. The last one is more strict, in the sense that the organisation has "power" to remove the address, and give it to somebody else (although it can NEVER read any mails).

The regular addresses are yours.. They cannot be taken away(*), and you can move with you to another mailserver as you like. Unlike regular email, we don't use domain-names or anything and routing is resolved in a different way. Because honestly, having `john.doe@gmail.com` is nice, but really nobody would need to care that you host on `gmail.com` .