b-jazz's Comments
Post | When | Comment |
---|---|---|
HTTPS All The Things (https_all_the_things) | Thanks @escada. I only thought about “website”, “:website”, “url”, and “:url”. I wasn’t aware of “image”. Looks like there are over 100,000 image tags. I’ll look into it and see if they are predominantly URLs. |
|
HTTPS All The Things (https_all_the_things) | I’ve found about 3000 instances of http://www.example.com redirecting to https://example.com in the lower 48. This makes me happy (because I abhor ‘www’). I’ll put a fix and run batches again as soon as I implement www.example.com to http://www.example.com as well. Great find @rorym. |
|
HTTPS All The Things (https_all_the_things) | Three excellent questions/suggestions. Thanks!
|
|
HTTPS All The Things (https_all_the_things) | As clear as mud. ;-)
My argument is that osmus.slack.com is a national-language forum for the U.S. with excellent representation. If that isn’t good enough for one reason or another, the wiki should call that out. |
|
HTTPS All The Things (https_all_the_things) | Thanks for the feedback @Nakaner. I’ll make sure I mention it in both the talk-us mailing list and the Slack channel in the future. Do you want to edit the AECoC page to point out that discussions shouldn’t take place solely on “proprietary communication channels”? Maybe we can prevent someone else from interpreting the page as I did in the future. |
|
HTTPS All The Things (https_all_the_things) | I agree that it would be pretty clear at that point that you can use HTTPS, but I think a simple HTTPS redirect is pretty convincing. Especially in this day and age when more and more websites are getting clued in about the importance of secure transmissions. |
|
HTTPS All The Things (https_all_the_things) | @Wynndale: Thanks for pointing that out. I’ll redact the names of the slack thread and post the rest of the content in the wiki so that people not on the US Slack server can see comments. I am currently only rewriting 301 (Moved Permanently) and 302 (Found). As you probably know, 302 has been known at times as Moved Temporarily. So it’s arguable that I shouldn’t be rewriting any of the 302 redirects, but IMO most website operators are using 302 when they really should be doing 301. It is the reason though that I’m avoiding touching anything that is much different from the original url. I’ve seen a bunch of domains redirecting to a facebook page or a google site temporarily. Those remain untouched. As for HSTS, I wasn’t familiar with that, but did a little reading. I’m not sure how you think that could be incorporated into what I’m doing. Can you explain? |
|
HTTPS All The Things (https_all_the_things) | @rorym: You can find the python code at https://gitlab.com/b-jazz/https_all_the_things/. It’s not meant for others to run just yet, but is there for review and comments. I’m currently just touching the “website” tag, but will likely add “url” and “contact:website” for the next go-around. I’m not sure I’ll do more than those as they make up the vast majority of http urls that are tagged. I’m happy to hear arguments on others that should really be included. When comparing the urls: I’m currently doing four checks. For http://example.com, I’m looking for https://example.com, https://example.com/, https://www.example.com, and https://www.example.com/. Those are the most common variations when specifying redirect urls. At this point, I’m not tackling protocol-less urls, but I certainly could. I should do some research and find out how common it is to leave off the http://. As for the U.S. vs. the entire planet, I’m open to running it on the rest of the world, but I just started with the U.S. as I know that community better than the rest of the world and only posted there looking for feedback. I could built up the script a little more and document how to run it and let others do their own countries. What I worry about most is getting buy-off from the larger community across the globe. If someone gives me the go ahead, I’ll happily run it world wide. |
|
The most surreal and memorable OSMF board meeting yet | Thanks Richard. I took it to mean, “you’re acting like a child complaining about this”. I appreciate the clarification. |
|
The most surreal and memorable OSMF board meeting yet | (Ugh. I should have previewed that comment before posting. And apparently I can’t remove it.)
I’d like to see something more substantive from OSM leaders like Richard and pnorman rather than dismissive ad hominem attacks. |
|
The most surreal and memorable OSMF board meeting yet |
|
|
Share your story: Open Gender Monologues | In this day and age, you can no longer make jokes like this. If SomeoneElse hasn’t figured that out yet, they will be in for a big surprise when they get caught on video making a microaggression and lose their job over it. SomeoneElse should be open to the fact that the man in the photo might have been seriously offended at the presenter making a joke about him when he (possibly) wasn’t doing anything wrong. Look at it from his perspective. |
|
Share your story: Open Gender Monologues | @Zverik is delusional if he thinks he speaks for “everybody here”. You lose a portion of the population when you advocate for unequal treatment and exclusion. Why not strive for truly level playing field and not alienating people. Do you think you’ll actually attract more people to your cause with statements like that? |
|
Share your story: Open Gender Monologues | I brought the following video to the attention of the SotM-US organizers: https://youtu.be/p1-EnjK14w8?t=3m3s They couldn’t have cared less about it and made it clear that they were biased towards sexism against men being acceptable. It was at that point that I stopped caring about diversity in OSM. You lost an ally in me. |
|
Sharp Turns onto Ramps | I have some scripts cobbled together to pull down different regions and process them individually and upload maps to github on roughly a weekly basis. The repo (mentioned above) is: https://github.com/b-jazz/sharp-turns-onto-ramps My count of worldwide nodes that were called out as of 2017-09-03 is 235,846. I was thinking of setting up regional map roulette challenges to see if we can get some movement on reducing that number. I’ve never messed with maproulette.org before, but it doesn’t seem too hard to do. Would that be a good idea? If anyone reading this has thoughts, I’m open to hear them. |
|
Sharp Turns onto Ramps | I believe that turns of 1-80 degrees, not 85, get called out. At least that’s what I see empirically looking at the results (it’s not my code, I’m just messing with turning the raw data into maps). And I agree with Hjart that the example map should be left alone and added to the exception list instead of twisting things around to make it not get triggered by this particular validation. That is likely an unintended consequence of the validation. If there is a physical triangular island or painted lines, I would do something like the above, but typically I leave these alone and add them to the exception list. |
|
Sharp Turns onto Ramps | Sorry, yes, I should have mentioned that the URLs aren’t active and clickable. I’m not sure if that is possible with the geojson rendering that github/leaflet/mapbox does. If someone knows the trick, please let me know. I gave up after a bit of searching, and like you noted, at least you can copy/paste the URL. I went ahead and changed the URLs to be “…/node/323277879” instead of “…/edit?node=323277879”. I prefer those as well. I’ve started a new github repo for the maps that I generate: https://github.com/b-jazz/sharp-turns-onto-ramps When you wrote your comment, the Denmark map was 23 hours hold, so I came back later to make sure I have the latest greatest. You’ll now see (if I remember) the date of the map in the github comment. I’ve also implemented a rudimentary “exceptions” file in that repo that can be updated with node IDs to ignore the next time I run my map generating script. Feel free to edit and submit a pull request. As always, let me know if you have any problems/questions. |
|
Sharp Turns onto Ramps | I’ve been playing around with osrm-extract on daniel-j-h’s sharp turns validation branch and parsing the input and making maps. I don’t have the compute horsepower to run the whole planet, so I’m looking at smaller countries in the meantime while I work on alternative ways to process chunks of the planet at a time. Here is an example map that I’ve generated of Denmark. I’ve kept the lines that daniel-j-h had and I’ve added a starting node marker (‘s’) so that you can see the direction through the node that is the problem. I’ve also included a URL to edit the problem node when you click on the marker so that you can easily start editing. (Note: the marker is for the first point, but the actual URL is to edit the second/middle point that has the sharp turn associated with it.) I spent far too many hours zooming in on one map and then zooming the editor/iD map trying to find the node in question. This should be a lot easier. https://gist.github.com/b-jazz/ec5003c0745270e9eb8994f6957107cf If you see problems with how I’ve generated the map, please leave a comment here or contact me directly. If you have some small (country-level) maps that you’d like me to process in the short term, let me know. |
|
Sharp Turns onto Ramps | Are there plans to update this on a regular basis. I try to poke around a clean up a few of the sharp turns when I have some time on my hands, but it is getting to the point where I run into ones that I’ve already updated, but they are still on the map. I’d love to see daily updates if it isn’t too difficult. I’m also curious at how things have changed with the map since you first started the project. There were ~30,000 at the start. I’m guessing the number has dropped since then (partly due to re-jiggering the methodology and partly due to people cleaning the data). But it would still be interesting to see how effective your project has been. |
|
Sharp Turns onto Ramps | This is fantastic. Thanks for the great analysis that will help serve to make OSM better and better. I’ve been cleaning up some of the ones in my area. It would be great if there were a way to tag false positives so they won’t continue to be tagged in the future. |