go-concise-encoding VS thgtoa

I'm not sure, TBH... Maybe I'm just a glutton for punishment?

I'm currently partway through refactoring all of the portable unit tests for Concise Encoding ( https://github.com/kstenerud/go-concise-encoding/tree/master... ) and it is a SLOG! I mean, so goddamn boring and tedious that I wanna stick an ice pick through my skull. There's easily another 200 hours of this terrible work ahead and I'll be right back to it the moment Dogma v1 is published in a few weeks (Dogma has been kind of a vacation from it in a lot of ways).

Do I dread it? Yes. Am I still going to do it? Yes. Because at the end of the day I want to be able to stand back and say "I made that. I completed it - ALL of it. It's not perfect, but it's doing its job and people are using it."

It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...

There are still a few things to do:

- Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.

- Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.

- Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.

I'm thinking that they should look more like:

    c1

I'll be working on the reference implementation [1] of Concise Encoding [2], which is a secure data format for the modern world. My aim is to replace insecure and clunky formats like JSON and XML and the various binary formats that do similar things less conveniently.

In a nutshell:

- Existing ad-hoc formats are too loosely defined to be secure, and that's becoming a huge problem as the bad guys become more sophisticated. CE is tightly specified and designed to mitigate exploitation of codecs.

- CE is a twin text and binary format. Humans view and edit in text, and machines send it in binary, so you get the convenience of text and the efficiency of binary for free.

- CE supports the fundamental types natively. Stringifying is buggy, causes incompatibilities, and opens security holes. And it's completely unnecessary with a properly designed data format.

[1] https://github.com/kstenerud/go-concise-encoding

[2] https://concise-encoding.org/

I'm building a general-purpose data format for the modern age. The old ones are too bulky, too insecure, and too limiting.

* Secure: As a tightly specified format, Concise Encoding doesn't suffer from the security problems that the more loosely defined formats do. Everything is done one way only, leaving less of an attack surface.

* Efficient: As a twin binary/text format, Concise Encoding retains the text-based ease-of-use of the old text formats, but is stored and transmitted in the simpler and smaller binary form, making it more secure, easier on the energy bill, and easier on the planet.

* Versatile: Supports all common types natively. 90% of users won't need any form of customization.

* Future-proof: As a versioned format, Concise Encoding can respond to a changing world without degenerating into deprecations and awkward encodings or painting itself into a corner.

* Plug and play: No extra compilation steps or special description formats or crazy boilerplate.

https://concise-encoding.org

Reference implementation (golang): https://github.com/kstenerud/go-concise-encoding

One thing golang did right is the go playground. When I put code in my README, I also include a playground link.

Example: https://github.com/kstenerud/go-concise-encoding#library-usa...

I could use some help if you're interested in implementing an ad-hoc data format codec in different languages.

https://concise-encoding.org is nearing release, but building the reference implementation (https://github.com/kstenerud/go-concise-encoding) has taken so much of my spare time that I couldn't even think about other languages (especially since I'll need to focus on the schema format next, and the proto-RPC protocol after that).

I've started doing this in my larger projects e.g. https://github.com/kstenerud/go-concise-encoding/blob/master...

An architecture document should be the code equivalent of a combined street map and tourist guide. Its purpose is to bring strangers up to a minimum level of familiarity with the code as quickly as possible. That includes where things are, why it was architected this way, things to look out for, and a few interesting points of weirdness perhaps.

Concise Encoding: https://concise-encoding.org

The friendly data format for human and machine. Think JSON, but with 1:1 compatible twin binary and text formats and rich type support.

* Edit text, transmit binary. Humans love text. Machines love binary. With Concise Encoding, conversion is 1:1 and seamless.

* Rich type support. Boolean, integer, float, string, bytes, time, URI, UUID, list, map, markup, metadata, etc.

* Plug and play. No schema needed. No special syntax files. No code generation. Just import and go.

I'm in the process of finishing up the reference implementation (https://github.com/kstenerud/go-concise-encoding), after which I'll start on the schema specification. Once that's done, I have a low-level communication protocol that will use this format under the hood.

Some of the anonymous advice here is pretty poor and recommends centralized services that require some level of identification.

If you actually need to be anonymous the daunting but doable tactics on https://anonymousplanet.org/ are a much better bet.

There is no single resource, but personally this is the most comprehensive I know of: https://anonymousplanet.org/

Anyways, maybe this site? https://anonymousplanet.org/

Said you shouldn't download Signal because it makes you stand out and attracts attention. Source: https://www.youtube.com/watch?v=IWMZ17Iyu3o Said that you shouldn't use ANY two factor because they're designed to track you, even software 2FA. Source: https://www.youtube.com/watch?v=ChKpf5HjcSY (He also says in this video that it's okay to let Google collect data about you as long as they don't tie it to a real world identity, even though the more data you give Google, the easier they can ID you.) Said that you should keep a "real identity" where you "pretend to be a sheep." Make Google searches for things you don't believe in, post tweets/statuses that you don't actually believe but perpetuate the prevailing narrative. AKA: look like you agree with the masses. Meanwhile, keep a second anonymous identity. (Source: https://www.youtube.com/watch?v=A8lHsIf6aA8) This is incredibly stupid. First, it doesn't work (source: https://lifehacker.com/generating-a-bunch-of-internet-noise-isnt-going-to-hi-1793898833), second you can easily burn an "anonymous" identity by accident and now it's linked to your real identity. True digital anonymity is almost (not 100%, but damn near) impossible. (Source: https://anonymousplanet.org/) His entire VPN video is just riddled with bullshit like saying that VPNs block email, block monetization, and that it's better to use a server in the US because of 4th Amendment Protections (worked so well in the past, right?) (Source: https://www.youtube.com/watch?v=OHfVPgLMMUQ). He then goes on to sell a "VPN router" in his shop that routes all your traffic over Tor - which means that your home internet may be slow, many common websites will probably block you, and as soon as you sign into anything you've lost all anonymity.

3) Said that you should keep a "real identity" where you "pretend to be a sheep." Make Google searches for things you don't believe in, post tweets/statuses that you don't actually believe but perpetuate the prevailing narrative. AKA: look like you agree with the masses. Meanwhile, keep a second anonymous identity. (Source: https://www.youtube.com/watch?v=A8lHsIf6aA8) This is incredibly stupid. First, it doesn't work (source: https://lifehacker.com/generating-a-bunch-of-internet-noise-isnt-going-to-hi-1793898833), second you can easily burn an "anonymous" identity by accident and now it's linked to your real identity. True digital anonymity is almost (not 100%, but damn near) impossible. (Source: https://anonymousplanet.org/)

Oh I thought bit launch was some bit exchange/management company or software, so I guess you see why I was telling you to isolated it to an incognito session+VPN. When you exit an incognito session it wipes all cookies, browser storage, etc for that session. However, I think you have to completely close the session, if you have more tabs open that data is probably still around until you completely close the browser. That's why if you use a second browser you're even more safe because you will think of it as a separate "thing" in your mind and be sure to manage it separately. Tor browser is a notch above that. If you don't resize it, you look like a million other tor-browser sessions (yes your browser reports it's "size" back to servers so they can figure out how to space things, and lots of times to finger print you). VPN gives you another layer in that it hides your IP (make sure to go to dnsleak.com and make sure you dns queries aren't leaking to your ISP's nameserver). This document is a bit paranoid, but I feel it has some good info and more than I am gonna type lol. https://anonymousplanet.org/ take from it what you need.

If you want to read more about censorship techniques employed by the Indian government (or any place) in general: Read 1 2

This is an interesting guide to become anonym: https://anonymousplanet.org/