It has been a pleasure for me to contribute to all of you 2 versions of this tool.

I've been working on other open source projects that I'm about to release for you, so I haven't finished trape version 3.0.

But, I invite you and the entire community that has used this project, to collaborate with some lines of code, implementing your own ideas and improving trape, turning it into a project o

Thank you for your sharing. And I wonder if there is the search region update strategy in this project. I try to change the instance size and output size to enlarge the search, while it seems that the result will become even worser. It seems that a large search region imply the target becoming smaller? What is the corret implement of the strategy? Please correct me if I am wrong.Waiting for your r

I have found that @activity.trackable does not work when there is a default_scope which excludes the tracked object. I found a working monkey patch (see below), though is there a more appropriate solution? Would it be possible to override this default_scope when it's present?

PublicActivity::Activity.class_eval do
  def trackable
    trackable_type.constantize.unscoped.find trackabl

I don't want to generally enable the tracker but need activate it by middleware or command.

The "use_middleware" seems not to be implemented.

How to start it?
use Tracker;
Tracker::currentSession();

Doesn't work!!

It only works with 'enabled' => true, in the config for each request.

Privacy Badger has still a project on Transifex, even though it's not mentioned anymore in the translation guide. So I wonder if it's going away at some point?

If there is still interest in providing an environment similar to Transifex, I would recommend Weblate, which has the following advantages:

• It's free and open source, can be self-hosted.
• It's easier to use

Hey there! Asking here as I couldn't answer this from the docs: is there a way we can run Toodles on a project (Node.js in this case), and generate a bunch of HTML/CSS/JS files that we can host along with other static reports we generate on every PR?

The descriptions to many of the links to the products and services are quite generic. It would be quite useful if some of them could be rewritten by people that have actually used the products.

This would allow visitors to get a clearer picture of what differentiates the products and services.

I've been meaning to provide this as importable within react-tracking via something like: import track, { mockTrackEvent, TrackingPropType } from 'react-tracking/mock'; but haven't had a chance yet. PRs welcome! 😁

/* __mocks__/react-tracking.js */

const PropTypes = require('prop-types');

const mockTrackEvent = jest.fn();

module.exports.TrackingPropType = PropTypes.shape();

The README mentions the following:

Also edit /etc/network/interfaces and remove the wpa-conf line for wlan1.

However, on a default Raspbian Lite install (September 2017), my /etc/network/interfaces contains:

# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man d

Hello,
Do you know about Conan?
Conan is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers.

Here you can find example, how you can create package for the library.

If you have any questions, j

There is a good article about subject: https://developers.facebook.com/docs/facebook-pixel/events-advanced-use-cases/v2.11

It is fairly easy to extend this gem to use pixel with simple events, but what to do with more complex ones, like key stokes or firing pixel on page scroll? Any ideas?

Currently the matching fails if too distant GPS/GPX entries but instead we should create two routes and make it happen.