Would love to have seen OpenPilot form Comma on this list to how it compared.

I could never get hardware accelerated video working with Firefox on my Linux laptop, and Google Meet (used for work) doesn’t work well ( but I guess I blame Google for that).

From the downvotes it seems like many people might be this:

Just out of curiosity, since I’m also considering bonds, what is “close to retirement” enough to consider non insignificant bod allocation?

Thanks for the input! I’ve been thinking that’d I’d probably just stick to index funds and avoid (for now) individual companies. My financial advisor does do individual companies (to fit the allocation targets), and does do tax loss harvesting, but I think that might be a bit complicated for my initial attempts.

I had thought about doing something like S&P 500 fund + some set of small and medium cap index funds, rather than trying to identify individual companies that fit into “large/mid/small cap & industry spread”, but even in those broad realms there’s lots of “index 500” funds and lots of “medium/small cap” index funds, how do I figure out which ones to buy and how to compare them?

I would love a suggestion for a ups that could tolerate running off my generator when the power is out for extended periods, anyone have a decently priced recommendation?

I use cloud flare DNS and it has support for dynamic IPs, my current setup is through a plug-in in my PFSense router

I want to preface this by saying that I really don’t know anything about Lemmy, but I can see where subscriptions are managed by the subscribers servers in a federated situation: the community’s server might not even know who is subscribed to it since the subscribers server might be responsible for pulling data.

But any individual subscribers server would know about other users on that server that are subscribed to that community

Paperless-ng (or ngx, but I don’t run that flavor)

I’m not opposed to operators trying to make money, if some server brings some feature that I find valuable, I won’t begrudge them trying to make money off it. I think the hopeful thing with federation is that when one feels that an individual server is being abusive or doesn’t like their monetization approach or is unhappy for some other reason they have the choice to go elsewhere. Competition is good.

Yeah I agree, but for us this would mean like 30 containers. We’ve tried several times to have some kind of flexible setup where devs could choose which parts to run, but that got complicated with all the various permutations of the containers and devs needing different setups in different situations.

It just became a lot to try and manage/support

Thanks for all of the suggestions!

Right now our guidance is that each developer is given a namespace and a helm chart to install and the wording is such that developers wouldn’t think of it as an ephemeral resource (ie. people have their helm installation up for months, and periodically upgrade it).

It would be nice to have user’s do a fresh install each time they “start” working, and have some way to automatically remove helm installations after a time period, but we do have times where it’s nice to have a longer-lived env because you’d working within some accumulated state.

Maybe there’s something to automatically scaling down workloads on a cadence or after a certain time period, but it would be challenging to figure out the triggers for that.