JLooks like Kyle was busy last night with some dynamic elements + a tips file.
JSome ideas from last night:
J- show a warning when image date > 30 days
JAnd then the tips thing will allow us to dynamically build a collection of built in useful stuff
JI was thinking it might be annoying to show it on every terminal open since I go through a ton a day, maybe a setting showing it only it's changed so we don't get too spammy
BSorry If it wasn’t clear, the thing I built for config only displays a static user-motd
BBut. Maybe we should change the hard coded path to display to be something in /etc (eg, /etc/user-motd) then the stock (from config) script will always work and stuff like @Kyle Gospo did for dynamic tips can run from a second script and overwrite the user-motd file
Jno opinions on design other than we should think about tips. Like should we have them in config so that they hit everybody and the bazzifin add theirs on top or do we leave them decoupled?
JI'm kind of leaning towards keeping them seperate so it's more targetted to each user story but also see the value of having one place in config to do like "warning: there are major shifts happening to foo, check this link" if we ever need it. For things like say, the
just transitionJ(Just spitballing ideas)
KI made the folder generic and the file it picks out of it is at random
KThat way you can continue stacking on more tips as your images get more complicated
KSo a base tip file totally makes sense
Jman this turned out so good. 
BSo… why aren’t we just using the coreos utility if we are reinventing the same thing?
BAnd apologies for not being more in touch with this today. A lot of family stuff.
Jno worries
Jit was actually way more complicated once bob looked into it
Jand it accounts for like, sshing in or not, etc.
Jand ubuntu's was messier
Jso it was just like "can we just cat/glow a markdown file?"
J
JWorth it.
JSO WORTH IT.
J@Kyle Gospo lmk when yours is ready and we'll start a thread
J(in the forum)
Jor feel free to kick it off
KIt's live
J
Jon a fresh vm, interesting
Jbrian did a fresh install and got the real one. I'm just an unreproducable mess today
K"skill issue"
KWeird though, do you have a tips file?
KShould be able to pick apart the shell script
Jit's ok I'm not sweating it, it'll be easier to find all this when the installer is ready
Jactually ...
Bmy email blew up with commits today "thanks Kyle?"
Bin the end, i still haven't seen the final code in bluefin/bazzite... i'm confused if what i built in config was wrong or what?
@j0rge @Kyle Gospo
@j0rge @Kyle Gospo
Band just dealing with more family drama... so not a lot of energy to look at this stuff today
Jdon't even sweat it
Jwe're in chat if you wanna hang tho
JKyle explained to me that we just slap on top of what's in config, so yeah, we needed that. 
JM V P
Jthat was a cool "weekend project" that's basically done and these tips are gonna be awesome
KStill using your base, everything I've done was just markdown formatting
KMuch appreciated
Jand each opening offers a new tip, and we can use markdown in the tips file
Jso like, we can put all sorts of links to docs in there
