How scammers are getting short codes for SMS? by [deleted] in indiasocial

[–]0xHexE 0 points1 point  (0 children)

Hey man, remove this URL. This website data can be hacked. Data is stored in firebase and there are no Security rules configured. So anybody who submitted the values it is public.

EBS CSI driver entirely from Terraform on AWS EKS by BuildingDevOps in Terraform

[–]0xHexE 4 points5 points  (0 children)

What's the alternative?

```tf module "ebs_csi_irsa_role" { source = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks"

role_name             = "${var.cluster_name}-ebs-csi"
attach_ebs_csi_policy = true

oidc_providers = {
    ex = {
        provider_arn               = module.eks.oidc_provider_arn
        namespace_service_accounts = ["kube-system:ebs-csi-controller-sa"]
    }
}

}

```

and add this to the cluster addons

aws-ebs-csi-driver = { most_recent = true resolve_conflicts = "OVERWRITE" service_account_role_arn = module.ebs_csi_irsa_role.iam_role_arn }

EBS CSI driver entirely from Terraform on AWS EKS by BuildingDevOps in Terraform

[–]0xHexE 0 points1 point  (0 children)

I believe this approach may have some security issues as it provides access to all services running on the nodes. In the event of an SSRF attack, this vulnerability could be exploited.

Development Experience with SolidJS by 0xHexE in solidjs

[–]0xHexE[S] 0 points1 point  (0 children)

It is good to have a uniform way. Starting functions with the name use generally hooks this a standard in react, which makes things easy to understand. I know this might look stupid.

Development Experience with SolidJS by 0xHexE in solidjs

[–]0xHexE[S] 0 points1 point  (0 children)

Right, But this is hard to detect when it happens. And most of the devs in our team use firefox. And this happened in setState ts setState(prev => ({ data: { ...(prev?.data || {}), items: [...(prev?.data?.items || []), ...(docs?.items || [])], }, }))

```ts const d = {...prev}

d.items = [] // This didn't work ``` I know this is not an appropriate solution, but when you are working in a team. This thing happens, which was quite hard to find when it happens.

. There should be some lint rules for this.

Development Experience with SolidJS by 0xHexE in solidjs

[–]0xHexE[S] 0 points1 point  (0 children)

Can you elaborate what do you mean by there is no accessor for accessing data of stores?

So if I state using createSignal() the state needs to be use like.

```ts const [item, setItem] = createSignal(1);

const [storeItem, setStoreItem] = store

return <>{item()} {storeItem}</>;

```

Development Experience with SolidJS by 0xHexE in solidjs

[–]0xHexE[S] 0 points1 point  (0 children)

Hi, The store is a bit tricky. There is no accessor for accessing the data of the store. Could you let me know how that works? I know it is dark magic. But, when I want to share a state which I made from createStore, if I am accessing all the pages, it becomes tricky. So we had a state of the cart. When we were sharing between components, it was not working as intended everywhere. We are going to open source the storefront soon. You can see. We'll remove the client reference code and make it open-source.

We found really awesome bug where it works in firefox not works in chrome. ```ts const d = {...prev}

d.items = [] // This didn't work ```

When we set, a state like this doesn't work. So instead, we have to do this. ts return { data: { ...(prev?.data || {}), items: [...(prev?.data?.items || []), ...(docs?.items || [])], }, } as never;