• Releasing Things From My Back Catalog

    “As some of you may know, I recently acquired the publishing rights to and original copies of my entire back catalog of writing, music, and some other miscellaneous projects. When I acquired them, I ordered them all to be taken offline and returned to me. Now that they’re all under one umbrella–my own, as part of 2492 Creations–I’m excited to announce that I will begin publishing certain items contained within that expansive vault under the new name. This move gives me full control over all of the items, and not a third party.

    Excited to share the first release from the back catalog with you soon.

    Slade”

    Labels:

  • Tim Sweeney, CEO of Epic Games, announced on Twitter this morning that the company had been approved by Apple to operate Epic Games Store and Fortnite in the EU, as the Digital Markets Act compliance deadline nears. The company will be bringing the game back to iOS in the EU’s member countries as a result, along with its own app store.


  • Reported by VGC and corroborated by Eurogamer today: the successor to the Switch, which was originally slated for launch in late 2024, will now reportedly launch in Q1 2025 (so around February-March territory) with Nintendo telling third party developers and publishers the new date. Important to note that the new reported release window is still located within the same fiscal year.

    I’m also able to corroborate these reports through my sources as well.


  • It’s official: Google has released the first Developer Preview of Android 15 (V). Currently, Android V will require a Pixel 6 or later, Pixel Fold, or Pixel Tablet to install (basically any device with a Tensor chip). This means Pixel 5/5a and earlier are no longer supported.

    If you want to learn more about what’s new in this update, 9to5Google has a running guide here.


  • Apple Confirms No Web Apps in EU

    From Apple:

    The iOS system has traditionally provided support for Home Screen web apps by building directly on WebKit and its security architecture. That integration means Home Screen web apps are managed to align with the security and privacy model for native apps on iOS, including isolation of storage and enforcement of system prompts to access privacy impacting capabilities on a per-site basis.

    […] And so, to comply with the DMA’s requirements, we had to remove the Home Screen web apps feature in the EU.

    EU users will be able to continue accessing websites directly from their Home Screen through a bookmark with minimal impact to their functionality.

    It’s official, users in the EU can no longer have Home Screen web apps on iOS in the EU. Apple says this is to comply with the DMA’s requirements, however as a web developer, I don’t quite see how this is anything but malicious noncompliance. The company says there is low adoption of these web apps, but that’s not entirely true, either, if you look anywhere online. Not to mention this change breaks a lot of web apps.

    It’s a bad move meant to create hardship for their own users. It’s really sad to see.


  • Previously, I announced following Slade’s Corner‘s leave from Substack that this site runs on Beauregard, a content management system (and alternative to the Substack platform) that I’ve been building from scratch since the whole, er, situation blew up over there. Since then, I’ve built so many features into the site: native Cloudflare integration, linklog support, autoposting to Mastodon (and derivatives), and even native Cloudinary support for super fast image hosting!

    Beauregard is the successor to BeauCMS, which itself was based on WordPress 6.0 and 6.1. It was born out of wanting something less clunky, more fluid. Thus, it’s a more mature content management system, one that is modern, written from the ground-up in native PHP, JavaScript, and HTML, but still fluidly compatible with WordPress’s fancy Gutenberg editor, along with its blocks, plugins, and themes. Beauregard isn’t WordPress. It’s literally brand-new code underneath!

    There’s a lot on the roadmap for Beauregard. Paid subscription support (to have the ability migrate my friends still on Substack off at some point), native email support, among other things. But a question I’ve been getting a lot is “Will you be opening this up to the public?” Honestly, thinking long and hard about it, the answer’s no. There are a few reasons:

    • Running something like that for more than a few people I trust is expensive. Server hardware is expensive and while my point of presence being in DC now helps, it’s still costly. Beauregard is lightweight enough that I won’t kill a server or two with it, but it’s still a big piece of software.
    • Beauregard just wouldn’t be cost-effective or make sense for most people. I’m really looking for people who love writing to the same degree that I do–I’m talking essays, articles, that sort of thing–and want to make some money off of it. For some of my friends, the platform makes sense, and that’s why they have access.
    • Setting up Beauregard is a very manual and time-consuming process. I still have to go in and install each new instance fresh manually. It got to the point where I had to write a script to automate most of the setup for testing on my Mac because it was so time-consuming. To go public, I’d have to streamline that process significantly, potentially even figure out how to make that bodged-but-somehow-working script work at-scale, and I just can’t be arsed. (I learned the word “bodge” from Tom Scott. Because of course I did.)
    • Even if I could somehow resolve all those concerns, I’d need to make a lot money off Beauregard, too, when scaling the platform up to potentially hundreds of accounts for any of this to make sense. I’d need to make more than enough to cover development costs, hosting costs, equipment costs, contractual obligations, and more. I couldn’t afford to run at a loss. I’m a self-taught developer who learned through many thousands of hours of Google-fu and StackOverflow. I just don’t think it’d be good if I was the only one building this for so many people.

    To be clear, I wish I could make it make sense and build a side business out of it–but I’d be way out of my comfort zone and burning myself out in the process. I just don’t know how to make it work. That said, I plan to onboard friends onto the platform. I can do a few people that I know–that’s manageable. That’s what will happen.

    I’m sorry if that’s not the answer some were looking for. I wish I could offer Beauregard to everyone. It’s a huge passion project of mine and it’s absolutely brilliant! I love what I’ve done with it! This post is being composed and displayed to you by it, for God’s sake! But again it’s a niche piece of internet software, and I just don’t see any way I could make it profitable at that scale. I also just don’t want to deal with licensing crap. So we’re just not doing that either.

    Thanks for understanding, though. If it changes, I’ll let you know–but I think this is the final decision: Beauregard shall remain a friends-only accessible and usable project from now until the end of time!


  • John Gruber writes (emphasis mine):

    At the end, he makes the case that each new generation of computing devices has an open alternative and a closed one from Apple. (It’s interesting to think that these rivalries might be best thought of not as closed-vs.-open, but as Apple-vs.-the-rest-of-the-industry.) I’m not quite sure where he’s going with that, though, because I don’t really see how my Quest 3 is any more “open” than my Vision Pro. Are they going to license the OS to other headset makers?

    The Quest system software is Android at its core, with Meta’s software running on top. Quest lets you connect to a PC and use it as a VR headset for it, install whatever app you want, whereas Apple locks it down tightly to their ecosystem. Their app marketplace, their rules. I think that’s more so what Zuck was getting at there: Meta simply isn’t keeping things as tight with their platform like Apple is. There are rules and restrictions, of course, even Android itself has them–but they’re not aggressive about it.

    As for your question itself, Meta could probably license the OS to other headset makers within the scope of Android’s open-source license, but I doubt they will. There are a lot of potential issues with that and Meta has a lot of proprietary stuff running on top of what is, again, essentially Android.

    I think what we’re likely going to see is the walls coming down even further than they already are on Meta’s side. They already have the price advantage with their own product line, so I don’t really see why they wouldn’t want to open things up even further.


  • There’s some new emoji, of course, but most of the new changes in iOS 17.4 Beta 3 — which was seeded to Public Beta testers today, and Developers on the Developer Beta track not long before that — are EU-specific.

    From MacRumors:

    The iOS 17.4 […] [beta] introduce a whole slew of changes for users in the European Union, allowing for alternative app stores and alternative payment methods.

    There are new options for choosing a default browser, NFC has been opened up to banks and other financial institutions, and browsers aren’t mandated to use WebKit.

    None of those features are coming to the US or any other territories besides EU member countries, though.

    However, Stolen Device Protection, new emoji, and transcripts in Apple Podcasts are included worldwide, so there’s that. My guess is most of the engineering efforts are on EU DMA compliance and iOS 18 now… Apple’s WWDC is imminent (June), and they usually have things ready to go by mid-to-late April/early May.


  • NBC News reports that a mass shooting took the life of 1, and injured as many as 15 people, today in Kansas City as the Chiefs and fans came together to celebrate their Super Bowl LVIII (58) win. At this point, I feel like a broken record each time we have a mass shooting in our country. It’s heartbreaking and it cannot keep happening.

    I am praying for the victims, their family and friends: my heart is with and aches deeply for them. 

    To my House Representative Elise Stefanik and my State’s Senators, who I will be writing about this issue later, it’s time to stop with the political theatre and do something. Congress must act. Enough is enough.

    Slade

    Labels:

  • In “Twitter is really creepy” news, this happened. To be honest, I’m not sure how they get away with this. They’re not supposed to be allowed to pull from your web history or anything if you have the inferred identity and analytics permissions stuff turned off. My guess is that, like many things at Twitter, that feature is broken. Probably intentionally. And even if it wasn’t intentional, it’s not like they’d be willing to fix it: they don’t really have the manpower to do so.

    Sigh. I hate that website.