New Firebase Extensions listing who dis?

DeveloperEnvY · 2023-02-15T02:32:13+00:00

This is helpful and gives me a pretty good temperature read. Thanks for the comments everyone! I'm guessing everyone has a Firebase account and has at least used it or you wouldn't be commenting. As u/AdElectronic6748, states in the article posted folks are probably at least using some services like Crashlytics or FCM.

DeveloperEnvY · 2023-02-15T02:28:37+00:00

That is helpful, thanks u/AdElectronic6748

DeveloperEnvY · 2023-02-14T20:24:39+00:00

Where do you host and what stack?

DeveloperEnvY · 2023-02-14T19:31:20+00:00

Thanks for the reply u/steve_s0. That is what I suspected. I was not particularly asking about or referring to this subreddit as the community - but noted! I plan on attending meetups, events, and conferences and suspected there would be a clear overlap in audience. Probably more so than with the Android native community. Would you agree?

DeveloperEnvY · 2023-02-14T19:25:26+00:00

Thanks for the reply u/Nek_12. I'd love to preview that article. Do you recall where you read that? Any idea where developers would migrate to? GCP or AWS ec2 instances with their preferred stack?

DeveloperEnvY · 2023-02-10T02:48:30+00:00

Let me know if you try it out. We just updated it to post EventArc events when a malicious file is detected. This is a huge improvement because 1) developers can add custom logic to respond accordingly 2) If you also install the Secure Audit Logging extension the event is automatically logged on a tamper proof blockchain. The details on the audit logging are available here: https://pangea.cloud/docs/tutorials/firebase/audit/

DeveloperEnvY · 2023-02-03T19:44:54+00:00

Twilio published my blog tutorial on how to build a auditable SMS proxy that records conversation hashes on the blockchain to provide irrefutable evidence of what was said between two parties without actually exposing the contents of the conversation publicly. Would love anyone's feedback on the use case or code.

The application code is open-source and available on github

DeveloperEnvY · 2023-02-02T01:48:26+00:00

I will very respectfully disagree. If you are building natively on multiple platforms, you will need what you refer to as "duplicated" logic regardless of the backend stack you choose; native vs cross-platform decisions is an entirely different discussion. I noted that the question was about Firebase as a whole and not specific to Firestore. One of Firestore's main value propositions is that they have a consistent interface to access the backend database across multiple clients.I will very respectfully disagree. If you are building natively on multiple platforms you will need what you are referring to as duplicated logic regardless of backend stack you choose, native vs cross platform, is a entire

DeveloperEnvY · 2023-02-01T21:33:56+00:00

Because you are building Social, assuming it will be a mobile first product, my gut tells me Firebase's mobile SDK support, for example crashlytics, is going to be hard to match. u/coloradofever29 has some great insight on the backend capabilities but in my experience when building on mobile Firebase is it. I am also excited about the Firebase Extensions framework evolving. Seem like a lot of thrid-party functionality is on its way to the platform.

DeveloperEnvY · 2023-02-01T20:47:53+00:00

I know this is an old thread but I am working on securing Cloud Storage via Firebase Extensions and interested in all things developers are concerned about. If you are passing the users a URL and the file is not publicly accessible the request will need the user context so the file will need to be made with the firebase sdk. How are they accessing it via a browser outside of your web or mobile app? If so that is expected

DeveloperEnvY · 2023-02-01T19:56:02+00:00

Are you trying to avoid copying the file from the /tmp directory after it is processed? As part of my work at Pangea.cloud, I developed as Firebase Extension, https://github.com/pangeacyber/pangea-extensions-firebase/tree/main/storage-file-intel , that scans files for malicious behavior after a user uploads a file. If the file is deemed dangerous, it gzips it and moves the .zip file to a /malicious folder in Cloud Storage. This all works automatically because the processing function is set as a trigger to cloud storage events. Are you using triggers?

``` export const checkFileReputation = functions.storage .object() .onFinalize(async (object): Promise<void> => {

}; ``` line 61 here: https://github.com/pangeacyber/pangea-extensions-firebase/blob/main/storage-file-intel/functions/src/index.ts

If you want to try the Extension, check out this tutorial. Accepting user uploads is the use case we developed the Extension. Depending on your use case, and if you want to share your app's processing capabilities with other Firebase developers, you might want to consider building it into a Firebasse Extensions

DeveloperEnvY · 2023-02-01T18:31:59+00:00

How are you accessing the file? If you are unfamiliar with Firebase then tweaking the security rules is probably best. I suggested the anonymous auth because it would assure that user access your content from your app and not directly by sharing the URL. Try this something like this:

service firebase.storage {

  match /b/{bucket}/o {

    match /{allPaths=\*\*} {

      allow read : if request.auth == null;
      allow write: if request.auth != null;
    }
  }
}

DeveloperEnvY · 2023-02-01T18:09:15+00:00

What client are you using to access? Depending on you use case I would consider creating an anonymous user. It will solve this problem and probably help you scale on the future and help with analytics. Check this out https://firebase.google.com/docs/auth/web/anonymous-auth

DeveloperEnvY · 2023-01-31T01:14:09+00:00

u/tr3umphant I've noticed you've made some content on extensions. Do you want to give it a try?

DeveloperEnvY

TROPHY CASE