agregoreweb / agregore-mobile Goto Github PK

• Change name
• Change Android package name
• Add Agregore logo from agregore-desktop
• -Replace kiwi protocol with agregore?
  • find kiwi:// and kiwi-extension:// and replace
  • chromium...AgregoreWeb:kiwi#diff-c9e1920f32307cd0071ec49e74b36539b599cc53222666624481c4edde271d46R1302
  • chromium...AgregoreWeb:kiwi#diff-39979775b46673b59d34a0b1fe5d67648209f63d8005ac1d8d894022d5a850b3R61
  • chromium...AgregoreWeb:kiwi#diff-39979775b46673b59d34a0b1fe5d67648209f63d8005ac1d8d894022d5a850b3R61
  • chromium...AgregoreWeb:kiwi#diff-facd637dae0d1f12654a41308a50ef0a6196e82570ffccb7a11e5d3cb4538c6fR728

• what is P2P
• What can you use it for?
• How does Agregore work

Loading ipfs/ipns URLs doesn't provide any useful feedback to users. The URL might load or simply time out with no indication how long it has taken or might still take

Chromium is able to render plain text by shoving it into a pre tag with default formatting.

This however is missing important metadata tags that make text rendering look nice on mobile. It would be useful to add these headers in so that regular text files (or markdown) would render nicely on mobile.

• Include custom protocols in autocomplete settings, url index,
• Add schemes to url_constants
• Add to url_pattern
• Add to kValidUserScriptSchemes

• Find a way to set up networks with minimal user input
• Abstract into a reusable library
• Add library to Chromium source tree
• Add button to trigger Wifi Direct
• Track wifi status on button

• markdown blog
• links to main websites
• search of some sort?

We should change the new tab page to something with some useful agregore-related links: chromium...AgregoreWeb:kiwi#diff-9b83e1fc9cdc9fda1a83501eabe3e40aff0afc4069acd9431de3aed6bffe17d7R158

Change default popular websites? chromium...AgregoreWeb:kiwi#diff-8e375f68c98b02287150dd254dbea553f999bbb4c3729ed2ad000259e127f8c4R1

Since we are no longer using Kiwi as a basis for the browser, but instead are using Bromite, we'll need to figure out how to get we extensions working again.

We can try to figure out how Kiwi does extensions by reading their source code changes and try to apply a subset of them ourselves.

This is important to enable us to reuse extensions between mobile and desktop

Currently, you can't go to a regular HTTPS website that uses an ENS domain. Only an IPFS one.

IPFS urls tend to be difficult to distinguish. Some way of annotating ULRs would be useful. Bookmarks might be sufficient to address the issue?

• Make sure the suite can load in Agregore Desktop (might require re-publishing it)
• Get the suite running on Agregore Mobile with the rc1 release
• See if all the basic tests pass
• Adjust the mutability tests to account for the new way IPNS sites are created.
• Make the mutability tests pass

This process might involve adding fixes to the daemon and to the protocol handlers.

Need to figure out how to make the GH actions work.

Do we need to set up a build server? Is the source for that public?

Might be good to figure out how to compile it locally on our machines too (if that's doable)

Should be a combo of undoing the latest patch from chromium/src then running git am on it to update.

This has come up when developing new patches and having to frequently unapply and re-apply the patch you're currently working on.

Currently the google API info is hardcoded and pointing at kiwi

We should replace this with our own API keys before releasing more broadly.

It'd be nice if we could publish the app on F-Droid.

This is useful since F-Droid is able to re-share APKs over ad-hoc networks already and could be useful for spreading the APK around between people.

I'm not sure how to actually go about this so any insights/help would be very much appreciated.

@staltz is it even worth going through the hassle based on your experience of getting Manyverse on there?

https://chromium.googlesource.com/chromium/src/+/refs/heads/main/styleguide/styleguide.md

https://chromium.googlesource.com/chromium/src/+/master/docs/android_build_instructions.md

• Should these be removed?
  • chromium...AgregoreWeb:kiwi#diff-58ea104935f4c14cedef3bf47f30b804d226cb92c8a6bc62af42b8dfc38c874dR1895
  • chromium...AgregoreWeb:kiwi#diff-91a3400221a619978e7fac3e7abaed53605d11ae757a5989c9735a8b616bcda8R330
  • chromium...AgregoreWeb:kiwi#diff-d705861b230686b823980154e4690f6a5c78883d51850fff2a452fddd65aef7dR307
  • chromium...AgregoreWeb:kiwi#diff-c43f227dc68fa70be4243b70b5722b795416f182b18a7d73886edc0ec75f066cR705
  • This is a list of exceptions, we should remove it. chromium...AgregoreWeb:kiwi#diff-c43f227dc68fa70be4243b70b5722b795416f182b18a7d73886edc0ec75f066cR611

• Show the state somewhere (in the app menu?, more visible notifications?)
• Give info on how it works (in an intro, blog post?)
• List peers # somewhere?

Installing the browser requires allowing installation of apps from untrusted sources:

Allow untrusted apps
Umidigi: Apps & Notifications -> Advanced -> Special app access -> Install unknown apps -> allow chrome
Xiaomi: Settings -> Privacy protection -> …
Download Agregore mobile browser: https://bit.ly/3zcco8p

Which one does it use currently?

Ability to report content at a URL similar to how other browsers allow you to report malicious / inappropriate URLs

• Find Android API for registering protocol schemes
• Register them
• Test launching Agregore from a hyperlink in another app

Adding devtools has been a major TODO to make it possible for folks to author new content and inspect pages from their phone.

Sadly doing this natively is a lot of work since the only browser that has it already doesn't provide easy to use patches.

Instead we can use Eruda which injects javascript into a page which hijacks various APIs to provide a console for us to use.

We can have a bookmarklet in the default list which injects Eruda into a page to make it inspectable.

This won't give us stuff like breakpoints, but it'll at least let us debug stuff and have a basic console.