Kirill Gromov

A 500 error is very generic. It's like a "check engine" light on your car.  It does not say what the problem is just that something went wrong.
 
Check your server logs for the real error behind it. Without it, it's hard to say what the issue is and how you can resolve it.

I still think that a summary will rob the community of its character and voices. 
It’s still important to see the author next to their content IMO. 

It's not listed in the new Marketplace's site. You can find it directly on the developer's site: https://invisiondevs.com/files/file/2-robokassa-payment-gateway/

Read this topic: https://invisiondevs.com/topic/27-how-to-downloadpurchase-files/
 
However, ignore the first part about the deposit and look at the last line:
I guess @Kirill Gromov will update your group once he sees your reply(?).

Cool feature, but it seems to me that a large number of icons will interfere with the perception of content in the community.

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

We will miss you, marketplace 😢

There is already a replacement from Adriano: https://www.sosinvision.com.br/index.php?/file/290-videos-directory/ including converter

There is already a replacement from Adriano: https://www.sosinvision.com.br/index.php?/file/290-videos-directory/ including converter

There is already a replacement from Adriano: https://www.sosinvision.com.br/index.php?/file/290-videos-directory/ including converter

Address collection is a big part of payment gateways, so this functionality will continue to work.

Check out this useful tool: https://www.yourforumservices.com/index.php?/topic/31-scheduled-posts-system/

Will there be similar changes in Commerce and Page? User profile view?

To be clear, we have no plans to remove jQuery from 5.0.0. We expect to begin a fairly lengthy migration process over several releases where we'll start rewriting our UI and utility classes to use native.
That said, I do not think it is critical to remove jQuery to improve page speed scores. We can probably get away with using jQuery slim, which is about 23kb of data sent once, and then your browser caches it. 23kb isn't insignificant but then a single image added to a page will negate any savings. Removing jQuery now would add further stress onto third party developers and delay v5 by 6-9 months given the huge amount of JS we are using for really little gain.
Anything significantly new is using native.
Here's the result of running Lighthouse for mobiles on my development install running with IN_DEV on (so no caching, no compiled or minified CSS, hundreds of script tags, etc). I would expect that to hit high 90s when not using IN_DEV mode.

Waiting for a demo so we can try it out.