
amateur bird photographer | tech sometimes | mid-30s
I've said this before but something interesting/funny/infuriating about Photo is that it takes almost nothing to get into (nearly everyone has some kind of camera and can be creative) but as soon as you get to a point where you want your gear to do something very specific it becomes so stupid because there's such a wide range of possibilities and ways to do anything, and ultimately there are a lot of tiny things that are annoying but don't matter but are still annoying? Anyway case in point behold my Contraption
I have been using this for a while and it works but there's one little, tiny part which Is Very Annoying which I have been hoping to improve literally since I put these objects together for the first time. Can u guess which part
Good Job! It's the tiny ebay rando brand EF mount to K mount adapter.
Technically it works fine, but:
TLDR: I have to like stab my finger every time I want to
So Anyway I thought I had finally found the solution because I found (and I need to stress this part) ONE un-labeled zero-branding or description adapter for Canon EF to Pentax K which was designed to be slightly too thick in order to have a normal lens lock lever on EBay...
...But I finally got it today and it turns out the actual mount part of the adapter is designed slightly wrong so it doesn't actually work fslkjdg
So yeah this is what photo as a hobby gets like sometimes. Look out
* [note: I don't have this problem w newer Rokinon lenses for x mount.]
Here's the error message I got when trying to DM.
The Twitter developer page says this about that error message (as error code 37 is something else, apparently):
Code 220
Your credentials do not allow access to this resource.
Corresponds with HTTP 403. The authentication token in use is restricted and cannot access the requested resource.
So yes, API keys were indeed restricted lmao
(Error code 37 seems to mean "Not authorized to use this endpoint" according to the Twitter Community forums, which is an inaccessible webpage which is conveniently cached in google search results though. More confirmation that it's API issues though!)