I'm working on a #design update of my site based on new.css. It's available as an alternate stylesheet, so if you want to check it out and you're using a browser that supports it, you can apply the New.css Styles stylesheet. When I'm happy with where it's at, I'll probably just switch the two stylesheets, so the current one sill still be available as an alternate.
How to spice up your blog posts with minimal effort.
I don't have a static site, but I'm going to try using some of these tips. I'd love to play around with art direction and animations on my site. I always love the look of sites like this, but don't know how to go about it on my own site. I'm working on a small design update of my site already and the CSS custom properties tip was already something I was thinking about. So, I'll start there and see how having those variables allows me to modify different posts.
Ok, so my #webmentions should be good to go now. I still wanna work on their display and fix my processing a bit, but I shouldn't be missing them anymore.
Bleh. I had the #webmentions route configured like my internal routes, so it was requiring a CSRF token. Should be fixed now.
But apparently I'm not displaying them correctly so still some work to do here.
Ah, dang :( Looks like my site isn't receiving #webmentions right now. If you want to reach me, my #fediverse account is up top and my email address is zack at tilde dot team.
Great read! I like the idea at the end of providing different experiences based on the client. I might give that a try on my own site.
I've seen vendor
Accept headers before, but never seen any detail on the format. Is the
application/vnd.*+json just a convention or is it standardized somewhere?
This is really disappointing. One of the main benefits of PWAs was how they could replace the need for native apps in some situations. I thought this was the start of getting rid of Electron apps. I don't understand how Mozilla makes these decisions. 😢😠
Wow. Another really disappointing move from #Mozilla. They're removing the bare-bones alpha version of desktop #PWA support from #Firefox. According to one of their team members, they have no plans to support PWAs on desktop anytime soon.
They're also so happy when Fortnite rips off another game (which is always a game made by a much smaller team). It pivoted to battle royale when PUBG was getting big, now it's ripping off Among Us and they celebrate its innovation. Epic is using the Facebook strategy for a gaming platform and games pundits are loving it.
It's really disappointing that a prevailing take on the Cyberpunk fiasco is that gamers need to give developers/publishers a break and stop making a fuss. They want to take away game ownership, make you buy a new platform every few years, make dev teams crunch, etc. But when a game comes out riddled with bugs and people complain about it, they say no software is bug free, learn to live with it or people don't really want refunds, they just like to complain. Gaming journalists/pundits never want to hold publishers or developers accountable.
I'm starting The Collapsing Empire by John Scalzi. I really liked his Old Man's War series, so I'm looking forward to this one. I'm on chapter two and getting some Dune vibes with an interplanetary empire controlled by a balance of political and religious parties and mercantile houses in a feudal system.
I know when people spend years making something artistic, they pour themselves into it and want it to succeed regardless of how they feel about the process. So, it's kind of sad that the ruined launch is a depressing finale to years of hard work for the team, but I wonder if game publishers/developers will finally realize that crunch doesn't work.