Mohammdd Alhalwachi

Software engineer building in public. Try ScoutlyAI, a platform to monitor competitors social media:

[Mohammdd Alhalwachi @malhalwachi2000]

Published ScoutlyAI 🥳🎉🎊
A platform for businesses to track and monitor their competitors and receive the insights they need!

Give it a try:
https://t.co/EspvO8dy31

[Mohammdd Alhalwachi @malhalwachi2000]

@housecor You still need to test your feature flags and phased releases procedures on a test environment. How do you know your feature flag even works?

[Mohammdd Alhalwachi @malhalwachi2000]

I would argue the opposite. Known frameworks help identify and patch vulnerabilities, unlike custom code. Hobby projects may not be targeted by hackers, but big businesses are, and custom code obscurity is ineffective.

[@levelsio @levelsio]

I'm gonna get annoying so don't block me but another reason I don't use frameworks or dependencies

It's hard to attack vanilla code

[Mohammdd Alhalwachi @malhalwachi2000]

@mahdi_tcs_ If I had to guess, some scripts or code depend on the opened file name. Returning multiple files for the same name would break them.

[Mohammdd Alhalwachi @malhalwachi2000]

@wiedymi @jarredsumner React is more of a templating engine that can be used anywhere. That’s a significant advantage. Without React, you’d have to build something similar for your project, maybe with a simpler feature set.

I’ve seen monstrosities that React would have been a better choice for.

[Mohammdd Alhalwachi @malhalwachi2000]

@__silent_ @theo @deadair3210 If it doesn’t compile wouldn’t that mean you haven’t tested if the changes even fix the issue?

[Mohammdd Alhalwachi @malhalwachi2000]

@thdxr Would love to see OpenCode integrated with Microsoft Copilot (not GitHub Copilot). Would be helpful for enterprises that only have access to that. It doesn’t seem to have limits either.

[Mohammdd Alhalwachi @malhalwachi2000]

I am building Runes: a graph-based personal task tracker.

Instead of lists, tasks are connected as a graph: showing dependencies, relationships, and how work evolves over time.

Built on @zero__ms for local-first and instant updates.

Would love feedback 🙌
Link is below.

[Mohammdd Alhalwachi @malhalwachi2000]

@jjmata @tebayoso @GithubProjects @maybe Thank you for keeping the project alive!

[Mohammdd Alhalwachi @malhalwachi2000]

@sashank_ps @SumitM_X If you’re fetching roles from the database, a simple session with cookies or an API token is the appropriate approach. JWT is designed to be self-sufficient, allowing it to authorize the user. You should resolve the role from the JWT. JWT has its applications.

[Mohammdd Alhalwachi @malhalwachi2000]

@cameronpetitti Veryyy cool video! Which software used?

[Mohammdd Alhalwachi @malhalwachi2000]

@mork1e @sorenblank Thats true. But usually users will refresh to check it was sent. If it is then they trust your software and appreciate how fast it is.

[Mohammdd Alhalwachi @malhalwachi2000]

@shadcn More content (either components or just docs) on the best practices for some UI components or UI in general.

For example, complex select inputs should have a search and a quick-add feature embedded with the ability to open a table for more complex selection.

And how to compose.

[Mohammdd Alhalwachi @malhalwachi2000]

@aboodman @dimaip @convex I switched from Convex to Zero for one reason, Convex didn’t sync locally first. It waited for data to come from the server. It did play well with my app paradigm.

But I like the instant feel of Zero.

[Mohammdd Alhalwachi @malhalwachi2000]

Banks relying on client side protection gives them false sense of security and makes it harder to work with (or around) it. Avoid if not required by regulations.

[Mohammdd Alhalwachi @malhalwachi2000]

HTTPs is sufficient. Adding your own layer doesn’t protect you from a malicious actor altering data in transit, it only makes it a bit harder. The only fail-proof approach is simply validating on the server and treat client side validation as a UX improvement. 1/

[Chizi @chiziaruhoma]

Client side encryption is great and recommend but always assume any client side code can be read in plain text by attackers, so your encryption algorithm can definitely be recreated if the attacker has your time, the only true solution to this is end to end encryption using both symmetric and asymmetric encryption (EEE)

[Mohammdd Alhalwachi @malhalwachi2000]

The only time where encryption and protection on the client makes sense is in multiplayer games, where you have to trust client validation as doing all the processing and validation on the server is prohibitively inefficient. /2

[Mohammdd Alhalwachi @malhalwachi2000]

@damengchen I am not convinced this provides enough security to justify the friction.

[Mohammdd Alhalwachi @malhalwachi2000]

@phonefuturist In this case, uniqueness provides no (or arguably less) value. Seems the consensus that the Apple design is the better approach.

[Mohammdd Alhalwachi @malhalwachi2000]

@SethGRosenberg Take a look at
https://t.co/idzAvPzJ7r

[Mohammdd Alhalwachi @malhalwachi2000]

@brankopetric00 Isn’t the premise of Lambda’s that it allocates granular resources on demand?

Why not just normal servers at this point?