How sure are we that these jobs are fake?

We should consult with the assistant vice coordinator of human resources assistance.

I see that you're targeting website creation, but a react-native syntax output (https://facebook.github.io/react-native/docs/flexbox.html) would be nice for me. It's just slightly different (it seems, to me) than vanilla flexbox.

Interesting use case I hadn't thought of. I'm making it in React and then converting it all to standard HTML and CSS so it would be simple to do a standard `react` output instead.

One of the hospitals I rotate in has solved this by having you physically scan your nametag (just like unlocking any of the doors) to log in, log out, and whenever else your credentials are needed. It works pretty well, and no passwords to remember once it's set up.

So anyone with your badge (or a copy of it) can authenticate as you? Seems a bit dangerous to me. A second factor seems like it would be prudent.

lots of neat (and hopefully useful) things that can be added! i guess that's what OSS is for hehe.

-blink detection (using a webcam or forward facing camera?) to pause while your eyes are closed?

-hold-to-pause or hold-to-spritz button, and show context (+- a few lines) when not spritz-ing?

-point of focus slides slowly across the screen, to exercise those extraocular muscles

Thank you for open-sourcing this! At the moment I'm using sharelatex to keep a version of all my equations "alive" since every time someone tries to resave my word documents, the equations become rendered to images.

Unfortunately for me, Latex hasn't gained traction in our department. I think the main barriers to entry, for our lab at least, are:

1) Local installation is more difficult than installing Word. Sharelatex and other cloud-latex solutions solve this.

2) Word's comment and review tracking system is more intuitive. If you're reading a document electronically and want to insert a comment or make an edit in word, you just do it right there. With latex, you can use synclatex to go back and forth but this extra step is actually a non-insignificant barrier. Also, with latex, is there a way to make and see comments in the pdf/preview but have the comment also live somewhere in the source, AND have the comments be editable in both places? I suspect the answer is yes, but I just haven't found the right tool?

I haven't unlocked the "history" feature in sharelatex but does it come close to this?

> Word's comment and review tracking system is more intuitive.

This. The first person that makes a LaTeX comment and track changes system as intuitive as Word's can have all my money. No, the comment and todo LaTeX packages don't count. There's just too much resistance in getting someone to go through the LaTeX install process just to use packages in a syntax they don't want to take the time to learn.

Could version control get you part way there?

The issue really isn't me tracking my own changes. In that case, version control does great. The problem is adoption by collaborators, particularly for PIs that don't want to take the time to sit down and learn something new.

The problem with Word's track / review features isn't necessarily that they're good, it's that they're so entrenched in academic writing (even in the sciences), that attempting to do anything else gets zero traction from most PIs and collaborators. Even PIs that use LaTeX themselves are hesitant to collaborate using it because of the extra friction it introduces as compared to Word's track/review tools.

As much as I hate to admit it, I think the only way to migrate some collaborators away from Word and to LaTeX in a collaborative setting is to basically duplicate Word's track/review/comment features and incorporate them into a LaTeX-based system.

I meant to suggest that git could be used as the "backend" for a track/review system. I'm imagining being able to write standard LaTeX, but have your editor expose the git history in a way that looks like Word's track/review.

(I'm not familiar with LaTeX or the packages you mention, so maybe I'm reinventing a broken wheel here.)

Our history system isn't great at the moment. We made the classic mistake of building a feature that doesn't really work for a lot of people. However, we understand want people want a lot better now and we're working on something that is very inspired/copied from the change tracking in Word. It's a very popular request!

i think it is the first journal solely focused on BCI and it will likely become the journal of the (eventual) (official) BCI Society.

the there's no official BCI society yet, but the people who put on the meeting where this announcement was made http://bcimeeting.org/ are actively investigating becoming one.

then again, the same question can be asked, what makes their society the official society?

Very cool! I'm a n00b to the music-notation-app-world, but was able to get going pretty quickly. I'm not sure if any of these are already standard features on most music notation apps...but I think keyboard shortcuts to the note/rest types would help. Maybe even an option to eliminate some clicks (just press the key corresponding to the note/rest to place it underneath current cursor position)

Then again, being a n00b, maybe I don't realize that speed-of-input isn't the bottleneck for composers hehe.

Thanks for the feedback! Those keyboard shortcuts sound very helpful. I think, they're standard in some programs, too.

Does anyone know if the API can/will provide the raw EMG measurements? (I work in a lab that does this kind of recording with wired electrodes. A robust wireless interface that spits out the full bandwidth signal would be quite a useful research tool).

Anyway, even if it doesn't, I think this will still be awesome.

We're evaluating this - haven't announced either way yet. There are a few reason we wouldn't - namely power usage if we have to transmit that data over BT.

Will there be an optional wired connection or at least the ability to use MYO while charging?