Monumento

[vocal kernel]

Maintainers:

Active Mentors: @balmy star (Mohammed Mohsin)

[lone spire]

Hi... is this where all conversation related to this project will take place from now on?

[vocal kernel]

Yes.

[vocal kernel]

Previous discussions about this project can be found in #monumento .

[hollow flax]

i have the same problem

and can't post images

[balmy star]

Do you see any errors in the terminal?

Probably something is missing in the post doc hence it isn't being displayed on the front

[balmy star]

Remove it and open a PR haha

[balmy star]

Also do you have an index created in firestore the posts?

[lone spire]

Oh okay I'll do that😅

[lone spire]

Also I was having some trouble with firebase storage, how should i set that up?

[balmy star]

Enabling storage in firebase should do

[lone spire]

will i have to add a payment method to enable that?
since when has firebase storage become paid 🥲

[balmy star]

Looks like you'll have to be on the blaze plan to use storage now

They do still have the free limits available on the blaze plan till October 2025, so you shouldn't be charged for it

[lone spire]

hmm ig I'll have to go ahead with that

[lone spire]

oh

okay then

thanks

[balmy star]

Looks like we will have to migrate to some other self hosted backend soon

[lone spire]

how's supabase though

have been seeing a lot of supabase tutorials on youtube lately

idk

[balmy star]

It's nice but difficult (on purpose) to self host haha

[lone spire]

ohh

I see

[balmy star]

I was thinking of https://pocketbase.io/
It's lightweight, simple, small and easy to self host

[lone spire]

ouu never heard of this... hmmm

ohh pocketbase is written in GoLang 😮

[hollow flax]

Resonate migrated from firebase to appwrite last year i guess

[lone spire]

Hi... I made the PR 🫡

[lone spire]

Hi... how is the monuments collection supposed to be populated, cuz I don't see any statement in the project that adds monuments, and ig since the collection doesn't exist, it throws me this rangeError

[thorn pelican]

Hello @Mohsin Myself Mohit Lakra,
I am contributing to open Source first time but I will try my best.
If you find some issues in which i can contribute please let me know

[thorn pelican]

Can someone please help me.
I am getting these red wavy lines in line number 16 where firebase_options.dart is imported

[lone spire]

yea you have to setup a firebase project on ur local, and then run the firebase setup for flutter

[thorn pelican]

Got It.
Thanks

[balmy star]

Merged

[balmy star]

We have a script (thanks to @median perch ) that populates the monuments collection, you can run it once to add a monument. More dummy monument details have to be added to the script so that there are atleast 4-5 monuments

[balmy star]

Hi Mohit

[balmy star]

Maybe this can be your first issue, to improve the docs to mention about stuff like this? 😉

[thorn pelican]

Thanks Mohsin for giving attention,
I will improve the docs

[thorn pelican]

sorry to disturb but can you please tell me my task more clearly.
first i think i have to update README.md regarding the script that populates the monument collection but it was already there

[balmy star]

I mean updating the docs to make it clear that they will have to setup firebase to be able to run the app successfully, and run the script if they want to add the monuments data etc etc

[thorn pelican]

GOT IT
thanks

[median perch]

You can pull the latest branch, which has been merged with the develop branch. The RangeError issue has been resolved after adding a script to populate the monument data.
@lone spire

[lone spire]

ohh okay

thanks

[thorn pelican]

Please help me Getting this issue while running flutterfire configure

[thorn pelican]

Hi @balmy star , I have made the PR

[steep bane]

make a firebase account of your own and start the firestore database and authentication with email after that run flutterfire configure --<project id from firebase>
mine was flutterfire configure --project=monumento-277103-41a9c

[thorn pelican]

thanks
it works

[lone spire]

Hi... I was having this problem on iOS that after signing in, I had to restart the build in order to get to the Home screen

it doesn't redirect me on its own

[lone spire]

it signs me in, but doesn't redirect me to HomeView

[thorn pelican]

Got this error at bottom while sign in
[cloud_firestore/unavailable] Failed to get document because the client is offline

[lone spire]

Hi... I also had a query that... How am I supposed to add one user as another user's follower, cuz initially the following list is empty, and therefore when it fetches the "following" posts, it returns an empty list, because of which, the discover page is always a circular progress indicator... So now how am I supposed to add a follower there

@balmy star @median perch

[steep bane]

i am facing this issue after new mreged commits if anyone has solution or temp solution please share

RangeError (index): Index out of range: index should be less than 4: 4

is this happening with others ?

i checked if it wasnt due to me and cloned again from the github page and this is the video of it

[balmy star]

It happens sometime with unstable internet

[balmy star]

Discover page should show posts from random users and not your followers/followings. Looks like some missed cases or something is wrong, can you try debugging and figure out why it is always a circular indicator?

[balmy star]

Is this after seeding the data?

[steep bane]

Yes sir

[steep bane]

@balmy star I have found the issue and I can fix it should I open a issue and pull request ?

after making few changes

[balmy star]

Yes please

[median perch]

This issue appeared after I seeded the data for monuments. It is related to the current UI code and not to the script changes I made earlier. Since there was no data on the page before, the issue did not surface. You can create a PR to fix it.

[steep bane]

yea i know it was a ui bug

[steep bane]

btw you did a excelent job with the script

[median perch]

You can use List.generate and leverage the index to ensure it stays within the bounds of the number of images. This will help prevent issues like the following:
RangeError (index): Index out of range: index should be less than 4: 4.

[steep bane]

thanks

the ui code had hardcoded values of indexes

[median perch]

Yes, this is the main issue

[steep bane]

and insted of using gridview or list it had hardcoded containers

[median perch]

Thnx Eng soumya

[steep bane]

which is also causing overflow issue i will try to fix all of these by tonight

[median perch]

Go ahead, best of luck

[steep bane]

hey @balmy star can you review few of my pull requests and merge them when you are free ... and if there are any issues in my pr then please also let me know .
my github id is hellosnipermonkey

[balmy star]

Sure

[balmy star]

Left some reviews, pls check. We can have a better and permanent fix for this issue by simply doing what the mobile UI does, that is using a carousel instead. The mobile UI already implements the below package, you can try doing the same for web/desktop

https://pub.dev/packages/carousel_slider

Having images displayed in this fancy way was a bad idea XD

[steep bane]

ok will look into it and implement it

[lone spire]

@balmy star this was what i was talking about on the discover view, the function doesn't return posts from the following list, but it does a check if the number of following is 0, in which case it just returns an empty List, leading to the CircularProgressIndicator

[lone spire]

also there's an issue where the search feature for searching people inside discover view probably shouldn't display the user using the app on searching, and if it does, then it should redirect to the profile page of the current user

right now, I can add myself as my own follower

which doesn't make sense 🥲

[lone spire]

also there are a couple of issues related to this, first of all the check shouldn't be there imo, so I commented the check for followingUids.isEmpty, but after that, I could see my own posts in the discover page, which again doesn't seem to make sense considering I shouldn't be able to see my own posts in the discover page right, could u help me on this one 🥲 , so I wrote a couple of lines to filter out the posts from other users

also in the DiscoverProfileViewMobile there was an issue with the LoadDiscoverProfilePosts event not being called, while there was a call for the same in the desktop view

and after fixing that, there was an error with the placement of the expanded widget, which should be placed right above the GridView.builder

after fixing all of these things, the app is finally working completely fine on my local environment, with every feature working as it should

I was just wondering if I could make a PR to address all these issues

[steep bane]

umm @balmy star i made the changes you suggested just check once before merging

[balmy star]

I see

[ruby heath]

@balmy star You are now level 2! :confetti_ball:

[balmy star]

Sure pls go ahead

Nice work @lone spire

[balmy star]

Yeah that check shouldn't be there. I'll have to check what exactly is happening there, haven't touched the code in a while due to work. Will do it soon

[balmy star]

Alright

[median perch]

@balmy star
I’ve completed work on this pull request https://github.com/AOSSIE-Org/Monumento/pull/209
Could you please review it?
Additionally, I’ve proposed a new feature in this issue. Could you assign it to me so I can start working on it?
https://github.com/AOSSIE-Org/Monumento/issues/210

[lone spire]

@balmy star I made the PR, could u review it, there are a couple of changes

[ruby heath]

@lone spire You are now level 2! :confetti_ball:

[balmy star]

Done

[ruby heath]

@balmy star You are now level 3! :confetti_ball:

[balmy star]

Done

Guys, for now, let’s pause any new features and focus on moving away from Firebase in the coming weeks, possibly to PocketBase, Supabase, or Appwrite. Weigh in with your suggestions if you’ve used any of the three solutions.

Having used all three, my personal preference is PocketBase because it’s simple to host and very lightweight.

[tawny zealot]

I would suggest Appwrite. Based on my following observations:

• It fluently integrates with flutter. (great documentation)
• offers more perks in free/pro plans (also gives free pro subscription to open source organizations).
• feature set of appwrite > pocketbase. So if we plan to add any feature in future, it won't be a hassle.

just my opinion:)

[median perch]

@balmy star I suggest using PocketBase for our current needs. It’s lightweight, simple to host, and cost-effective, offering all the essential features we require without unnecessary complexity. It aligns well with our priorities and ensures an efficient transition from Firebase.

You can check now latest changes you suggested for this pr
https://github.com/AOSSIE-Org/Monumento/pull/209

[vale jay]

i am trying to setup and when i am trying to sign in, i am facing this error

[torpid sentinel]

trying to setup project getting this error, can anyone help me ?

[steep bane]

try running the chrome or web version

[steep bane]

in my opinion appwrite would be a good choice because as ayan gupta said "feature set of appwrite > pocketbase. So if we plan to add any feature in future, it won't be a hassle." also it has self hosting flexibility in case of unforeseen circumstances, we can easily migrate the database and run it locally, ensuring data security and can provide 24/7 service

[lone spire]

u could do flutter clean and flutter pub get once and try

[sand crater]

Since this a web based flutter app
There are many step missing in the project setup

To enable Google Sign In -
Enable Google People API and sign up again

Also one Must ensure this when storing images
https://stackoverflow.com/questions/41943860/getting-403-forbidden-error-when-trying-to-load-image-from-firebase-storage

To view images on web -
https://stackoverflow.com/questions/37760695/firebase-storage-and-access-control-allow-origin

[ruby heath]

@sand crater You are now level 3! :confetti_ball:

[lone spire]

@balmy star are we finally going with appwrite or pocketbase

[median perch]

Can you please latest PR i have raised? @balmy star
https://github.com/AOSSIE-Org/Monumento/pull/220

[slate lagoon]

i am trying to setup locally the Monumento repo. But i facing some issues. @balmy star

[uncut wave]

@balmy star I am trying to setup this repository locally but getting errors related to gradle. Can any one help, l’m using flutter version 3.22

[lone spire]

what all have u guys tried

as in fixing

cuz i was having trouble on both ios and android

and i changed the firebase dependency versions and then reinstalled pods and then it was pretty much done

on android i had to change the compileSdk version

[uncut wave]

What flutter version you’re using

[lone spire]

3.27.1

[uncut wave]

Hey I was able to run the project locally. For me the image_cropper was creating the problem.

Adding these lines of code to AndroidManifest.xml file worked for me

[lone spire]

ohh

[uncut wave]

I have created an issue and want to work on that, Should I wait to get assigned or directly make a PR
https://github.com/AOSSIE-Org/Monumento/issues/221

[ruby heath]

ashutoshsingh71

KARNX7's stats

You can view the leaderboard or your profile!

Stats

189 messages
0 seconds in voice

Experience

Level 10
193/212 XP
1,380 total XP

Jan 7, 2025, 8:08 PM

[uncut wave]

Raised an issue https://github.com/AOSSIE-Org/Monumento/issues/223

@lone spire are you working on any issue

[lone spire]

hi... not atm, I did work on a couple of issues before though

[ruby heath]

@lone spire You are now level 3! :confetti_ball:

[uncut wave]

should I start raising PR, I haven't assigned any issue yet

[ruby heath]

@uncut wave You are now level 2! :confetti_ball:

[lone spire]

i mean yes u can if there's no one else working on those issues

i fixed a couple of issues in a single PR, and they weren't listed as issues on the repo, but were literally essential bugs that needed to be fixed, so I just raised a PR and wrote everything in there

[uncut wave]

oh thanks

[uncut wave]

hey can anyone review my pr which resolves issue no.221, 222, 223
https://github.com/AOSSIE-Org/Monumento/pull/224

[toxic marten]

hi @balmy star for issue 178 I just identified that the code is managing _isLoading boolean variable to ensure the state and at the same time the bloc is also managing the state, both are using circularProgressIndicators() which is resulting in 2 of them. Is that the point?

[median perch]

Check the GitHub comment threads, @toxic marten —I've replied to you there.

[median perch]

I noticed something in your commits that could enhance your contribution. @balmy star recommends focusing exclusively on the issue that has been specifically addressed when making a pull request (PR) rather than incorporating unrelated fixes or enhancements. This approach helps to keep each PR clear and purposeful, making it simpler for reviewers to understand and approve your changes.

[toxic marten]

hello everyone, are there any issues on which I can work in this project?

[balmy star]

Sorry guys for the delayed response, I was AFK here due to work and personal stuff. I'll be reviewing all the open PRs hopefully by tomorrow

[ruby heath]

@balmy star You are now level 4! :confetti_ball:

[balmy star]

Can someone pls open a PR updating the readme? I totally forgot to include these things back then

[lone spire]

i'll do this asap

[balmy star]

I was considering PocketBase because it’s simpler and doesn’t have too many features. I have a self-hosted instance of Appwrite running on the cloud for one of my personal projects, but something or the other tends to break every time there’s an update. Additionally, it requires significantly more resources compared to PocketBase. My plan was to deploy PocketBase somewhere and make it publicly accessible so users don’t have to set up a backend themselves. However, if the majority of you prefer working with Appwrite, we can proceed with that as well

[median perch]

I think PocketBase sounds could be a better fit for our project.
I totally agree with you@balmy star

[ruby heath]

@median perch You are now level 2! :confetti_ball:

[median perch]

Check comment related to latest raised PR @toxic marten

[iron field]

@balmy star i want to start contributing but right now i don't know much so i should start with learning swift right?

[uncut wave]

This project is using flutter

[ruby heath]

@uncut wave You are now level 3! :confetti_ball:

[uncut wave]

@median perch SERVER_CLIENT_ID is same as GOOGLE_SIGNIN_ANDROID_CLIENT_ID??

[twilit granite]

hi @balmy star @vocal kernel , Shruti this side , I am a proficient application developer and I am interested in contributing into this project..
my tech stacks - Flutter , nodejs , javascript , html , css , django etc.
I am also working towards my problem solving and competitve programming skills.
I am also exploring side towards golang and rust.

[median perch]

@uncut wave

• GOOGLE_SIGNIN_ANDROID_CLIENT_ID is used for logging into Google on Android apps.
• SERVER_CLIENT_ID is used by servers to check that the login information sent from an app is valid.
  They are usually different because they serve different purposes: one is for the app and one is for the server. However, some smaller apps might use the same ID for both, though it's not usually recommended for security reasons.

Can You please check latest two PR's?@balmy star

[lone spire]

a follow up to this, my bad for the delay, I just made the PR for the change in documentation

@balmy star

[median perch]

@balmy star Can u please check latest pr 🙏

[balmy star]

done

[ruby heath]

@balmy star You are now level 5! :confetti_ball:

[median perch]

I have replied for the comment , can you please check again?

[steep bane]

@balmy star should i make a FAQ.md to address common questions related to the project and people can make change to it and add their experiences like common errors faced while running project on ios ,android , macos , etc and how they solved them which will save time for others

[steep bane]

or should i make a faq part at the very bottom of readme.md just above licence

[ruby heath]

@steep bane You are now level 2! :confetti_ball:

soumya5845

soumya's stats

You can view the leaderboard or your profile!

Stats

7 messages
0 seconds in voice

Experience

Level 2
5/103 XP
105 total XP

Jan 24, 2025, 5:52 PM

[median perch]

@balmy star
Can you please check my latest PR?
https://github.com/AOSSIE-Org/Monumento/pull/238

[steep bane]

@balmy star can you check my latest PRs ?
https://github.com/AOSSIE-Org/Monumento/pull/233
https://github.com/AOSSIE-Org/Monumento/pull/241

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/243

[median perch]

Can you please review this PR ? @mdmohsin7
https://github.com/AOSSIE-Org/Monumento/pull/252

[steep bane]

Can you please review this PR @balmy star
https://github.com/AOSSIE-Org/Monumento/pull/251

[balmy star]

Done! Have reviewed all the PRs

[median perch]

Thanks bro for your effort 💯

[ruby heath]

@median perch You are now level 3! :confetti_ball:

[rugged root]

hi can somebody help me out with this issue. I was trying to install the app on ios simulator and it was giving this error. i tried googling it but no luck as the same error for produced for some other dependency

[night galleon]

.

[iron wharf]

Hey y'all! I'm Deeptej, a CSE undergrad, and I'm looking to contribute to the Monumento project! I was setting up the project locally and reached the part where it needs me to add the SERVER_CLIENT_ID GOOGLE_SIGNIN_APPLE_CLIENT_ID GOOGLE_SIGNIN_WEB_CLIENT_ID and GEOAPIFY_API_KEY and needed help with the google keys, do i need to set up a project on google cloud and then get the keys from there? clicking the link provided in the README.md for the project takes me to a 'Google Identity' website

[dawn patrol]

Hi everyone , i wish to contribute on this project , getting error during sign up with google and sign up with email , can anyone kindly help me in solving this ?

@balmy star please sir.

[balmy star]

Hi yes you'll have to get the keys from GCP. Once you create a project in Firebase, the same should be there in GCP as well

[balmy star]

Make sure you have enabled 'Sign In with Google' in FIrebase Auth

[ruby heath]

@balmy star You are now level 6! :confetti_ball:

[dawn patrol]

thank you😃

[sick glacier]

hi @balmy star I would like to contribute in this project, i am very well versed with flutter and firebase

[sturdy loom]

.

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/261

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/262

@balmy star
Can you please review these PRs?

[balmy star]

Sure

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/241
@balmy star can you review this PR ?

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/266
Can you please review this PR ?
@balmy star

[iron wharf]

Hello! Needed help with the setup! I created a project on GCP and got the keys for android, ios, web and the geoapify, im currently on the firebase part. I ran flutterfire configure and got this ```? You have an existing firebase.json file and possibly already configured your project for Firebase. Would you prefer to reuse the values in your existing firebase.json file✔ You have an existing firebase.json file and possibly already configured your project for Firebase. Would you prefer to reuse the values in your existing firebase.json file to configure your project? · yes
Failed to write android google-services.json file write for default service file. Please report this issue at:https://github.com/invertase/flutterfire_cli. Exception: ServiceFileRequirementException: android - Failed to obtain the service file: google-services.json for android. Response code: 403. Response body: {
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}

ServiceFileRequirementException: android - Failed to obtain the service file: google-services.json for android. Response code: 403. Response body: {
"error": {
"code": 403,
"message": "The caller does not have permission",
"status": "PERMISSION_DENIED"
}
}``` Could someone help me out please?

I've already created a project on GCP to get the API keys as mentioned in Step-1 of the setup doc

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/267
Can you please check this PR?
@mdmohsin7

[steep bane]

Did you create a project in your own firebase ?
Also did you sign in to firebase through your terminal ?
These 2 steps are necessary.
As my current understanding is you are trying to use the predefined code used which points to the firebase account of owner which you don't have access to. So make a account on firebase setup a project and in terminal change the firebase to your own firebase project this should fix your issue

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/272
Can you please review this PR ?@balmy star

[ruby heath]

@median perch You are now level 4! :confetti_ball:

[balmy star]

Sure will do

[ruby heath]

@balmy star You are now level 8! :confetti_ball:

[median perch]

Hi @balmy star,

I had a discussion with @steep bane, and we've confirmed that we'll be using AppWrite for the upcoming migration events ✅.

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/266
@balmy star
I have resolved conflicts, and the branch is now ready to be merged.

[tawny zealot]

Hi @median perch, I'm familiar with appwrite (I love it), I almost use it for all my apps.I have been contributing to monumento for a while now and I would like to collaborate with you and @steep bane to migrate our backend to appwrite.

cc: @balmy star

[ruby heath]

@tawny zealot You are now level 2! :confetti_ball:

[wise ingot]

hi

hi#

o

i want contribute

in gsoc

how i start ?

@balmy star

[median perch]

Hi @tawny zealot

That sounds great! We've discussed this with @steep bane , and I'll be focusing on the auth module of our app as the initial step. You can take the part of the current app that deals with the database and start migrating it to Appwrite. Looking forward to collaborating on this! Let me know if you need any inputs as you proceed.

[wise ingot]

hi @median perch

[tawny zealot]

Cool @median perch :)

[lone spire]

Hi guys, I've been a little involved with exams and stuff for the last 10 days, could someone get me up to pace with what we're doing from now onwards, also I saw that we've finalised migration to appwrite, could someone give me a short summary of what I missed in the last 10 days🥲 @median perch @steep bane

[steep bane]

Well in the last few days lots of commit came to the project and regarding the db change we discussed about appwrite,supabase, pocketbase and came to a conclusion to use appwrite as it is many similar features to firebase and has good documentation.

[steep bane]

Also appwrite provides pro tier to students for free if you have GitHub education plan.

[ruby heath]

@steep bane You are now level 3! :confetti_ball:

[tawny zealot]

My suggestion, we should plan to setup appwrite locally. (Like in the project #1317913663360864346 ) It's better that way. Decreases dependence on appwrite.io and more of self hosting.

[steep bane]

But you would need a vps(virtual private server) for that

[tawny zealot]

No

Locally on the user's system

And it's not even that heavy. (I have 8 gigs of ram and works fine along with all the android dev project.)

[ruby heath]

@tawny zealot You are now level 3! :confetti_ball:

[steep bane]

Okay, it seems that I misunderstood

[steep bane]

Is this setup for testing the app locally ? When there is no internet connection ?

[steep bane]

@tawny zealot can you add the problem encountered in https://github.com/AOSSIE-Org/Monumento/issues/270 to FAQ section

[tawny zealot]

I don't feel there is a need to add it to FAQ, It's just a minor bug a pr regarding it has already been raised, and when it merges it will get solved.

[tawny zealot]

You can test locally as well.

[steep bane]

Ok, no problem

[steep bane]

Yea I tested it and it's working

[wary harness]

https://github.com/AOSSIE-Org/Monumento/pull/275
https://github.com/AOSSIE-Org/Monumento/pull/273
Can you please review these Prs? @balmy star

[tawny zealot]

@balmy star
Please review this https://github.com/AOSSIE-Org/Monumento/pull/276

[balmy star]

Whoever is interested in working on the migration can collaborate with others and work on it together. It’s not specifically assigned to Kareem or Soumya — it's open for everyone to contribute, divide tasks, and complete the migration collectively.

Before opening a PR, please make sure to first create a relevant issue for it. Also, try to keep your PRs limited to the changes mentioned in the issue to ensure they remain clean and easy to review.

Looking forward to seeing everyone collaborate on this!

[ruby heath]

@balmy star You are now level 9! :confetti_ball:

[tawny zealot]

I've finished the database migration to appwrite and raised a PR here.

What's the status on auth migration? @median perch

[median perch]

Iam currently working on it

[tawny zealot]

@vocal kernel SPAM

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/281
Can you please review this PR ?
@balmy star

For any one who is working on the Appwrite migration, there's a small but annoying issue you might run into.

🔴 The Problem: Build Failure on Android

• Appwrite depends on flutter_web_auth_2 v3.1.2, which still uses the old Registrar API.
• Flutter 3.x removed that API, so if you're using a newer version, your Android build will fail.

✅ The Fix: Override the Dependency

Instead of waiting for an Appwrite update, you can manually override the dependency:

• Set flutter_web_auth_2 to v4.1.0, which removes the outdated API.
• This will fix the build issue instantly.

📌 What You Need to Do

Just add this to your pubspec.yaml:

dependency_overrides:
  flutter_web_auth_2: ^4.1.0

This keeps everything working smoothly until Appwrite updates its dependencies.

Once Appwrite upgrades flutter_web_auth_2 on their end, you might not need this override anymore

[median perch]

This is my reference :
https://www.appwrite.io/threads/1334415894394306571

[ruby heath]

@desert robin You are now level 12! :confetti_ball:

[waxen pebble]

Hi everyone! I came across Monumento and love the concept. I have experience in UI/UX design and have worked on an AR-based project before, so I understand the importance of a seamless user experience in AR apps.

I’d love to contribute by sharing Figma mockups that refine the UI and improve usability. Would the team be open to reviewing design suggestions? If yes, I can share some initial mockups and refine them based on feedback.

Looking forward to your thoughts!

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/284

Can you please review latest PR ?
@balmy star

[ruby heath]

@median perch You are now level 5! :confetti_ball:

[wary harness]

https://github.com/AOSSIE-Org/Monumento/pull/283
https://github.com/AOSSIE-Org/Monumento/pull/288

Can you review these PRs?
@balmy star

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/286/
@balmy star can you review my latest PR
and i would like to suggest all the appwrite related changes be merged in a different branch than develop because some of social features require authentication features and working between 2 different modules need to be tested before it is merged on main branch

[steep bane]

hey @median perch can you please put this info on FAQ.md so new contributors dont have to face this issue .

[balmy star]

Will check all the PRs tomorrow

Also I've created a branch named appwrite-migration, pls change the base branch from develop to appwrite-migration for appwrite specific PRs

[median perch]

Consider id done 👌

@balmy star
Branch conflicts resolved, you can check it now ✅

[steep bane]

@balmy star merge conflicts resolved, please merge the branch at your convenience

[ruby heath]

@steep bane You are now level 4! :confetti_ball:

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/291
@balmy star can you review my latest PR

[summer rover]

@balmy star i think we shouldn't migrate from firebase to appwrite, due to API call limits

[tawny zealot]

Bro.!? Context... Explaination..

[summer rover]

API call krne ki limit hoti hai appwrite main, once you use that limit your project will not respond

[steep bane]

Can you tell me what is the rate limit of firebase and appwrite so we can consider solutions to mitigate rate limit issues

[balmy star]

Those are the usual rate limits. Shouldn't be an issue as long as you are not abusing their APIs

[summer rover]

one of my friend using appwrite and he is getting this issue that's why i'm telling you

[tawny zealot]

Bro all the serverless backends have more or less the same rate limits. And your friend facing rate limits is because he's testing/debugging the app, In the real word It's just to protect api abuse and works fine.

Also fyi, there is a "whitelist" thing in AW, do check it out.

[ruby heath]

@tawny zealot You are now level 6! :confetti_ball:

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/293
Can you please review the latest PR?
@balmy star

[balmy star]

will check

Also what's the status on the migration? what all do we have pending?

[tawny zealot]

All the individual repositories have been migrated to appwrite. Now the only work that is left is to connect them with the UI, make them work, fix bugs and remove the firebase from the app.

I'd like to create a new issue and work on it.

[balmy star]

if no one is working on it then pls do it

[tawny zealot]

Created the issue, please assign.

https://github.com/AOSSIE-Org/Monumento/issues/294

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/296
@balmy star Can you please review this PR at your convenience ?

[median perch]

I've reused as much existing code as possible for a smooth migration. My code listens to the Appwrite users collection and works as expected, without needing a direct UI connection. Now, I'm proceeding with the next steps from the PR, including Google Sign-In and Forgot Password implementation.

I also suggest writing unit tests to ensure the migration to Appwrite is working correctly. This includes testing data retrieval, create/update/delete operations, and handling failure scenarios. We can use flutter_test for unit testing and mockito for mocking Appwrite responses. This will help maintain the migration and catch potential issues early. Let me know if there's anything else to consider @balmy star

[tawny zealot]

Yeah agree @median perch I and @steep bane did the same. But there are few bugs and also minor changes in the structure of the database are there. So to consider those changes in the UI. I have created the issue.

[tawny zealot]

About tests I don't think they are necessary yet in migration. One could address those in the develop branch as the migration branch is merged.

[steep bane]

Okay so we can make unit tests for develop branch when it's time to merge the migration branch to develop branch so that everything operates smoothly

Also i have some suggestions for appwrite populate script

[median perch]

Ayan, I get your point, but adding unit tests now can save time and prevent issues later. Since we're making structural changes and replacing Firebase with Appwrite, tests will help catch breaking changes early, ensure data consistency, and reduce future debugging efforts. If we merge first and test later, debugging could be harder. Even basic tests for authentication, data retrieval, and CRUD operations can help prevent regressions. What do you think?

[median perch]

That makes sense, But adding basic tests now can help catch migration issues early and prevent bugs from reaching develop. What do you think?

[tawny zealot]

Yeap cool @balmy star can tell is going on on tests would be right at the current point of time.

[steep bane]

Yes while I was making changes in appwrite social repo debugging was really tough job because it was a 2000 line file,
If tests can prevent long debug time then I am all for it

[balmy star]

We can include basic unit tests but only if they don't take too much of our time. Personally I'd say first migrate everything, then do a manual end to end test, and then write unit tests to validate core stuff

[median perch]

Yeah, that makes sense. Get the migration done first, test it manually, and then add unit tests for the important parts. Sounds like the right balance.

[ruby heath]

@median perch You are now level 6! :confetti_ball:

[tawny zealot]

@median perch just was running the app and auth isn't working. Did you check it with ui??

[median perch]

Yes , i have checked it before submitting and every thing was working fine , as attached in PR
but let me check again

[median perch]

I noticed there’s an issue with the manifest file related to the Appwrite project ID. I’ve resolved it in the hotfix branch, and the app should function properly once the branch is merged.
@tawny zealot , @balmy star

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/298
Can you please check this ?
@balmy star

[median perch]

@tawny zealot you can rebase with current branch untill @balmy star review and merge with 'appWrite-migration' branch , i think all your issues will be solved and continue your flow smoothly

[native wharf]

Hey, I’m setting up the project and need some clarification. Has the migration from Firebase to Appwrite been fully completed? If so, what’s the updated setup process? If not, should I follow the existing setup guide, or is there anything else I need to consider?

[median perch]

Hey @native wharf , hope you're doing well!, The migration to Appwrite is still in progress, and there are some issues that need to be resolved. The code hasn’t been merged into develop yet, so for now, you can follow the current setup guide. Once the migration is complete, we'll update the guide to reflect the Appwrite setup.

[median perch]

Can you please review this PR ?
@balmy star
https://github.com/AOSSIE-Org/Monumento/pull/301

[lone spire]

@median perch i noticed that appwrite_auth_repo has 4 instances of a variable called APPWRITE_USER_COLLECTION_ID, but it hasn't been declared in the .env.template, could u clarify whether it's the same as APPWRITE_USER_ID ?

also i changed the above to APPWRITE_USER_ID to make it work on my local, but it still throws me an error when trying to sign up, where it says that we're trying to push "uid" as a param when creating the document, but the collection doesn't have an attribute called uid, also i made and populated all the collections using the appwrite_setup.js script

[ruby heath]

@lone spire You are now level 4! :confetti_ball:

[lone spire]

could u help me here

[tawny zealot]

There is are many issues. The uid there has to be jsonseriolized to $id

Also the two variables are same

[lone spire]

yea

got that

[lone spire]

but it still shouldn't be pushed as part of the data right?

shouldn't it just be the documentId for the document

[tawny zealot]

Yeap it need not be pushed

[lone spire]

hmm

okie thanks

[tawny zealot]

Np these issues were created while pushing the auth repository by @median perch

I don't know if he has corrected these in a recent pr he raised.

[lone spire]

i mean i pulled the latest code from the appwrite-migration branch

and the last hotfix pr was merged by then

so... afaik i don't think this issue has been dealt with yet

[tawny zealot]

I see i fixed these issues in the local branch i had but there were simple too many issues to deal with so i have kept it still on hold.

Wanna sort this together in a pr? (Collaborate) @lone spire

[lone spire]

yes sure

[wary harness]

https://github.com/AOSSIE-Org/Monumento/pull/304
https://github.com/AOSSIE-Org/Monumento/pull/300

@balmy star Can you please review these PRs?

[balmy star]

done

[balmy star]

I'm guessing everyone used different variable names when working on different issues. Pls try to use same var names and stuff. Also pls test thoroughly the appwrite migration branch and if any issues noticed, feel free to open an issue and PR fixing it. And whoever worked on migration of that specific feature (in which an issue has been found) can review it. I'll review the PRs after them and will merge it. This way the one who migrated can also cross check if the fix is correct or not

[median perch]

Hey @lone spire @tawny zealot , the issues you were facing was due to :

1. Environment variables were inconsistent across modules, so I unified them to use the same names.
2. The sign-up error was caused by a missing uid attribute in the Appwrite collection setup that@tawny zealot created . I updated the setup_appwrite.js script to include it, matching Firebase’s structure.

To apply the fixes:

• Pull the latest code after my PR is merged by @balmy star .
• Delete your current Appwrite database, run the updated setup_appwrite.js script, and set all collection permissions in the Appwrite console.
• Test the sign-up process—it should now work smoothly.

https://github.com/AOSSIE-Org/Monumento/pull/305
This the hot fix branch , can you please review it @balmy star

[tawny zealot]

hey @median perch don't use uid in setup_appwrite.js

its $id instead of uid what you're using

don't touch that i've updated it and made changes to accomodate it in the app code. I'll make a issue and PR. Please pull that and use that to further develop other features.

also rather than creating a new uid field for a user's document. use the same userId as the documentid in user collections. so it will be easy to conect the user and its relative userdata

[median perch]

uid is already the same as document id , you can check the firebase repository on getOrCreateUserDocForEmailSignup method , we need to send the uid with rest of user data after sign up , which you havnt added in your script while creating the user collection attribute , and that was the root cause of the issue

[median perch]

@balmy star
Can you please share with us your opinion about this ?

[ruby heath]

@median perch You are now level 7! :confetti_ball:

[lone spire]

i mean unless we're tryna change the entire structure, ig creating a uid field won't do much harm, considering it was also a part of our firestore documents' schema thing

but idk if its of any use if we already have it in the documentId

[median perch]

Excatly 👌 , that will not affect any of database structure , but this already the original firebase decoument structure , that we are migrating from .
this solution is as simple as just adding one more parameter to the script without affecting the current data base structure
@balmy star @lone spire @tawny zealot

[tawny zealot]

if won't harm us but we don't need to add it. that's it

[median perch]

We need appwrite document structure to hold the user id after creation , in the same level of user name , email , etc ...
as it was in firebase

This is the original firebase user collection structure we should have after user successfully Sign up

[tawny zealot]

Yeah this was in firebase but we don't need to blindly copy this to appwrite. At last all details will be converted to a usermodel before using in any UI component/screen.

[ruby heath]

@tawny zealot You are now level 9! :confetti_ball:

[median perch]

I think it’s absolutely necessary to include the userId as one of the attributes when creating a user document. This isn't just blind copying it's a fundamental requirement for any database structure. This ensuring that user-related data is correctly associated and retrievable.

[tawny zealot]

But a $id is automatically created when creating anh document in appwrite.

[balmy star]

Let's not spend too much time discussing whether to include a field or not. If the codebase has a reliance on that field in multiple places, then let's just have it. If there's no reliance then just remove it

Besides, what's the current migration state? I've lost track of it. What all is left and who's working on what?

[median perch]

The auth module depends on it in several places, so we can keep it and move on from this point to focus on the next thing.

[median perch]

The auth is 100% working ✔️
all that's left for me is reset password. I'm currently working on it, and once it's done, I'll move from the auth module to testing current app features after migration and fixing any broken features.

@balmy star Please review my latest branch I’ve fixed the inconsistent env variables and the Appwrite exception that @lone spire faced yesterday. Any new contributor working on the migration would have encountered the same issue.

https://github.com/AOSSIE-Org/Monumento/pull/305

[steep bane]

sorry my bad i missed it while i was resolving merge conflict

[steep bane]

there seems to be some errors in my part (social repository) part , i am looking into it and will provide a fix soon

[balmy star]

So is everything clear between @tawny zealot and @median perch?

[tawny zealot]

Yep pretty much! I'm waiting for kareem's pr to get merged and then analyse and follow up.

[median perch]

Yep, waiting for your review insha'Allah

[mossy quest]

Hello @everyone, I’m excited to share that I have successfully set up the project on my local environment and am eager to contribute to this amazing project.

[balmy star]

done

[mossy quest]

I think most of face gradle issue while setting up this project like i faced! for that i think i have the solution for this

--> use jdk-21 version with setting up

1.android/gradle/gradle-wrapper.properties --> distributionUrl=https://services.gradle.org/distributions/gradle-8.5-all.zip

2.android/setting.gradle within plugins --> id "com.android.application" version "8.2.1" apply false

3.android/app/build-gradle --> minSdkVersion-23

If still not working then use "flutter doctor --verbose" to check if Android toolchain is using java version 17, like this is using --> Java version OpenJDK Runtime Environment (build 17.0.10+017.0.10b1087.21-11609105)
if not then use this to fix it-> "flutter config --jdk-dir="C:\Path\To\Your\JDK17"

Hopefully your problem would get fixed.

[steep bane]

Hey @mossy quest can you please put this info in faq section of documentation so others will have better android build experience

[ruby heath]

@steep bane You are now level 5! :confetti_ball:

[mossy quest]

@balmy star should i raise a pr for this ??

[balmy star]

yes pls

[mossy quest]

@balmy star pr has been rasied please have a look.

[tame ingot]

@here
Hey everyone!
I’m excited to share that I’ll be mentoring on Monumento alongside @balmy star.
Feel free to reach out if you need help with proposals, code reviews, or any questions.
Wishing you all the best!

[tame ingot]

Are there any updates on the migration work?
Could you please share what's still pending in each repository?
@steep bane @median perch @tawny zealot

[ruby heath]

@tame ingot You are now level 5! :confetti_ball:

[tawny zealot]

Hey @tame ingot All the repositories have been migrated but still some issues with the each of them connecting with each other. Am working on it and in #294

Now planned to collaborate with @steep bane to close this asap.

[tame ingot]

Great!

Can you list exactly what is still pending and which features are currently broken with Appwrite? This way, we can break them down into smaller issues and PRs rather than getting stuck on a large bulk PR for too long.

It seems like we've been in the same state for about two weeks now. Clarifying everything will help everyone move forward. I also suggest mentioning the broken features in your proposals and considering the time required to fix them.

[tawny zealot]

Hey @tame ingot tbh I'd love to break it down to smaller issues so we all can work together. But the problem is this issue can't be broken into more smaller issues. We're trying to integrate appwrite architecture in the app. We initially tried distributing work by building each repository separately me, Soumya and Kareem but problem arises that we end up setting up appwrite inefficiently, creating different conflicting collections our own way, giving rise to many more issues, bugs on the way.

what I suggest is, give us some time I and @steep bane have had a discussion, understood where the app bugs and what we need to fix and we'll work together to close this asap.

Here's a list we came up with about some issues independent of appwrite setup that other contributors can start working on.

[steep bane]

1. error handling of session management when the session is active in appwrite but user is logged out of actual app , so he cant login becase of session already in use error

2. Image post sometime not being posted and user gets logged out of app while/after posting image posts

[tame ingot]

I see your point, but breaking things down is still essential to avoid delays. Even if we can’t split everything into separate PRs, we need a clear list of what’s broken.

For example:

• Publishing a post is broken
• Password reset is not working

Please test things together and compile a list of broken features so I can track progress and help stabilize the app as soon as possible.

As for the conflicting collections, @median perch has already resolved those issues. I’ve tested it, and there are no setup conflicts at the moment. Our main priority now is identifying and fixing the broken features.

[tame ingot]

Away from the minor problems, let us focus on making the main features work

• sign in
• signup
• google auth
• password reset
• fetch/bookmark monuments
• fetch/edit profile
• post
• post like/unlike/comment

[ruby heath]

@tame ingot You are now level 6! :confetti_ball:

[median perch]

I'm working on the authentication module of the app and have completed almost everything needed. Currently, I'm working on the reset password feature, which is nearly done. The only issue I'm facing is with the password reset flow—when the user enters their email, Appwrite sends a reset email, but the redirection link for submitting the new password isn't working as expected. I'm actively working on resolving this and should have it handled soon, insha'Allah.
@tame ingot

[median perch]

• sign in ✅
• signup ✅
• google auth ✅
• password reset (in progress)

[ruby heath]

@median perch You are now level 8! :confetti_ball:

[lone spire]

i've been having a very peculiar problem in signing up, where the document gets created in the users collection, yet the function getOrCreateUserDocForEmailSignup throws me an error saying:
AppwriteException: user_unauthorized, The current user is not authorized to perform the requested action. (401)

@median perch could u help me with this

[median perch]

Just make sure to set the correct permissions in Appwrite Console @lone spire

[lone spire]

this should be fine right?

[median perch]

Set these permissions in all collections created in Console after running appwrite_script.js @lone spire

[lone spire]

yea i've done that

[ruby heath]

@lone spire You are now level 5! :confetti_ball:

[lone spire]

im still getting the same error

@median perch

but the document is being created just fine

🥲

[median perch]

Is document security enabled ?

[lone spire]

nope

disabled

[median perch]

enable it and try again

[lone spire]

i did

still not working

also how does enabling document security help in this case

[median perch]

Are you sure that permissions are enabled for all collections , as i was facing a similar problem , while trying to run apppwrite_script but it was only a permissions problem @lone spire

[lone spire]

okay so

I did fix it

by changing the other collections' permissions, it did work

but how does this make sense 🥲

shouldn't the auth functions only be concerned with the perms of the users collection?

is the code performing some read/write operation on some other collection on signing up?

[median perch]

@lone spire That actually makes sense! If the users collection is related to other collections, or if the signup code reads/writes to them (like roles, logs, etc.), then those collections also need proper permissions. That’s probably why it worked after you updated them.

[tame ingot]

Thanks for the update

What about the remaining features ?

[tawny zealot]

Here's the progress

• fetch monuments details ✅
• fetch/edit profile ✅
• bookmarking monuments ✅
• fix appwrite script to include permissions ✅
• post management - create, like, unlike, comment (inProgress)

[tame ingot]

Great ! Thanks for the update,Ayan

Can we open separate issues for each small feature
For example

• upload post
• like/unlike
• comment
• check in (if also broken)
  Etc
  Let’s do our best to get the migration done before the coding period start

[ruby heath]

@tame ingot You are now level 7! :confetti_ball:

[tame ingot]

What do you think about that ?
@tawny zealot @steep bane @median perch

[tawny zealot]

Yeap can be done.
I'm currently working on the upload post feature.

Have fixed some of the bugs in #310. Pls review.

[tame ingot]

Sounds good , so the remaining post management stuff will depend on the upload post fix
So let’s now only focus on these two issues once they are done we can jump to the next

• post upload -> @tawny zealot
• password reset -> @median perch

Please open issues with these specific issue I’ll assign them to both of you and try to make the pr changes only specific to the issue you are addressing

[tawny zealot]

@tame ingot like, comment feature was implementd by @steep bane in a previous PR related to SocialRepository not sure if it's working or not as post upload is not working so we can't verify that. Once I fix post upload, it will be clear and I'll share the situtation.

[median perch]

OK, consider it done insha'Allah

[lone spire]

ig we don't have a checkIns collection so far in the setup script

[tawny zealot]

yes @lone spire and we don't need it. have updated the script and opened a PR. It will be managed in the user collection itself. a separate relationship attribute checkInMonuments List of monuments.

Leveraging appwrite relationship we could implement features of collections like likes, bookmarks, checkins in user and monument collection itself.

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/315

Can you please review latest PR? @tame ingot @balmy star

[median perch]

All done! The Auth module has now been fully migrated to Appwrite. @tame ingot @balmy star

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/316
@tame ingot @balmy star can you review the PR i made

[tame ingot]

I will check all PRs tomorrow and let you know.
Thanks all for your fast responses

[ruby heath]

@tame ingot You are now level 8! :confetti_ball:

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/319
Can you please review latest PR ?
@tame ingot
@balmy star

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/316/
@tame ingot @balmy star can you check the pr again i have provioded the required context and provide detailed steps to reproduce the bug

[lone spire]

@median perch I just tried what u mentioned in this, and for some reason it works completely fine with FirebaseMonumentRepository, and throws me the FailedToRetrieveMonuments error on changing it to AppwriteMonumentRepository

[ruby heath]

@lone spire You are now level 6! :confetti_ball:

[tawny zealot]

hey @lone spire pull the latest code and try again this has been fixed.

[median perch]

Pulling latest code merged and rebase current branch I have raised untill it been merged, this will solve issue insha'Allah

[ruby heath]

@median perch You are now level 9! :confetti_ball:

[lone spire]

wait

i pulled the latest merged code

its still giving me that error

[lone spire]

what should i rebase from

[median perch]

After pulling the latest changing delete the db from appwrite console and try to re run the appwrite setup script again

[tame ingot]

Hey, can someone refactor this service locator file? The excessive use of the cascade operator is making the code messy. Also, we should separate the registration of blocs from repositories to prevent 'Get it' exceptions in the future.

[median perch]

Sure I can do this please assign me this

[tame ingot]

Thanks , I’ll

Hi @everyone
I'll be reviewing some draft proposals and contributions today. Please drop me a DM with a shareable google drive link if you need to review your proposal.

[median perch]

https://github.com/AOSSIE-Org/Monumento/issues/321

[balmy star]

I've reviewed all the proposals that have been submitted for my feedback. Based on my observations, here are some general suggestions for improving your proposals:

• Make the "Detailed Proposal Description" truly detailed: Ensure mentors clearly understand what you are building, how you plan to build it, and how it will function. Your description should provide enough clarity for mentors to grasp your approach to implementing the features. This is the important section of your proposal.

• Structure your weekly timeline effectively: You don’t need to specify tasks for each day, but ensure your timeline is structured in a way that makes it easy for mentors to see what you aim to achieve each week.

• Define features with implementation details: When listing features, describe how you plan to implement them, outlining the complete flow. If a feature is complex, consider defining its logical structure to give mentors better clarity.

• Be realistic about your workload: Avoid suggesting that you’ll complete 10 features in 10 hours, assuming that more features will increase your chances of selection. Instead, be honest about what you can realistically implement and what you hope to learn.

[tawny zealot]

Hey @balmy star @tame ingot
I've fixed the post upload functionality https://github.com/AOSSIE-Org/Monumento/pull/322 Please review.

[median perch]

Are you still facing this issue?
@lone spire

[lone spire]

I'm facing a different issue where on signing up a session for that account is created

Which on trying to login gives an error that a session already exists

[tawny zealot]

hey @lone spire try clearning session from the Appwrite console.

[median perch]

As I mentioned earlier @lone spire :

• Remove all database collections from the Appwrite console.
  Then, run the appwrite_script.js again.

Everything should work fine, insha'Allah.

[lone spire]

thanks, worked

[median perch]

Great 💯

[median perch]

Done ✅

Can you please review latest PR ?
https://github.com/AOSSIE-Org/Monumento/pull/324
@balmy star
@tame ingot

I am ready for the next thing .
can you please assign me this issue ? @balmy star
@tame ingot

https://github.com/AOSSIE-Org/Monumento/issues/325

[honest kraken]

how to propose a problem statement\

can anyone suggest me any problem statement

[steep bane]

@balmy star @tame ingot can you please review my PR ? https://github.com/AOSSIE-Org/Monumento/pull/316

[steep bane]

@tame ingot i have fixed the merge conflict and tested the app on chrome and every feature is working on that platform

[honest kraken]

@balmy star @tame ingot can you please check this new feature

https://github.com/AOSSIE-Org/Monumento/issues/329

[honest kraken]

https://github.com/AOSSIE-Org/Monumento/issues/328

[balmy star]

Maybe consider finding bugs in appwrite migration and fixing them before we can add new features 😉

[steep bane]

@everyone quick heads up

If the 3D view isn't working for you in local development, it's because the current model link has strict CORS settings. So the request gets blocked when you're running the app locally.

Here's a temporary fix:
Change the modelLink in your Firebase or Appwrite to this link:
https://firebasestorage.googleapis.com/v0/b/monumento-277103-41a9c.firebasestorage.app/o/3d%2Fscene (2).glb?alt=media&token=740e5377-2475-4393-a53c-dbe7a0c26bc1
This one has looser CORS settings and should work fine locally.

You can see the 3D model working here:
https://monumento-277103.web.app
Props to Mohsin for deploying it—it’s super helpful.

If you want to make your own Firebase model links work locally, download the model by pasting this link in browser and uploading it to firebase storage, you’ll need to upgrade to the Blaze plan and set up CORS. There’s a good guide here:
https://stackoverflow.com/questions/37760695/firebase-storage-and-access-control-allow-origin

As for Appwrite—you can't upload .glb files to its storage bucket, so that's a limitation to keep in mind.

[ruby heath]

@steep bane You are now level 6! :confetti_ball:

[steep bane]

@balmy star @tame ingot should i create an pull request for this ?

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/335
https://github.com/AOSSIE-Org/Monumento/pull/316
@balmy star @tame ingot can you please review these pr wen you are free ?

[tawny zealot]

Hwy @tame ingot @balmy star Please review this PR https://github.com/AOSSIE-Org/Monumento/pull/327

[ruby heath]

@tawny zealot You are now level 11! :confetti_ball:

[median perch]

Try to remove appwrite console data
And run setup script again, I think this issue not found on latest version of our appwrite-migration branch
@steep bane

[steep bane]

This bug only comes when the user has posted a post in the app with a picture

[tawny zealot]

Hey @steep bane, We can upload .glb files to Appwrite Bucket

[tawny zealot]

agree

[steep bane]

Can we ? Can you please tell me the steps

[tawny zealot]

let's talk over vc

[median perch]

Or if you have an opinion for this
Please provide reproducing steps and screen recording plz
@steep bane

[steep bane]

Ok

[steep bane]

I have provided steps in the pr

[tawny zealot]

have you tried on the latest code

[steep bane]

No

Let me create a different branch and try it out

[tawny zealot]

Yep, Appwrite-branch is currently unstable and is receiving bug fixes every other day, so I request @here to pull the latest code as and when you're developing on it.

[steep bane]

i am unable to like or comment for any post in appwrite branch currently

[median perch]

https://github.com/AOSSIE-Org/Monumento/pull/340

Can you please review latest PR raised ?
@balmy star
@tame ingot

https://github.com/AOSSIE-Org/Monumento/issues/341
I have fixed checkin Functionality issue and iam ready for the next thing
Please assign me this issue .
@balmy star
@tame ingot

[ruby heath]

@median perch You are now level 10! :confetti_ball:

[tame ingot]

Hey@everyone,
I'll be reviewing your PRs and open issues tonight. Please prioritize fixing the migration-related issues, as this is our main focus during this period. I’ll also be giving priority to these PRs during my review and merging process today.

Please don't forget to submit your proposals on the portal before tomorrow.

[ruby heath]

@tame ingot You are now level 9! :confetti_ball:

[median perch]

Quick update on the migration status:

✅ Sign in

✅ Sign up

✅ Google authentication

✅ Password reset

✅ Fetch & bookmark monuments

✅ Fetch & edit profile (minor issue unrelated to Appwrite — can be addressed after migration is complete)

✅ Post upload (thanks to Ayan for fixing this)

✅ Check-in (I've raised PR fixing it yesterday)

♻️ Like/Unlike/Comment on posts (Iin progress I'm working on them RN)

[median perch]

@tame ingot
@balmy star

[tawny zealot]

• Documentation done ✅

[median perch]

If anyone comes across any other issues related to the migration, please let us know so we can add them to the list.

[tame ingot]

Thanks for these updates

[tame ingot]

Yes, please, this is our priority right now.

[steep bane]

improvement in appwrite setup script
https://github.com/AOSSIE-Org/Monumento/pull/348
Ui improvements/fix overflow issues
https://github.com/AOSSIE-Org/Monumento/pull/335
https://github.com/AOSSIE-Org/Monumento/pull/350
@tame ingot @balmy star Can you please review latest PR ?

[tame ingot]

Hey @everyone
We will stop merging new features/enhancments/fixes until we make migration branch stable and merge it into develop

Also please avoid opening PRs without first creating a corresponding issue and getting assigned to it.

This ensures we’re aligned on priorities and helps avoid unnecessary work. It also makes it easier to track who’s working on what.

Thanks @steep bane for your work and effort! I’ll review your latest PR related to the migration. The other PRs will remain pending until the migration is complete.

[ruby heath]

@tame ingot You are now level 10! :confetti_ball:

[steep bane]

ok ma'am i will keep that in mind

[tawny zealot]

Hey @steep bane , regarding pull#348 — I don't think this change is necessary.

The Appwrite script is intended to be executed once before running the app to set up the backend environment. It’s not designed to handle conditional logic like checking if collections already exist. The current approach ensures that the backend is always in the expected state for testing or deployment.

The core issue with your proposed change is that it only creates the collection if it doesn’t exist. This introduces a limitation — if we ever update the script (e.g., add new attributes, indexes, or permissions), and rerun it, those changes won’t reflect unless the old collections are manually deleted from the Appwrite console. This defeats the purpose of having a controlled setup process and could introduce inconsistency.

That said, the error handling and other improvements you’ve made are good, but I strongly disagree with this part of the approach.

Would love to hear your thoughts on this, @median perch .

P.S.apologies if I came off too strongly or offended you in any way — that wasn’t my intention. Just sharing my perspective based on how we've been structuring things so far.

[median perch]

I agree with this, especially regarding the part about missing updates. If the script skips creating a collection just because it already exists, any changes to attributes, indexes, or permissions won’t be applied. That can easily lead to inconsistencies or bugs down the line. It’s much safer to always recreate the collections to keep the setup reliable and up-to-date.

[steep bane]

okay i have closed the PR

[ruby heath]

@steep bane You are now level 7! :confetti_ball:

[tame ingot]

I’ve noticed some of you opened issues and PRs for UI improvements and enhancements .
In this phase what’s really matters is the quality of the contributions not the quantity please keep that in mind

Also DON’T push a PR before being assigned to work on it
This is VERY important

It’s not a matter of the number of PRs but the quality of the contribution and the importance of issue you are fixing

[median perch]

Could you please review the latest PR I just raised?
@balmy star
@tame ingot
https://github.com/AOSSIE-Org/Monumento/pull/362
**for this issue **
https://github.com/AOSSIE-Org/Monumento/issues/341

[steep bane]

https://github.com/AOSSIE-Org/Monumento/pull/364
@tame ingot @balmy star can you please review my latest PR ? related to google sign picture error in using appwrite google authO 2.0

[tawny zealot]

Hey @tame ingot @balmy star I've fixed 3D Model view, which was having bug for appwrite-migration branch. Please review this related PR.
https://github.com/AOSSIE-Org/Monumento/pull/365

[steep bane]

@tame ingot @tired zenith can you please assign me this issue
https://github.com/AOSSIE-Org/Monumento/issues/366

[steep bane]

https://github.com/AOSSIE-Org/Monumento/issues/367
@tame ingot @balmy star can you please assign me this issue

[steep bane]

@tame ingot I have the code ready with me and I can submit the pull request immediately can you please assign me this issue right now https://github.com/AOSSIE-Org/Monumento/issues/367

[tame ingot]

No problem just push the first PR and if it merged without comments I’ll assign the second issue to you if @median perch haven’t already done it

[ruby heath]

@tame ingot You are now level 11! :confetti_ball:

[steep bane]

Hey @tame ingot , just to clarify — When I created issue https://github.com/AOSSIE-Org/Monumento/issues/367 #367 (6 character password) and had the fix ready when I asked for it to be assigned. I was referring to this specific issue when I mentioned the code was ready, not a first one(https://github.com/AOSSIE-Org/Monumento/issues/366). I’ve already submitted a PR for it. Just wanted to make sure there's no confusion — would appreciate it if the contribution could be considered accordingly

as for issue #366 (https://github.com/AOSSIE-Org/Monumento/issues/366) i am already working on it and plan to submit a pull reqest by tommrow evening 19:00 IST

[tame ingot]

Hey @steep bane
Please submit the PR for the assigned issue first

[steep bane]

@balmy star @tame ingot https://github.com/AOSSIE-Org/Monumento/pull/370/ can you please review my pr at your convenience

[steep bane]

@tame ingot @balmy star can you please review my PR which i had submitted last week for appwrite-migration https://github.com/AOSSIE-Org/Monumento/pull/370/ , https://github.com/AOSSIE-Org/Monumento/pull/368

[steep bane]

Hi @tame ingot @balmy star ,
I hope you're both doing well. I just wanted to kindly follow up regarding my message and pull request from last week. I completely understand that you may be occupied with other responsibilities or reviewing GSoC proposals, and I truly appreciate the time and effort you put into maintaining the project.

That said, I haven’t received any updates or feedback in over a week, and I’m unsure about the current status. It would be really helpful if someone could take a moment to review my PR or let me know if anything else is needed from my side. I’d be happy to make any required changes.

Thank you for your time and consideration!

[ruby heath]

@steep bane You are now level 8! :confetti_ball:

[tawny zealot]

Hey @steep bane ,
I'm in a similar situation. Ever since the GSoC submissions, things have gone pretty quiet in the community. I also opened a GitHub issue but haven’t heard back yet. Honestly, just waiting and not knowing the status can be a bit disheartening :'(. It would really help if we could get some kind of update or feedback from the mentors, even if it's just to know where things stand.
@balmy star @tame ingot

[tame ingot]

Hi @tawny zealot @steep bane
Thank you so much for following up and for your patience. We really appreciate your contributions and the effort you've put. Apologies for the delay—things have been a bit busy with GSoC reviews and other ongoing tasks.
We’ll make sure to take a look at your PR as soon as possible. If any changes are needed, we’ll reach out directly. Thanks again for your understanding and for being proactive!

[steep bane]

@everyone did you receive accept or reject mail from [email protected]

i got rejected

[tawny zealot]

same man

[steep bane]

congratulation @median perch

https://summerofcode.withgoogle.com/programs/2025/organizations/aossie

[tame ingot]

Thank you all for your efforts and hard work 🙏
You all did really well, and the choice wasn’t easy. Unfortunately, we had a limitation of only one slot for the project this year.
I truly encourage you to keep contributing, and there's always a chance for next year. Keep pushing forward, you're all doing great 💪
@tawny zealot @steep bane @wary harness

[median perch]

Thanks brooo , for ur kind works ❤️❤️

[vocal kernel]

@median perch (cc: @tame ingot @balmy star), thanks for preparing the mid-term evaluation demo video. It is looking great!

@balmy star @tame ingot @median perch (cc: @bleak bough ), the only remark I have is that it is not clear to me what the long-term strategy for Monumento is and how the new features (AI Trips, Communities) fit into the strategy. What are your thoughts?

[balmy star]

When I proposed the idea of adding AI trips, I planned to gradually steer it toward a platform like TripPlanner AI
but social and open-source. The concept of community would allow anyone to share their itineraries with others and even plan trips collaboratively. Over time, we could expand from focusing solely on monuments to covering every type of destination. This was my long-term strategy for Monumento, as focusing only on tracking monument visits seemed too limited. This is what I had in mind, and I hope it conveys my vision clearly.

cc: @tame ingot @bleak bough

[vocal kernel]

Interesting. I think it is a good strategy.

Right now, the community feature and the AI trip feature seem a bit disconnected from each other (as if Monumento is now 2 (or 3) separate apps in 1). What are the plans (if any), to integrate these two aspects?

There is a natural tension between AI and community in the sense that, if you are getting advice from an AI bot, you don't need to get it from humans from a community and vice-versa.

Which AI service is being used?

What is its pricing?

[vocal kernel]

Figuring out a way to dissolve this tension, so that AI and community cooperate with each other instead of competing with each other, would be very interesting.

(AI is even plagiarizing and violating copyright from people and communities who posted information about trips and destinations on-line.)

Another comment: perhaps the communities feature should be a bit more restricted. For example, it seems strange to allow users to create football communities inside monumento. I expect that lots of spam communities might end up being created.

I am aware that there are many whatsapp groups for digital nomads that seem to be city-based and aimed at connecting digital nomads with locals. (I have participated in one for São Paulo once.) But it is not easy to discover such groups.

If Monumento's communities focused strictly on city-based communities, I think it could be a good niche.

... maybe "region-based" community, to be more general.

Here is a list of digital nomad groups scattered in whatsapp, facebook, ... : https://docs.google.com/spreadsheets/d/1WkCWMMnjqzjLt4whpH-s73vdqdxrOJB9fTnFouStsGk/edit?gid=0#gid=0

[balmy star]

The way I was thinking about integrating this is that we could start by generating itineraries from the monument data we already have. One idea could be that if a user has visited a monument, they can join a community specific to that monument. Right now, the way I imagined verifying visits was through a check-in system that works only if someone is within a 100–200m radius of the monument. It’s definitely not the strongest method, but maybe it’s good enough as a starting point since we already have it implemented.

On the AI vs. community itineraries part, my thought was to let people take any community itinerary and tweak it according to their own plan. For instance, if someone doesn’t want to visit a particular spot on the third day, they could swap it out with another. In that sense, it’s somewhat similar to TripPlanner, which also allows you to start with community itineraries and then adapt them to your needs. But I see this as a starting point, we could refine the balance between AI and community contributions further as we go

For communities, I agree with everything you said. Apart from check-ins, maybe asking people to upload a ticket photo or even a picture near the monument could help in avoiding spam?. Your idea about making them city- or region-based is really good, and I hadn’t thought of it before. At first, I was thinking more about tourist places like for example, if someone’s itinerary has two places, they could join the communities for those two. But I guess city based communities make more sense

[balmy star]

Currently the free plan of gemini

[vocal kernel]

Right now, the way I imagined verifying visits was through a check-in system that works only if someone is within a 100–200m radius of the monument. It’s definitely not the strongest method, but maybe it’s good enough as a starting point since we already have it implemented.

It is good enough for most users, but hackers would probably be able to tweak and fake their mobile's gps coordinates. Or, if we are using a server that receives API requests where the GPS coordinates are plaintext and unsigned, hackers could simply submit API requests with arbitrary GPS coordinates.

... but, anyway, this is better than nothing.

as long as there is no monetary incentive for hackers to fake check-ins, it should be sufficient.

upload a ticket photo or even a picture near the monument could help in avoiding spam?

I think it wouldn't help much.

One idea could be that if a user has visited a monument, they can join a community specific to that monument.

This could be interesting for some users. But, at least for me, it wouldn't be so interesting. I would be interested in having a badge showing that I have been to, let's say, the Eiffel Tower or the Taj Mahal, but I wouldn't be interested in participating in a community with other people who have been to these places, because I know that all sorts of people go there and I wouldn't have much in common with those people.

I think region-based communities, matching people who want to go to a destination with locals from that destination would be more useful. Travelers need things in the destination and locals want to offer things (e.g. places to stay, experiences, ...). It just needs to have moderation, so that there is no spam from locals offering irrelevant things.

[foggy crescent]

Hey everyone, I am Hasan 3rd year CS student, I am currently contributing in Neurotrack and Ell-ena project. I am really interested in contributing to Monumento , this project is really interesting - I am eager to learn from the codebase and help something meaningful to the project.

It would be great if I get some guidance from you all...

[upper skiff]

Is this project still active , pls reply?

[twin lark]

Hi @vocal kernel ,
Hope you're doing well!
I just wanted to check in regarding the project, is it still active, or should contributors hold off for now?
I'm interested in contributing and just wanted to make sure the repo is still being maintained before I proceed.
Thanks!

[vocal kernel]

<@&1075774609032495176>

[chilly frost]

hey hii

[ruby heath]

@chilly frost You are now level 3! :confetti_ball:

[chilly frost]

hey how do i contribute to the Monumento Repo, i am pretty comfortable with Flutter, dart, Appwrite...

[vague otter]

Hello everyone!
I'm Akarsh Kushwaha, a 3rd-year CS student. Excited to join and start contributing to open source!
Looking for good first issues and happy to learn from you all.
I would greatly appreciate any recommendations for "good first issues" or guidance on getting started.

[vague otter]

@vocal kernel How to fix this error

[chilly frost]

hi...

completed setting up monumento on my local device...but some issues are very inactive

@balmy star how shoud i approach in this case??