Oceans of Wisdom

it does not work to deploy to staging while you are doing something else?

bc obviously for the two of you you don't just need to understand the "FE pages that create Stream feedback" but Stream itself

you are going to need to save some high priority biological brain cycles for it

Stream is COMPLICATED

ok let's get to #3!

my suggestion is the following: 1/ Let's ship what I did last night 2/ Please test the couple of other things we did last night 3/ let's get both of your big brains on the Stream feedback thing that is more important than this and also the deployment bus discussion you are having

yes i was thinking to do that but I did not have time. I think it is plausible,

And then please all eyes on this Stream review FE and get it to production at the end of your day so we can start seeing how people use it and improve

So for today, please knock out the easy items above

Beyond the above, this is a repeating oattern, we will need to do this another 20 times for various tech items, I want us to make this as reusable as possible

1. I would like a subwave of Follow The Repo only for Stream feedback as there will be a lot and it will swamp everything else 2. Because it is annoying to switch back and forth between the complex documentation site and coming to a Wave, it needs to be easy to comment from the site 3. The comment box should not be implemented the way v0.01 was implemented, it should be side bar so you can read at the same time 4. The v0.01 is classic codex style chips, cards, architectural abstraction astronaut, needs a bit of clean up to look nicer 5. It should update as the Stream repo changes as we we will be changing multiple times per day 6. As we get closer, we should deploy Stream to test net and we should build in shadow mode the FE for Stream and Museum 1/1 contract to work with the text net contracts and see what we like and don't like 7. Stream is very important, I want to be sure it is right before it is deployed for real to mainnet 8. This means something like an order of magnitude more network testing commenting discussion before we "go" - this PR is the beginning of that

Here are the things that need work, review and so on

2. It is the most complex NFT contract we have made by far 3. The contract embeds a lot of complex technical decisions but also design decisions on a variety of topics 4. Before we finalize, audit, etc, we need to get a lot of eyes on it, a lot of commentary on it, a lot of rounds of not just me, but anyone here with Solidity experience, the whole dev team but also the artists and collectors even for topics like how features and behavior work 5. We need to get the feedback before we deploy the contract not afterward :slightly_smiling_face: 6. Because this is the case, I have built a whole section of the website to describe the contract and to allow people to give feedback on it

1, Stream contract is starting to get close to being ready

The goal for this one is the following

https://github.com/6529-Collections/6529seize-frontend/pull/3475

https://staging.6529.io/reviews/6529-stream

Now the big and important one, those above are your appetizers for today

A bit of security hardening pls check

https://github.com/6529-Collections/6529seize-frontend/pull/3458

This is more straightforward than the above - once it lands, please give it a test with lots of etherscan URL types and make any relevant improvements

https://github.com/6529-Collections/6529seize-frontend/pull/3464

7/ Think, for example. why we don't notify someone that their subscription is running low

6/ Let's get these out, polished, etc and then there will be more to do. this needs a lot of work

5/ The above is a continuation of a general theme that there is no a proper hierarchy of concern on site. subscriptions which is arguably the most important network strength topic remains deprioritized vs dozens of less important things

4/ If you are on automatic subs, it should be clear when your sub runs out, when you are getting low, green status should turn to yellow and then to red

3/ Even when subscription is 0 and you are going to subscribe, the subscribe page has no visual hierarchy, call to action etc

2/ there should be a chip, status, etc on the home page of the profile

1/ subscriptions are hidden too deep on the profile

I renewed the subscription for two family members last night and had the following observations

https://github.com/6529-Collections/6529seize-frontend/pull/3476

https://github.com/6529-Collections/6529seize-backend/pull/1839

Needs careful testing etc, but otherwise please get it out today

We need to use the proper standard for SIWE otherwise Rabby and maybe other wallets throw a scary looking (but pointless) warning

please review and ship this

https://github.com/6529-Collections/6529seize-backend/pull/1838

@[prxt0] @[GelatoGenesis]

gm all

This week is Team Stream week. By tomorrow morning or ok let's say EOD, I should have up on the site a detailed feedback mechanism for the current status of the Stream contract that I have been working on the last few weeks. This is needed both for Stream and for Museum/Keys and Gates so it is the main blocker which is why I have taken it on. I will be back tomorrow with a lot more detail, but note that this week you will have to put your big brain hat on

Just posted this in dive bar

This week is Team Stream week. By tomorrow morning or ok let's say EOD, I should have up on the site a detailed feedback mechanism for the current status of the Stream contract that I have been working on the last few weeks. This is needed both for Stream and for Museum/Keys and Gates so it is the main blocker which is why I have taken it on. I will be back tomorrow with a lot more detail, but note that this week you will have to put your big brain hat on

just posted this in maybe bar

This week is Team Stream week. By tomorrow morning or ok let's say EOD, I should have up on the site a detailed feedback mechanism for the current status of the Stream contract that I have been working on the last few weeks. This is needed both for Stream and for Museum/Keys and Gates so it is the main blocker which is why I have taken it on. I will be back tomorrow with a lot more detail, but note that this week you will have to put your big brain hat on

look in principle we want this to end up in production, we are not doing it for our health, why don't you read the last few hours of this chat and check how the Gelato Deployment Bus works and decide how to handle it, in like with @[GelatoGenesis]'s approach but in any case we want to run the merge to staging to prod pipeline

welcome to the future my friend!

you can take deployment instructions from any one of us too; but I think anyway we are supposed to use the deployment bus

he he he, I will sort it out don't worry

yes this is ok, the bots were not understanding; we are fine

the Real Boss (tm) has shown up to the chat!

it is resolved - they were being dumb