- Autoplaying video/audio is a PITA. If you use video or audio in Guri you'll see a play button. It seems iOS will eventually remove the restriction...

- CORS is a hard restriction for this tool. That's why I built the uploader into the editor. If you plan to do your own experience and can avoid it having your assets in the same domain on a CORS-enabled cdn please do

This being said, the A-frame community is the most welcoming I've ever seen

Kind of, I saw wordseye the first time after starting building guri (and I love it). I guess my nlp is much worse but in the other hand Guri has some capabilities built-in to the editor for searching resources. Also the AR-mode in Guri expands what you can do with it

Not yet :'( but you can import some pokemons from clara.io :P

Hi, GuriVR author here. Let me know if you have any questions :)

Just nitpicking: you use the Spanish flag to switch languages, but the grammatical person and verb conjugation you use are generally not currently used in Spain.

If the Mexican flag had been used instead, other people would have complained about that usage.

I'm argentinian and it's a challenge LOL Next design says the word "spanish"

Just wondering: if I ran two instances of your application, would I have "guríes" or "gurises"? :-)

I'd say gurises, since Guri comes from `kid` in uruguay

Lo' chiquiline'

What direction are you planning to take this project?

I see a lot of potential to create and edit virtual worlds on the fly using things like NLP, big data, proc-gen, computer vision, etc. then expanding that into mixed reality.

I'm currently working in the journalism world so taking a lot of feedback on how to tell compelling stories with the tool.

In the other hand I'm playing with other kind of input, such as speech recognition, for in-vr authoring.

is there a way to see what others have made?

Not yet but I plan to add it

Worst app ever. Please QA before launch (even it's a beta).

I'm using a library I made in node.js (https://github.com/danzajdband/Tuiter) to retrieve the tweets server-side via the Twitter Streaming API (https://dev.twitter.com/docs/streaming-apis). Then I send the "Twitter client" to the client using Socket.IO. I'm refreshing the chart, not the entire site, every 500 ms = 1/2 seconds to update the chart.

I'm updating every 500ms and not every time I receive a tweet because of performance issues.

Thanks for the feedback.

Very cool, I was unaware of the streaming API. Nice work!

It's not broken. Heroku free plan doesn't allow for websockets. The demo code on https://github.com/danzajdband/Tuiter/tree/master/examples/m... it's prepared to use webosockets first.

Ah, well that sucks but explains why it was occurring :)

Try again.

Natural is great for example for analyse a tweet stream... Is very useful for me.