Agreed; wish the default filter was "newly available" since that includes all 3 major browsers (Chrome/Edge, Safari, Firefox) but still includes new stuff that isn't "baseline" yet.
I was honestly surprised at how much older hardware is even in the newer SF Symbols library. When I saw my first iPod in there, I couldn't help but shout it out in my app... https://eph.me/pt-easter-egg.jpg
Agreed. It doesn't seem like a long-term solution, but it is the best way we have _right now_ to visit consequences on people/orgs that enabled the tragedy. If our society sees everything in cost/benefit, then increasing the costs of actions that lead to tragedies like this is one of the best things we can do.
Yeah, this seems like a clear-cut "We want justice, not money" decision. We don't know how much the families gave up (could be a little, could be significant), but whatever it was was the difference between Infowars remaining what it is or utterly destroying Infowars' credibility.
Because now the Wikipedia entry is going to say "parody site" at the top.
For the last five years, I've been working on a project called Smolblog. This is my vision for getting away from the problems with social media as we know it and building a better, more sustainable future. Submitted here for discussion.
To play on how every engineer is different, OP is excited about PHP because of a framework, while I'm having more fun than I've ever had explicitly _not_ using a framework!
(I am using the PSR standard interfaces[1], which means I can sub in any number of different libraries for different pieces of infrastructure. Including Laravel's. :D)
I literally just wrote a script to handle my Markdown->PDF workflow: https://github.com/oddevan/periodical "Finished" it today and then saw this article. :/
Location: South Carolina, USA
Remote: Yes
Willing to relocate: No
Technologies: PHP, Ruby, React, Svelte, Swift
Résumé/CV: https://eph.me/
Email: 'me' at domain above
> It would allow you to maintain a proprietary product with proprietary features that you don't release under the AGPL and use my code within that product.
As much as I can say "everything in my version is AGPL; this is just for _other_ companies" I don't know that there's a way to _legally_ guarantee it that wouldn't be easily circumventable, at least not without rendering the idea useless in one way or another.
So yeah, thanks for the insight, I really appreciate it!
Out of curiosity (since I'm pursuing an AGPL/proprietary dual-license), how would you consider a CLA that explicitly tied my right to sell the proprietary license to releasing under the AGPL?
> Smolblog shall be entitled to make Your Contributions available under a proprietary license provided Smolblog also makes Your Contributions available to the public under the terms of the GNU Affero General Public License version 3 or later.
