search

steveseguin / social_stream

Consolidate your live social messaging streams and much more
http://socialstream.ninja/
GNU General Public License v3.0
516 stars 74 forks source link

Manifest Version Deprecation Warning #242

Open chrisspiegl opened 4 weeks ago

chrisspiegl commented 4 weeks ago

I just installed the extension in Arc Browser and got the warning that the current Manifest Version of Social Stream will be deprecated in 2024.

Xnapper-2024-06-06-09 01 10

I checked, and it appears there is no issue tracking this yet, so I thought to report it here.

There is also some CST warning, which may need taking care of?

Xnapper-2024-06-06-09 02 25
steveseguin commented 3 weeks ago

Thank you for tracking it. This has long been on my radar, as Google has been claiming it would be deprecated for a few years now. I'd say it's likely to actually happen by end of 2024 or early 2025 though. Firefox claims it will continue to support MV2, so it should still work in a limited fashion that way thru 2025.

The Social Stream Standalone app will not be impacted and opens up more options long term than an extension could. For example, it allows for direct websocket interfacing and no blue debug bar when responding to chat, but I can also decompress the interface/menu, providing more room for UI, settings, and customization options.

I've experimented with Manifest Version 3 and it limits things that makes what I'm doing in MV2 difficult. It intentionally tries to limit CPU usage, persistence, data collection, and hinders p2p data-channels, while also forcing me to rewrite large portions of complex logic.

While I have a prototype of what a MV3 version of Social Stream might look like, I've not commitment myself yet to it. If I get it working, it may require the user to have a management dashboard open as a tab, which would replace the background service that currently handles this all. The extension's service worker would be mainly for passing messages between this tab and the other tabs open.

I still feel I have plenty of time to navigate here, offering a solid solution one way or another, and when MV2 does actually lose support, the upside is I'll have more opportunity to work on improving the standalone app, the menu layout, and and configuration system.

chrisspiegl commented 3 weeks ago

Good to hear, and I agree with the sentiment that long term the stand-alone version is likely the way to move forward.

I also can see how the interface can be much more intuitive and spread out in that version to be easier to use.