Please take this in good faith, as I hope your own post is, but I interpret the thread you're replying to as focusing on the "everyday' part.
Share knowledge? I don't think anyone here is arguing against that in any way (or conversely arguing for hoarding knowledge).
The concern, one I share, is where the sharing has to happen publicly "every day" - so no matter how trivial, useless, niche, overly-specific the tip is (whatever, the list isn't exclusive), someone shares it.
That's the part that's not sharing knowledge for the benefit of others, but rather self-serving. I might even go so far as to say self-serving doesn't even need to be selfish; the person might genuinely believe they're doing good, but even there, self-serving.
TLDR: Share your knowledge, don't make sharing something every day, even when you don't have something valuable to share, your target.
PS - if this note irks anyone (are routine maxxers a thing?), make the goal to learn something every day, then share where appropriate.
> Treating a public channel like ye olde facebok wall? Mildly annoying.
Every team/department/org/whatever should have channels everyone should subscribe to, and channels individuals set up that are optional for everyone. The appropriate way to handle this is for the OP to write a few tips once in a while in the public channel, and if people seem to like it, announce that all future tips will be in that channel.
Even weather was/is comically bad. Ask it anything specific and it would fall over, repeating the broadest, least helpful version of weather data, even if all that data is clearly available in the ios weather app. Specifics on wind, precipitation hourly, etc.
So no, you can't really ask a homepod for the weather either - Homepod's weather was more like a shitty version of sticking your head outside and looking up at the sky.
Wouldn't most users considering or using Forgejo also have considered (or used) self-hosted Gitlab which would have the same opex / security costs (and much higher hardware requirements)?
Finder is indeed frustrating. "Recent" seems like an attempt to fix this without the need to use some giant camera roll?
The (hard) problem is that almost every finder alternative/add-on I've tried is someone else's ideal workflow that still doesn't sit well with me. I find KDE's Dolphin similarly frustrating - for very similar reasons.
Both work marginally better (for me) when used in concert with the quick-find tools like Alfred (or Spotlight) and KRunner. None of these are perfect.
Showerthought: maybe the "find files" interfaces aren't the worst offenders; maybe it's the "place files" workflows that are problematic and we're trying to solve the wrong problem?
If only recent actually worked. I see no rhyme or reason why something gets in recent. I guess finder has to be involved. So often I am working with files between apps, saving and opening and such and the files never appear in recent which defeats the purpose for me.
And then we have the spotlight deamon processes which seem to exist only to burn earth's precious resources.
High quality 500-600w bifacial n panels are between $200-300 in Canada at normal install sizes (12-32). We do lag behind the costs elsewhere, but still nowhere close to $1000 per panel.
Really? That's more expensive than I would've guessed. The US has substantial tariffs, and you can get a pallet of panels for $0.20-$0.30/watt. You can also pay a lot more, but I'm not sure why you would.
To further back this up, just because OSM might be a map's data source, it doesn't mean they use the same rendered vectors or images for the tiles.
I make changes to OSM so they can be propagated to a cycling-specific mapping tool I use (it's a commercial tool with their own custom map layers) - it takes about 3-4 weeks from when a change is made on OSM for it to be incorporated into their data set.
So yeah, it's not as simple as "we all use OSM so we'll just share all our rendered mapping values".
Share knowledge? I don't think anyone here is arguing against that in any way (or conversely arguing for hoarding knowledge).
The concern, one I share, is where the sharing has to happen publicly "every day" - so no matter how trivial, useless, niche, overly-specific the tip is (whatever, the list isn't exclusive), someone shares it.
That's the part that's not sharing knowledge for the benefit of others, but rather self-serving. I might even go so far as to say self-serving doesn't even need to be selfish; the person might genuinely believe they're doing good, but even there, self-serving.
TLDR: Share your knowledge, don't make sharing something every day, even when you don't have something valuable to share, your target.
PS - if this note irks anyone (are routine maxxers a thing?), make the goal to learn something every day, then share where appropriate.
reply