You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
RSS feeds seem to only work with threads, not microblogging. And if an user has only ever posted on the microblogging section, the RSS link results in a 404 error.
On which Mbin instance did you find the bug?
thebrainbin.org
Which Mbin version was running on the instance?
1.7.4
To Reproduce
Steps to reproduce the behavior:
Go to the user's profile page, e.g. https://thebrainbin.org/u/Auster (mine) or https://thebrainbin.org/u/@[email protected] (first user I found with only microblogging posts).
Find the RSS link, in the case of the instance I use, right above the text Powered by Mbin (see the image in Screenshots below). Also, the link will be the same no matter the tab you are.
Try to open/load/fetch the RSS link.
If the user has posted threads, only those appear in the feed generated, while if only microblog posts were made, it results in the aforementioned error 404. Expected behavior
As the RSS option appears for every user, and already works partially as observed previously, it could be presumed that it would work with the microblogging part, but as also tested, it appears not to. And as no information on RSS feeds could be found on the documentation, I couldn't be sure if it's a bug or intended behavior, though getting the 404 error might indicate a missing feature, or something to be added later? Now, if it is a bug, the report is made, and if it is either an intended or missing feature, perhaps RSS integration to the microblogging part could be added?
Screenshots
Desktop (please complete the following information):
OS: Linux Mint 21.3 x86_64, kernel 5.15.0-130-generic
Additional context
As I can't be sure if it's a bug or intended behavior, I wasn't sure if it was better to label this issue as a bug report or as a feature request, and so made a blank issue while using the most overarching of the two templates, the bug one.
The text was updated successfully, but these errors were encountered:
Honestly I just learned about the feature... It is something that we inherited from kbin, but never worked on or improved it in any way.
Imo an RSS feature should only work for local users / magazines. An RSS option should be available for a bunch of thing, including:
users
magazines
magazine modlog
instance modlog
As for the priority: imo we have a lot of things to work on and improve and I think of RSS as a very niche feature, so I would not prioritize it very high.
BUT adding microblogs to the way it currently works should not be that difficult
Describe the bug
RSS feeds seem to only work with threads, not microblogging. And if an user has only ever posted on the microblogging section, the RSS link results in a 404 error.
On which Mbin instance did you find the bug?
thebrainbin.org
Which Mbin version was running on the instance?
1.7.4
To Reproduce
Steps to reproduce the behavior:
https://thebrainbin.org/u/Auster
(mine) orhttps://thebrainbin.org/u/@[email protected]
(first user I found with only microblogging posts).Powered by Mbin
(see the image inScreenshots
below). Also, the link will be the same no matter the tab you are.Expected behavior
As the RSS option appears for every user, and already works partially as observed previously, it could be presumed that it would work with the microblogging part, but as also tested, it appears not to. And as no information on RSS feeds could be found on the documentation, I couldn't be sure if it's a bug or intended behavior, though getting the 404 error might indicate a missing feature, or something to be added later? Now, if it is a bug, the report is made, and if it is either an intended or missing feature, perhaps RSS integration to the microblogging part could be added?
Screenshots
Desktop (please complete the following information):
Additional context
As I can't be sure if it's a bug or intended behavior, I wasn't sure if it was better to label this issue as a bug report or as a feature request, and so made a blank issue while using the most overarching of the two templates, the bug one.
The text was updated successfully, but these errors were encountered: