-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Instagram] Stories not listed #694
Comments
The media_type parameter was recently replaced by media_type_u (for user mode) and media_type_h (for hashtag mode). This was necessary in order to add the media type 'story' only for the user mode. "The reason for that is that RSS-Bridge supports multiple parameters with the same name if and only if they contain the exact same value. Here, hashtags don't have stories, so it would not be possible to pass "story" as a parameter. This is a design mistake that I made when I added support for hashtags." -- 8770c87?diff=split#r28871502 However as pointed out this change breaks existing feeds as the parameter name is no longer compatible to previous implementations. This commit changes the implementation to provide the old media_type parameter globally and check for invalid options on each request. If a user uses the 'story' option in history mode the bridge returns a client error. references 8770c87 references #694 fixes #696 fixes #699 fixes #701
Does changing the media type from |
I pulled the latest commit and used the previous parameters. The stories are still not showing up.
|
That's strange, I see the stories on my machine. Based on your query this is the first story currently in the feed (second entry right now): https://www.instagram.com/p/BjRpeS0nQu7/ Do you receive any results when changing the media type to |
I tried that as well. Same thing. Just for clarification, am I right to assume that I only see the |
The source code refers to three different types rss-bridge/bridges/InstagramBridge.php Lines 57 to 69 in 064ba45
I actually downloaded the contents manually to see if the bridge works correctly and it looks perfectly fine to me. There are, however, multiple Maybe the bridge is still missing the correct field? Than again I don't see any story icon right now, do you need to be logged in for this? In that case you are out of luck. |
IG stories can be accessed by clicking the user profile pic. And yes you need to login if you click there. They have expiration on them (24 hours I think). The link for the stories will still be alive but they are not available in the interface. I thought IG stories are supported because of this: 8770c87 These story links are available without logging in. I just don't know how they are extracted. |
This is what I thought as well, but it seems that your story and the stories captured by the bridge are different types of stories.
Since they don't seem to be linked directly, I did a comparison of two profiles, one with story and the other without. The particular area around the profile picture is pretty much the same in both cases. The only difference is the class It's worth mentioning that IG heavily depends on JavaScript for page rendering. The raw HTML (about 250 lines) pretty much consists of one large JSON object and a few HTML tags (primarily meta data). Unless someone has an idea how to proceed from here there is no way to extract your story links. That being said, maybe this is different when being logged in. Maybe you can have a look and see if you can find anything (I don't have an account). Right now there is nothing we can do to support stories unfortunately 🤷♂️ |
Fix following issues which related to output of the GraphSidecar type posts. - The GraphSidecar post's media wasn't outputted except for first picture when searching by hashtag or location - Video didn't embedded NOTE: The function getInstagramStory() which was called when the post type is GraphSidecar didn't seem to work just as one intended. Because the web request called in that function is just to get the media of single post, NOT to get the media of Story. But I don't have any idea to solve RSS-Bridge#694, so it seems be better to rename these function and member variable properly.
…ng (#1361) * [InstagramBridge] Fix GraphSidecar output Fix following issues which related to output of the GraphSidecar type posts. - The GraphSidecar post's media wasn't outputted except for first picture when searching by hashtag or location - Video didn't embedded NOTE: The function getInstagramStory() which was called when the post type is GraphSidecar didn't seem to work just as one intended. Because the web request called in that function is just to get the media of single post, NOT to get the media of Story. But I don't have any idea to solve #694, so it seems be better to rename these function and member variable properly.
The media_type parameter was recently replaced by media_type_u (for user mode) and media_type_h (for hashtag mode). This was necessary in order to add the media type 'story' only for the user mode. "The reason for that is that RSS-Bridge supports multiple parameters with the same name if and only if they contain the exact same value. Here, hashtags don't have stories, so it would not be possible to pass "story" as a parameter. This is a design mistake that I made when I added support for hashtags." -- RSS-Bridge@b92405f?diff=split#r28871502 However as pointed out this change breaks existing feeds as the parameter name is no longer compatible to previous implementations. This commit changes the implementation to provide the old media_type parameter globally and check for invalid options on each request. If a user uses the 'story' option in history mode the bridge returns a client error. references b92405f references RSS-Bridge#694 fixes RSS-Bridge#696 fixes RSS-Bridge#699 fixes RSS-Bridge#701
…ng (RSS-Bridge#1361) * [InstagramBridge] Fix GraphSidecar output Fix following issues which related to output of the GraphSidecar type posts. - The GraphSidecar post's media wasn't outputted except for first picture when searching by hashtag or location - Video didn't embedded NOTE: The function getInstagramStory() which was called when the post type is GraphSidecar didn't seem to work just as one intended. Because the web request called in that function is just to get the media of single post, NOT to get the media of Story. But I don't have any idea to solve RSS-Bridge#694, so it seems be better to rename these function and member variable properly.
@rEnr3n Is this still an issue? |
@rEnr3n ? |
Issue is still here. Just a rehash, I can't view the stories as a guest on a browser. dev.2023-07-11 (git.master.0780917) |
I updated my url to the new parameter. I'm just getting the normal posts not stories.
?action=display&bridge=Instagram&u=jessica.syj&media_type_u=all&format=Atom
The text was updated successfully, but these errors were encountered: