Main name of the project: #!os vs. HashbangOS -> HashbangMobile and #!mobile

[ypid]

I am starting to update the docs and adding my workflow. @lrvick you call the project #!os which is a creative name that all Unix people will understand.

One issue I thought exists is that #!os is tricky to search. I have some background with Elasticsearch and by default, you will have a hard time to search for #!os in a text field. I just tried it with Google and duckduckgo.com. Google actually found this GitHub repo with "!#os but not consistently depending on the personalized search.

I think when we stick to some norm, the project will be easier for people to approach. In the AOSP based hardening community, the space before "OS" is often omitted (1) so "HashbangOS" would be the natural option. !#os can still be used as an internal code name. Also the Wallpaper is still nice https://github.com/hashbang/os/blob/master/branding/wallpaper.png with references to the code name.

@lrvick What do you think?

[lrvick]

I have another project in mind I may work on in the next year or so that is more generic in nature to run on either mobile or desktop which the name hashbangos might be more suited for. HashbangAOSP (can still be stylized in logos as #!aosp) may make more sense here to fully disambiguate if we are changing things up anyway.

…

On Sat, Feb 6, 2021 at 2:06 AM Robin Schneider ***@***.***> wrote: I am starting to update the docs and adding my workflow. @lrvick <https://github.com/lrvick> you call the project #!os which is a creative name that all Unix people will understand. One issue I thought exists is that #!os is tricky to search. I have some background with Elasticsearch and by default, you will have a hard time to search for #!os in a text field. I just tried it with Google and duckduckgo.com. Google actually found this GitHub repo with "!#os but not consistently depending on the personalized search. I think when we stick to some norm, the project will be easier for people to approach. In the AOSP based hardening community, the space before "OS" is often omitted (1 <https://github.com/AOSPAlliance/README>) so "HashbangOS" would be the natural option. @lrvick <https://github.com/lrvick> What do you think? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQ4UENUGBSRRCAAQXSOY3S5UIA3ANCNFSM4XGD2ZMQ> .

[ypid]

HashbangAOSP does not really describe it anymore as I based it on GrapheneOS, see #47 which will be contained in #40 as I see GrapheneOS as a sensible base for this project.

I could go with HashbangROM. I think OS would describe it better but ROM is not wrong as I once thought considering that the Android system image is read only. No, lets not go there. ROM is defined differently.

Lets do the "usual" in the AOSP based hardening community, come up with a snake or a material. Or how about ResistantOS or MultisigOS to hint to the project goal.

PS: Are you still interested in this project than or would your more generic OS also replace this project?

[lrvick]

The future project I want to do would be a similar separation of concerns architecture of QubesOS, but based on user choice of kvm or containers, and small enough to run on mobile, desktop, or servers. I have done some work along these lines recently that has convinced me there is a reasonably short path here. It would not be android compatible, or capable of using binary blobs so most android hardware today is out. This is a longer term play. The android ecosystem is not going anywhere any time soon so work needs to continue to provide a best effort android compatible solution for many years to come, and the hardware #!os targets won't overlap with any devices this project supports. In this instance I kind of want to reserve "os" for the project that runs on many platforms (Initially pinephone, librem5, cloud servers) and have this project named something more consistent with its limited scope of android/mobile but still under the hashbang namespace. HashbangMoble (#!mobile) HashbangPhone (#!phone) HashbangAOSP (#!aosp) HashbangDroid (#!droid) Are my top picks atm in no particular order. I too considered "ROM" but that feels as overloaded as OS to me for something scoped just to mobile.

…

On Sat, Feb 6, 2021 at 7:15 AM Robin Schneider ***@***.***> wrote: HashbangAOSP does not really describe it anymore as I based it on GrapheneOS, see #47 <#47> which will be contained in #40 <#40> as I see GrapheneOS as a sensible base for this project. I could go with HashbangROM. I think OS would describe it better but ROM is not wrong as I once thought considering that the Android system image is read only. No, lets not go there. ROM is defined differently. Lets do the "usual" in the AOSP based hardening community, come up with a snake or a material. Or how about ResistantOS or MultisigOS to hint to the project goal. PS: Are you still interested in this project than or would your more generic OS also replace this project? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQ4UBMHIFSSBKG3KUOIJDS5VMJFANCNFSM4XGD2ZMQ> .

[ypid]

• HashbangDroid: There was/(is) an issue with using "Droid" for Android related projects but I cannot find a reference to the details right now. It was the reason why DavDroid renamed to DAVx⁵. So maybe avoid HashbangDroid.
• HashbangPhone: "Phone" does not really describe it.

Lets go with HashbangMobile and #!mobile then.

[lrvick]

Sgtm

…

On Sun, Feb 7, 2021 at 3:51 AM Robin Schneider ***@***.***> wrote: - HashbangDroid: There was/(is) an issue with using "Droid" for Android related projects but I cannot find a reference to the details right now. It was the reason why DavDroid renamed to DAVx⁵ <https://www.davx5.com/>. So maybe avoid HashbangDroid. - HashbangPhone: "Phone" does not really describe it. Lets go with *HashbangMobile* and #!mobile then. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAQ4UFBOSSR2I5L4JKGASTS5Z5DJANCNFSM4XGD2ZMQ> .