jacksonsabey

Location: Vancouver, Canada

Remote: Yes

Willing to relocate: Possibly (within Canada)

Technologies: Golang, RethinkDB, SMTP, PHP, MySQL, PostgreSQL, MongoDB, Elasticsearch, Memcached, Redis, Ubuntu, FreeBSD, ZFS

Résumé/CV: on request

Email: [email protected]

Recent Work:

https://0ut.ca/documentation - Link Shortener, Tools, Parser/Validators, and API for +16 correct and complete RFC implementations for URI/IRI and Email components

Github: https://github.com/sabey https://github.com/sabey/ishtargate - contextual template engine for iptables/firewalls

I'm interested in continuing work with Golang, specifically on backend infrastructure. Web Services, Email, Storage, Security, and Distributed Systems are my main interests.

I have a similar problem with email spam, except at the bottom of every email there is a link to "disavow_contact" - the problem is it does nothing

The new AMD APUs don't have ECC support either, I'm hopeful the future versions will

this always happens anytime there's a sale on aliexpress, most of time it actually costs more when it's "on sale"

will I be able to build a laptop with ecc? if not buy a laptop with it, buy ram that will be supported

would 2 different torrents that contain a file with the same exact physical hash share the same torrent file hash?

if torrent A and B both contain the exact same file, but torrent A only has the first half available, and torrent B has the second half available, could I combine both torrents to download that file? this could help fix old dead torrents or at least make the file searchable elsewhere by it's sha256 for example

you just described usenet, requests or fills are usually done over irc

I have an implementation, although it's currently closed source and is only available via API: http://0ut.ca/documentation

I believe it's closest to the standard that I've found, and if it isn't I would like to correct that.

There is a Strict parser which will fail on any error, and Loose parser which will discard errors when possible and follow the defacto parsing implementations.

It should be able to handle any of the edge cases, such as partially percent encoded unicode, invalid characters, normalization, or octal/hex ipv4 addresses. The only thing from your linked unittests that it will not handle is | and \ for windows paths, they will be encoded.

You can easily compare the expected output in your browser here if anyone is interested in seeing how parsing is done: http://0ut.ca/api;v1.0/validate/uri/after?hTtPs://foo:%F0%9F... You can also try validating strange relative URIs: http://0ut.ca/api;v1.0/validate/uri/after?+invalid-scheme:/p...?

I would be happy to explain any of the reasoning behind the parsing if anyone is interested.

Location: Vancouver, Canada

Remote: Yes

Willing to relocate: Yes

Technologies: Golang, RethinkDB, PHP, MySQL, PostgreSQL, MongoDB, Elasticsearch, Memcached, Redis, Ubuntu, FreeBSD, ZFS

Résumé/CV: on request

Email: [email protected]

Recent Work:

https://0ut.ca

- Created my first MVP for a SAAS platform that's focused on Link Shortening and Link Tools

- Implemented Parsers and Validators following RFC guidelines for +16 different common components that make up a URI, including Email

Github: https://github.com/sabey

- the spoofgo repo is the latest/largest public project I've released as an example of my coding style

I love working with Go and it would be great to continue working with the technology that I am familiar with. However, I am open to learning new languages. The ability to learn on the job is important to me. I'm interested in Distributed Systems, Ad Networks, Security Tools, and Crypto Currencies.

I've recently released a beta platform and API for tools for working with links: https://0ut.ca/

There's currently a Link Shortener, UTM Campaign Builder, Parser and Validators for 15+ RFC implementations for different URI components.

I have a lot of continuing work to do, such as better analytics, a user system, and more tools.

I haven't got any feedback yet, I would love to hear just about anything, it would be encouraging. Feedback about my implementations would be greatly appreciated. Thanks!

Location: Vancouver, Canada

Remote: Yes

Willing to relocate: Maybe

Technologies: Golang, RethinkDB, PHP, MySQL, PostgreSQL, MongoDB, Elasticsearch, Memcached, Redis, Ubuntu, FreeBSD, ZFS

Résumé/CV: on request

Email: [email protected]

Recent Work:

https://0ut.ca

- Created my first MVP for a SAAS platform that's focused on Link Shortening and Link Tools

- Implemented Parsers and Validators following RFC guidelines for +16 different common components that make up a URI, including Email

Github: https://github.com/sabey

- the spoofgo repo is the latest/largest public project I've released as an example of my coding style

I've been programming since I was a child, I love it. I love working with Go and it would be great to continue working with the technology that I am familiar with. However, I am open to learning new languages. The ability to learn on the job is important to me. I'm interested in Distributed Systems, Ad Networks, Security Tools, and Crypto Currencies.

you could inform your users that email addresses are case sensitive much like passwords usually are or just normalize the local part along with the host and use that as the primary ID and have less issues in the future

servers that have case sensitive mailboxes are more likely to be used for throwaways or the user may control the server anyways so they could still respond to normalized local parts

as for verifying the email at registration you could check to see what the remote smtp server responds to when you issue the RCTP command to check if they consider the email valid

client side validation is pointless if you can't validate server side

http://www.w3schools.com/html/tryit.asp?filename=tryhtml_inp...

the firefox implementation will gladly accept the invalid [email protected] but won't accept the valid "test"@example.com

this is just a case of poor validation which we are now stuck with

Emojis are disallowed in IDNA2008. \u1F63B is in the disallowed but you can still register it on some TLDs https://whois.domaintools.com/xn--238h.com vs https://whois.domaintools.com/xn--238h.cf

  Gmail for example still allows me to email myself at \u1F63B.*.com or xn--238h.*.com

http://unicode.org/reports/tr46/#Table_Data_File_Fields

You can see the complete list of characters here:

ftp://ftp.unicode.org/%2F/Public/idna/8.0.0/IdnaMappingTable.txt

Hey, this is still in early beta. I've recently released an API for Validators of Email and different URI components. As for the shortener its self, there is no user system or analytics yet. Feedback is appreciated!

There's already a solution in the spec for the slash issue

Either you have a valid scheme or you don't, and either you have a relative path or an absolute path

Double slash after a valid scheme implies an authority, if a 3rd slash exists it's an absolute path, anything past the 3rd slash has to be normalized. So, http:////// is actually http:///

If you have an invalid scheme or a relative path such as http:/ or +http:// it would actually be normalized to ./http:/ ./+http:/

https://tools.ietf.org/html/rfc3986#section-4.2

there's also this https://en.wikipedia.org/wiki/MDY_Industries,_LLC_v._Blizzar... when they managed to get glider, one of the first bots taken down

> To fix the ambiguity, brackets were introduced

literals were introduced because the order of parsing for an email host is first "Domain" for any non literal, then literal which defaults to IPv4 [127.0.0.1], then a literal prefix was added for IPv6 and any future registered protocol "[IPv6:::]"

the order for parsing for a URI is:

// host = IP-literal / IPv4address / reg-name

// IP-literal = "[" ( IPv6address / IPvFuture ) "]"

ipv6 just happens to use a colon which conflicts with the port delimiter from authority in a URI so it's a literal and not a registered name

// [ userinfo "@" ] host [ ":" port ]

> why not re-use the dot from IPv4 notation

because you have conflicts from "0.0 -> 0.0.0.0" to "255.16777215 -> 255.255.255.255"

0-9 conflicts with an IPv4 decimal

a-f conflicts with GTLDs

the only reason your blobs don't have a conflict with an IPv4 Historic is because hexadecimal notation starts with 0x

> try double clicking on those

try double clicking on any of these valid characters from "reg-name"

// unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"

// sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "" / "+" / "," / ";" / "="

or these from IPvFuture

// IPvFuture = "v" 1HEXDIG "." 1( unreserved / sub-delims / ":" )

// unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"

// sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "" / "+" / "," / ";" / "="

if you want to develop your own "standard" either use the literal IPvFuture, or use a Registered Name

non literals IPv4, IPv4Historic, and Domain names are valid registered names, but domain names aren't even part of the URI standard

the only reason you would have conflicts with domain names is because they're de facto parsed after an IP, so a double dot would probably be discarded as invalid, which is why punycode exists for unicode

if at that point you didn't have any conflicts it would be a registered name, but you wouldn't have any way to resolve them

lastly, if you want to fix the nonissue of double clicking use a registered name, if you chose to use underscore you may have conflicts with dns

edit trying to figure out newline parsing