gepoch
Just have to remember that the year comes before the time zone but after the seconds :clown:
No idea where that came from. Probably the time format from the punchcard machine at bell labs.
If it was iso 8601 based, it would almost make sense.
01/02 03:04:05PM '06 -0700
So that's why it's in 2006, since you asked.
I think this is all totally fair. You are getting less laptop for the same price.
I will put a couple of nits here:
> * No dedicated GPU options, period.
It supports thunderbolt, so you can have an eGPU! That said, while eGPUs are pretty cool, they're expensive an inefficient.
> * Form factor is quite a bit more bulky than its competitors, even considering the fact parts are removable.
I would revise "quite a bit" down to "slightly." The Dell XPS is 15.28 mm thick. The Framework is 15.85mm thick. That's 0.57mm. It is on-par with the slimmer ultrabooks out there. I'm totally happy with the form factor.
* The magnetic bezel works great and I've had no problems with it at all. It's completely secure and you pretty much need to lever it off with your fingernail if you want to change it for a different color, or clean around the edge of your screen. The lid spring is slightly wobbly as others have reported, but not too bad.
* It does have thunderbolt and it works great. I've use mine with a Razer core x for gaming without issue. It also works with my Kensington dock.
Playing on easy modes is like walking. Once you build up some skill, playing on hard modes can feel like sprinting.
Additionally, Signal's encryption scheme gives their messages the "forward secrecy" property which means that acquiring key material at some point in the future does not allow you to decrypt any previous messages. Any encrypted messages that they could provide would be useless.
For more, check out their really interesting doc on the double ratchet algorithm that they use!:
https://en.wikipedia.org/wiki/Bullet_Cluster
Although that's a colliding pair of galaxy clusters. I'm not currently aware of any examples of this effect being observed for just two galaxies.
I searched for one of the unique tokens in the docs: https://www.google.com/search?q=0facda3319
That pulls up their SDK github repo: https://github.com/smartcar/node-sdk/blob/master/doc/readme....
Which is published with a standard MIT license: https://github.com/smartcar/node-sdk/blob/master/LICENSE.md
Which says (among other things): "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software."
Which may have significantly complicated their copyright claim if Otonomo includes the MIT license and attribution to smartcar.. At the same time, I can't find Otonomo's docs anywhere.
Something to think about when setting up your GitHub license!
So you could spray ammonia everywhere to promote growth, but it's not clear that you'll offset the carbon emissions from making so much ammonia in the first place.
[1] https://m.phys.org/news/2018-07-electrochemically-produced-a...
However, a few points to consider:
1. The signal server can't "see" the group. Clients are just sending N messages to everyone in the group with some encrypted metadata that says it's a group message.
2. The client app is open source. You can go look for a ghost user or backdoor mechanism yourself.
3. The build is reproduceable. You can build it yourself and sideload your own APK, or compare it to the APK coming from the play store.
I don't think it's impossible to put a backdoor in, but I think it at least makes vigilance a good defense. Smart serious people are paying attention.
https://kimonote.com/@mildbyte/travelling-murderer-problem-p...
Absolutely awesome.
Source: am a hipster.
If I tried to transcribe my notes from every meeting, I would end up working on it for more time than the actual meeting took at this point.
I have thought about the exact same app actually. Being able to photograph my Gregg outlines and get an English transcription would be the dream.
Gregg and many other shorthands are purely phonetic. There's no difference between to, too, and two. You would need to do OCR on the outlines, map those to sounds, and map the sounds to possible words, then assemble a meaningful sentence based on what meanings make sense in context. A neural net could probably do a good job of mapping from outlines to possible words, and you could use NLP tools to try to choose a sentence from the possible outputs. It would be tricky to do well, for sure.
For now, it's vim for my meeting notes :)
First of all, it's very fun (the main reason I got into it)
I currently can write about as fast as I type. Somewhere in the range of 40 - 80 WPM depending on how many complex words I need to use (those slow you down a lot more than common ones)
The biggest negative for me right now: reading. I can write it far faster than I can read it. For things like meeting notes,this pretty much rules shorthand out as I need to be able to flip through to find a particular meeting, or something important that someone said. This will get a lot easier with practice, but it's the biggest blocker for me at the moment.
I've made about 1000 flash cards in Anki for memorizing words, short forms, special rules, etc.
Very cool, but probably an obsolete technology in an era where recording is easy and typing is pretty good. I might feel differently as I improve, but that's how I feel now.
The problem is, they still end up needing some dark matter before they work very well. I think every bright person assumes dark matter must be fake when they hear about it, but nobody has succeeded in getting rid of it. Dark matter plus the physics we know about is actually a really great fit to what astronomers see, and it has been hard to improve on.
https://en.wikipedia.org/wiki/Tensor%E2%80%93vector%E2%80%93...
We tried git flow for awhile, but it didn't really meet our needs, so we got rid of it. Plus the whole thing feels a bit yak shavey to me.
The main practical concern was that we need to make long-lived releases of our components that we would need to support in the long term. Git flow (and, at the time, its opinionated tooling) just assumes you have the one master branch for making releases. We needed to maintain a few at a time. There have been some accommodations in tooling for this since then [1] so maybe it wouldn't be a problem any more.
From the yak shave perspective, I guess I was just unable to find much of value in this process over a much more ad-hoc approach where people work in branches, rebase from time to time, and then put in for a merge with their team when they're done. All of this to-ing and froing with the develop branch, feature branches, bug branches etc, leads to much more typing and work to do simple things, but doesn't really add a lot of value to the repo in terms of stability or readability or anything else, as far as I can tell.
In my view, git flow abstracts away git even more, and conceals the actual mechanics of branches, commits, and merges, doesn't add much value to the repo, and potentially does harm by detouring devs away from really learning the tools they actually need to understand to do work in industry at large.
Maybe this is something that makes sense at a larger scale? Not sure.
[1] https://github.com/petervanderdoes/gitflow-avh#creating-feat...