I've got ~ 70 git repos to move from AWS code commit to Gitlab and need to tweak config files in each one for the new hosting environment, so this should definitely help
Hey Mark! Same here up to now but Trooli are just starting to install cable in our area. Having looked at their service, T&Cs and reviews I'm going to wait and see as none inspire confidence, but seeing as Virgin missed out our area as "not commercially viable" and BT have no plans for FTTP then I doubt I'll have any other options.
I found https://bidb.uk/ tonight which is useful to see what's going on...
Thank you for this, I have been searching for something like bidb for months. We're moving soon and this is the exact data I need. Up until tonight I'd just been googling local providers and trying to find their maps.
I am curious if photoshop is better installed from the App Store instead of through creative cloud so all the extra apps aren’t added. Core sync drives me mad.
Out of curiosity, what would be the best way of displaying a rough distance for location on these style apps? (Round to nearest mile? Show a town name?)
One approach I've been thinking about in the past (at least as a rough concept) is for the back-end to round both users' location to an "area" (probably city level or similar), then compute the distance between the centroids of those areas. That way moving around your own city wouldn't change the returned distance, nor would the other person's moving around their own city. Even spoofing API requests wouldn't help much, as you'd only be able to triangulate which particular area centroid the distance is being measured to, and that is probably something the user is already disclosing on their profile anyway.
This could even be done in a relatively private way by only reporting the area level location to the server (not that I imagine many services would want to give up valuable raw location data!), as the server wouldn't need anything more granular.
Obviously there's challenges in more rural areas where population and premises density are lower - how big is the "area" in that case, and is the distance reported that meaningful in these situations?
The way tinder dealt with it, as I understand, is by dividing the world into a coarse grid. Users were placed in the grid, then distances calculated from the centers of the grid squares. Basically rounding of position, not rounding of distance. They tried rounding distance (calculated from exact positions) but one can exploit that by exploring for the boundary where the distance changes from one integer to another.
We’ve ran our own mattermost server for almost 5 years. Sits alongside our hosting environment and not had any outages, except maintenance. Some staff moan it’s a “poor mans slack” but it works well, keeps everything in our platform and virtually free.
