At first I thought it was something about it being a worst case scenario for compression algorithms, costing bandwidth.
At first I thought it was something about it being a worst case scenario for compression algorithms, costing bandwidth.
I think bandwidth and data caps are a hindrance to this. Looking on the bright side, at least something would have to be better in this dystopian future.
Got this by using “force RTL layout direction for all locales” in Android developer options:
.bibisco2 are really just zip files which PhotoRec can find, if you want to use that. Good luck.
Bibisco2 is a JavaScript app, unlike version 1. It seems .bibisco2 files are only created when exported, otherwise it’s in a database somewhere. You can add custom formats in recovery tools like TestDisk and Photorec. I could look around and see if the database or the bibisco2 export files have a header, which I think is required to add a format.
Edit: Nevermind, there’s a paid version which creates bibisco2 files automatically.
That’s not a new way to change data, it’s reading it.
For legal issues that are not EU-specific you may also want to take inspiration from this instance.
Looks like it. Does this mean that what you wrote here will only be visible in the sh.itjust.works instance until lemmyml is online again, or is it more resilient than that?
I wonder how difficult it would be to add Lemmy support to existing Reddit apps.
I was able to enable it on stable by toggling browser.urlbar.showSearchTerms.featureGate
Edit: Nevermind, it doesn’t work for custom engines, which suggests that it’s a separate implementation from mobile?