"any-sync networks are permissionless. This means that anyone who knows the IP and port of the coordinator node can connect to it, create new spaces, or download existing encrypted objects. Data inside spaces is always secure, as it requires space encryption keys to read it."

From the docs on self-hosting. I am not a security expert, does anyone know if this is still considered safe? Feels weird that anyone can download my data, even if it is encrypted

Surely that’s just the nature of IPFS, right?

Not necessarily. You can add auth at the encrypted block level: https://peergos.org/posts/bats

I would argue that access and utilization of the internet is needed to participate in society. That is to say if we define "participate in society" beyond being alive and merely existing in close proximity to your neighbours, the internet is inescapable if you want to pay bills, stay up to date what is happening in your neighbourhood or have any chance of a decent living (e.g. a paying job).

This is why I built Yumee (https://yumee.recipes), a social recipe sharing app where you can only share recipes that you have yourself cooked (and you need to share a picture of your creation). Makes it very real and you can build your cookbook own cookbook mixed with recipes from your friends and family

Do you know of (or used) any guide to get started? I'm reasonably proficient but struggle to put all the moving pieces together

Well it was mostly pieced together information - the one that I already had from experience and the rest pulled from the Internet.

But which parts do you mean exactly? How to setup nginx to act as a reverse proxy? Or putting together a docker-compose? I'm thinking of doing some kind of guide for this type of thing on my blog - basically from setting up a Hetzner VPS box to running a docker-compose'd app and exposing it on a HTTPS endpoint for your own domain (so setting up DNS probably also).

I haven't read the book, but just hearing the idea to tape my mouth shut induces some anxiety. Isn't it dangerous that you don't get enough air?

You can actually cut a little slit in the mouth tape, so that you won't panic. Breathing a straw sized amount of air through the mouth if you need to, will prevent suffocation anxiety, but also limit your mouth breathing enough that your nose does most of the work.

Watch this guys two videos on a DIY CPAP. https://www.youtube.com/watch?v=g8JzXEoT9LI

I can see how it can cause some anxiety. I suppose I was lucky that it didn't for me. The first two nights I work up in the middle a couple times, decently alert, and could tell my body was trying to say something might be wrong. I was able to fall asleep quickly though, which also was something I wasn't able to do before.

If you might have that anxiety, I'd say try putting tape on your mouth during the day at times to get used to it, and you might find you'll forget about it and that can ease the worry. It might be difficult, but we all can breathe only through our noses, even if that requires some practice and reassurance.

It did cause some anxiety for me. But I use a soft tape that easily comes loose with just the back of my hand or a big jaw movement.

I especially enjoy how the nasal cycle with nose breathing just seems to physically “halve” colds. Even with a cold with nose breathing one nostril just opens up at night in order to let me breathe.

Trying to wrap my head around this as a React Native developer, my biggest issue right now is that we developed mobile first and now need to create a web app.

Using react-native-web is not as straight forward as it first sounds, as there a lot of packages that don't support web and just crash when trying to run the RN app on web.

Would this solve that problem, to be able to easily move a React Native mobile app to web?

It probably won’t help with native dependencies on the web. I’ve done a few projects that were android/iOS and then later on we added react-native-web support.

The best way is to go through your package.json dependencies one by one, figure out which support web and which don’t, then go into your project and make an empty component (eg: file.web.js) for any component that doesn’t work on the web. Once you have your app up and running on the web (even with a ton of “blank” web components), start the work of finding web equivalents for the missing functionality. Be diligent that the props for the native component and web component are the same or at least compatible, so that the component calling the now web compatible component needs no changes.

In my experience it’s super important to keep “platform specific” code isolated into its own component. General layout and the skeleton of your app should remain cross platform. In-line use of Platform.OS should be kept to a minimum.

Makes total sense, thanks a lot! I've been weighing the pros and cons from going RNW or just try a monorepo with Next.js and share logic and navigation (with new expo-router, when it gets to 1.0) but then rebuild the rest.

I like your suggestion though, a good start to see how much of a lift RNW would be or if it is just better to start "fresh" through Next.js

This is great advice. It’s very helpful to have a step-by-step procedure to follow for such a transition.

Not really, unless you redesign your app using Tamagui.

Your best bet is using React Native Web and removing dependency on the packages that don’t support web: remove/treeshake them, shim them (like RNW does with RN), or detect the platform using a conditional and then exclude the troublesome package/component in favor of a web compatible one.

Alternatively: Keep the web app separate from the native one, and simply share logic and some shared components (RNW) in a monorepo. Could be the easiest path forward, but will give some duplication of code.

My two cents, FWIW. Someone who has done the transition themselves, or has more insight to your particular case could probably offer even better advice.

Thanks a lot, super helpful to hear the ways to remove/treeshake, shim or conditional to handle mobile Vs web. This was something I struggled to find explained how to do properly, except create files with different extensions - but that felt a bit like using a sledgehammer when a smaller hammer would suffice (in some cases)

This looks really interesting, does this run on react native? Or is it only for web apps?

It seems to support Expo for push notifications (https://github.com/novuhq/novu/tree/main/providers/expo). I'm not sure if you could use it with "vanilla" RN.

You can use either Expo or Firebase Cloud Messages by the looks of it

I can see from the docs that what I read as in-app notifications, is actually the notification feed rather than mobile in-app notifications (to make it feature complete, similar to Onesignal). Looks really promising and will follow this as it develops!

For now we only support a react ,vue, angular and web component. So no react native component at the moment. But you can always consume the react library with the provided hooks and implement your own UI using the API.

Also if it's possible to run everything without uploading it to S3. For a smaller time dev with projects in production I would find this really interesting for debugging the production database data, but in development. Uploading it and having it in S3 would needlessly complicate it for me (even though I can understand enterprise customers might prefer it that way)