Skip to main content

Seeing something I haven't seen before, building something that never existed before.

Collecting new skills and experiences like precious shinies.

Technology Strategist & @elgg expert, occasional @withknown contributor, Hacker, Wanderer.

Have laptop, will travel.

www.marcus-povey.co.uk

www.linkedin.com/in/mapkyca

www.twitter.com/mapkyca/

www.flickr.com/photos/mapkyca/

github.com/mapkyca

plus.google.com/+MarcusPovey

www.instagram.com/marcuspovey/

angel.co/mapkyca

www.redbubble.com/people/mapkyca/portfolio

Replied to a post on github.com :

I think this might be a separate issue, and doesn't appear to be down to the new output filtering. Will investigate a bit further when I get a chance.

Meanwhile, putting a youtube link in your post should still expand out into a youtube video.

Anyone know of any IT recruitment agencies specialising (or at least handling) international recruitment? Full time or contract.

@kevinmarks I think this might be something for @benwerd - I think this would need something special done with the hosting for that domain.

@kevinmarks Ahh, so is the problem that there's no https on that domain?

@kevinmarks @jgmac1106 Well, http://*.withknown.com are rewritten to https with a 307. What's the error, is it not following the redirect or is there some token being generated specifically over the http:// url...?

@jgmac1106 @kevinmarks What are you trying to accomplish? Changing htaccess for an individual *.withknown.com I don't think is possible. Export is possible but is a manual export of the database... possibly worth bouncing this off @benwerd

Replied to a post on github.com :

I agree. Personally, I'd like to move api over to OAuth2.0, although this may require a bit of discussion. The current API has a number of issues which OAuth2 would go a long way to solving.

Actually wrote a Known plugin that does this some time back, so it may be worth adopting that and cleaning off the bitrot.

@benwerd, what are your thoughts?

Replied to a post on github.com :

The obvious way would be to somehow get a token from a username/password, which might be to use a form/token post on the login and retrieve a token. This proves difficult, owing to the session id portion in the token generation.

I'm thinking OAuth is probably the way to go

Replied to a post on github.com :

Simple solution would be to limit the amount of data retrieved to a few tens of k, but I'm not sure that's currently possible at the moment

Replied to a post on github.com :

Yeah, it'll either be the webmention ping (which I think pulls the full url), or the link unfurling (which I think may do the same, but I can't remember if I was more clever with it)