# Change criteria for front-ends

**URL:** https://discuss.privacyguides.net/t/change-criteria-for-front-ends/20555
**Category:** Site Development
**Tags:** rejected
**Created:** 2024-09-02T13:07:56Z
**Posts:** 2

## Post 1 by @anon80779245 — 2024-09-02T13:07:56Z

Since we now align with OSI for open-source definition, Grayjay can’t currently be added.

I do basically believe we need to make sure that the new criteria

- Ensures public instances are trustworthy
- If it is a web-only instance, ensure anyone can run an instance
- Know that any front-end apps are transparent and that you know how they work
- Being able to build an app from source

With that in mind, the new criteria could be

> Web frontends should be open-source, while app-based frontends should be [source-available](https://en.m.wikipedia.org/wiki/Source-available_software) and have a license that allow for personal buidling and modification.

---

## Post 2 by @Niek-de-Wilde — 2024-09-02T13:19:16Z

That is still not decided, but it is the likely end result of the current discussion.

> <https://github.com/privacyguides/privacyguides.org/pull/2732>
>
> Relevant discussion:https://discuss.privacyguides.net/t/what-does-privacy-guides…-see-as-opensource/20230

the pr is still a draft, and our requirements are only official once they visible on the website.
