Mist Reviews

Parse-Server Reviews

Mist mentions (1)

• Ask HN: Does the Ethereum foundation not develop a post-Merge client?

  I'd expect them to provide at least one full set of usable software from it, not just specifications on how to write the software - which is what they seem to only be producing now? They already cancelled their GUI wallet some years ago (https://github.com/ethereum/mist) which was kind of weird already considering that people did have money in it already. But you could at least resort to using geth as a terminal... - Source: Hacker News / almost 2 years ago

Parse-Server mentions (5)

• What to choose for backend

  If you like headless CMS / Backend As A Service you should consider https://directus.io/ or https://github.com/parse-community/parse-server. Both nodejs and open source. Source: about 2 years ago

• Any general purpose visualisation "just add the data" framework

  There's numerous standard backends which frontenders could use in simplistic cases to start, say https://github.com/PostgREST/postgrest or https://github.com/parse-community/parse-server. Source: over 2 years ago

• Show HN: Caffeine, minimum viable back end for prototyping

  Parse is still around and supported: https://github.com/parse-community/parse-server. - Source: Hacker News / over 2 years ago

• Ask HN: What Back End Framework with User Management Is Your Favorite?

  I am curious what backend framework you would choose to run with for prototyping an application with run of the mill user management requirements. That is functionality along the lines of: session management, password policies, password reset, user verifications, etc. Sadly it seems there really aren't any frameworks that have user management natively supported. The only one I am aware of is [Parse... - Source: Hacker News / almost 3 years ago

• [Open Source] I made my first app. Its a fully functional social media app. And I decided to open source it.

  I believe you are referring to main.js file. The answer is no. I used parse server for backend. And by default all classes are public which means everyone can read every data. There is a preferred way to prevent this. You disable all class level permissions for every class. Then you put your app logic to cloud code which is main.js file you were looking at. Here is an article about this... Source: about 3 years ago