Until recently, the Morrowind Screenshots integration with VK worked like clockwork: posts were published quickly and with virtually no technical glitches. This was one of the most hassle-free integrations in the project—compared to other services where it is present, VK had a relatively straightforward API.
However, the company then suddenly decided to prohibit the use of the wall.post method for posting on walls via the API for almost everyone, except for a select group of large companies. And all they offered in return was RSS, which can be imported into a group at a specified frequency. Even setting aside the fact that this is not a replacement for a full-fledged API, this format works extremely poorly with images: the image in the post turns into a link to the website and is crudely cropped. It’s completely impossible to create a collection of images using this method. And I wouldn’t want every post in the community to look like just a link to the project’s website. In short, this format is completely unsuitable for a photo community, not to mention its other drawbacks.
I still can’t wrap my head around how you can prevent an author from publishing posts via the API in their own community.
А есть вариант обратиться в поддержку? Может, будут открывать доступ обратно точечно, по запросу?..
Ярослав, в поддержку обращался, доступ отказались открывать. Про RSS информация - как раз от них.
Антон, :((((
Пришлось забросить крупный музыкальный паблик примерно по аналогичной причине год назад. ВК буквально всем палки в колеса ставят.
Очень печально это. Но я, кажется, нашёл решение, которое пока работает. Напишу об этом позже.