arkshine
Forum Replies Created
-
It’s fixed in the latest Rehub version.
My bad, just noticed it’s not a block from Greenshift, but Rehub.
Actually, I think reported it already long time ago, should I report it again on rebub support page?
Forum: Plugins
In reply to: [WP Telegram Widget and Join Link] Weird telegram behaviorSorry for the late answer, I did not see the notification.
The answer is no. We had this plugin enabled for a while without issue and we did not change channel settings. It happened suddenly one day.
I came back because I wanted to share I implemented a basic caching system with Redis to save/get the output in send_request_to_t_dot_me for a few minutes, and it works well.
There are likely connection restrictions but I could not find any information about it.It would be handy to have a caching feature in the future.
For now, will mark this as resolved, thanks for the help.
Forum: Plugins
In reply to: [WP Telegram Widget and Join Link] Weird telegram behaviorAny news, please? It still happening.
It looks like it prevents spam and unnecessary loading: https://1drv.ms/u/s!AnfUx87FwDK4sFtJYuWZyOAvbvSg and implementing some cache mechanism might solve this. What do you think?
Forum: Plugins
In reply to: [WP Telegram Widget and Join Link] Weird telegram behaviorWhy this is marked as resolved? It’s not. *confused*Updated the status- This reply was modified 2 years, 3 months ago by arkshine.
Forum: Plugins
In reply to: [WP Telegram Widget and Join Link] Weird telegram behaviorI understand it’s an issue from Telegram. I’m wondering if it’s because the HTML is not fetched from an actual user? (maybe you might need to provide user-like headers?)
Refreshing is not helping. Sometimes the messages are back, but if you refresh again, most of time it reappears. You can see with the provided link.
Any solution in mind?
I’m actually a dev. Updating the plugin is not an issue and yes it works by removing path_duplicated.
I was looking for some plugin on behalf of a client to deal with webp and I found this plugin. If possible, I would want to avoid to modify a public plugin. That’s why I’m somehow insisting if an option could be considered.If still no, feel free to mark it as resolved and thanks anyway.
Well, considering you append a .webp to the path, it seems quite impossible it would happen.
Alright, is it still a no or are you going to consider an option for it?
I can do it myself, but I figured that other people might be interested about it.EDIT: I see “resolved”, I guess it’s a no.
- This reply was modified 4 years, 9 months ago by arkshine.
I understand but this why i’m saying as ‘option’. It can be a disabled option (even advanced option) and can come with warning message about it as well. Whoever activates it takes responsibility, it’s fair.
Actually, what risks are we talking about exactly?