Not quite sure if this is the best place to ask...but I need some advice on buying walkie talkies. I am one of the coordinators of our Good Ole Fashioned Hoedown at the stables in April. We want to get 4 units so that we can communicate easier. The longest distance is about a mile over hilly terrain and a few buildings.

We need something that is reasonably priced but reliable. Any tips?

---

Hey Liese,

What I'll probably do is create a project on GitLab with a generalized version of what I'm doing for this study. I still have a bit to work out before I can get there though.

---

SuziQ, I purchased a handful of these for work in the theater. They might get 1 mile line of sight. Not sure about through buildings. They are cheap Chinese knock-offs. The ear/mic pieces don't work so good. The connector on the ear/mic piece is a fraction of a size different than the connector on the radio, which causes lack of connection in the mic. So, if you don't need to use those, it's not a bad radio for cheap. [link]

---

Oh fun! Microsoft has started sending ads to the Win 10 lock screen. Details (and how to turn it the fuck off) here:

http://lifehacker.com/windows-10-is-showing-ads-on-your-lockscreen-heres-how-1760984834

---

Still not regretting my switch to Ubuntu.

---

No worries, Gud. I'm not anywhere close myself. I am at an event this week with my songwriting prof and bunch of writers, so I'm going to try to do some requirements gathering, though.

---

On my work browser (Firefox 44.0.2), while cruising the Amazon website, anytime I open a product (versus seeing search results), I get a script error that says:

Warning: Unresponsive Script
A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

It then gives a "script: [web address of product]

I click the "stop script" and "don't ask me again", but since each product is a different script, it always pops up. I wrote to Amazon, and their response was

I'd suggest clicking the "Help" link at the top of your window (above the browser commands) for browser-specific troubleshooting tips. If that doesn't solve the issue, you may need to contact your Internet service provider directly.

But the help menu had nothing about unresponsive scripts that I could find.

Is anyone else having this issue? Does anyone know a solution?

TIA.

---

Okay. The sample code for an Angular2 based web application with a PHP backend connected to MySQL is going to live here: https://gitlab.com/welarson/noter

I'm still just setting up the project. As I have time, I'll copy over and adapt code from my main project which resides in a private repo. First will come the backend, then will come the frontend.

---

Pushed some code to the PHP backend. You can see the basic structure of the REST API now even though most of it isn't implemented.

If you want to start playing with it, you'll need to take a few steps. In the noter/back directory you'll need to run:

composer install

That will download the PHP libraries you need. You'll also need to set up MySQL (or another database) with a schema and user and edit the 'propel.yml' file to those settings. Don't worry about creating tables or anything, that will be done for you.

Once 'propel.yml' is configured, then run the following commands in the noter/back directory to set up your database and generate the model classes.

vendor/bin/propel sql:build
vendor/bin/propel sql:insert
vendor/bin/propel model:build

Then you need to create the PHP configuration that the application loads in the bootstrap.php file. That is just another propel command.

vendor/bin/propel config:convert

You'll also need to make sure that Apache is configured to point to the noter/back/public directory and that the mcrypt PHP module is installed and enabled.

The Postman Chrome extension is really handy for test REST APIs. I'd recommend getting it.

I haven't run this code at all, so there are probably problems. I'll be adding more when I get a chance. Once I put in authentication, I'll make sure to run it to work out bugs and configuration issues.

---

Ooh! Exciting! Thanks, Gud. It'll probably be a week before I get to start to dig into it, but I'm super amped.

---