Reader

The iPhone 14's MagSafe wireless charging delivers the full 15W magnetic experience — the snap-on alignment, the fast wireless speeds, and the accessory ecosystem that makes the cable-free life viable as the primary charging mode. Setting it up well requires the stand decisions, the case awareness, and the speed expectations set honestly. Here's the iPhone 14 MagSafe guide — the setup, the speeds, and the daily routine.

The MagSafe Setup Components

The wireless charging kit for the iPhone 14. The certified charger: the MagSafe or Qi2-certified stand or pad — the certification guaranteeing the magnetic alignment and the full 15W delivery; the uncertified “magnetic” accessories varying in both. The stand forms: the flat puck for the desk drawer, the stand for the nightstand's clock-and-display mode, the folding travel versions — the form factors serving the placement scenarios. The power source: the 20W+ USB-C adapter feeding the MagSafe charger — the wireless speed's ceiling set by the adapter, the certified pairings stating their requirements. The case factor: the MagSafe-pattern cases preserving the magnet and the charging; the thick cases attenuating both — the case being part of the charging system. The notification integration: the iOS charging indicators and the optimized-charging feature managing the overnight cycle — the phone's intelligence completing the hardware's delivery. The components' summary: certified charger, adequate adapter, MagSafe-pattern case — the three pieces of the wireless setup.

The Speeds and the Real-Life Expectations

The wireless performance set honestly. The 15W delivery: the full magnetic wireless speed — the phone reaching roughly 50% in an hour, the full charge in two-to-three hours depending on the conditions and the case. The heat variable: the wireless charging's warmth throttling the speeds in the warm environments — the summer nightstands and the sun-lit desks seeing slower charges; the thermal management being automatic but visible. The case thickness effects: the MagSafe-pattern cases charging at full speed; the thick or non-aligned cases dropping to the 7.5W Qi rates — the case choice being a speed choice. The overnight irrelevance: the speed differences mattering only in the hurry moments — the overnight stand charging fully regardless of the 7.5 or 15W rates. The hybrid routine: the MagSafe for the overnight and the desk, the 20W wired for the hurry moments — the two-mode charging that most iPhone 14 households settle into. The expectations' summary: the MagSafe's 15W is the wireless speed's practical ceiling — set up certified, used sensibly, and compared fairly against the wired alternative.

The Daily Routine and the Buying List

The MagSafe life's practical assembly. The nightstand setup: the certified stand at the bedside — the phone snapping on at bedtime, the optimized charging managing the overnight, the alarm display greeting the morning. The desk option: the second stand at the workspace — the top-ups during the meetings and the calls; the two-stand households never thinking about charge levels. The travel piece: the folding magnetic charger packing the nightstand into the bag — the travel routine preserved. The power bank option: the magnetic bank for the mobile top-ups — the untethered charging layer for the long days out. The buying list ranked: the certified stand first (the nightly routine's centerpiece), the 20W adapter second (the wall feed), the magnetic bank third (the mobile layer) — the total kit under the price of one wired fast-charging setup of old. The routine's summary: the stands placed where the phone lives, the certification guaranteed, and the charging happening by placement rather than intention.

Conclusion

The iPhone 14's MagSafe charging setup is the wireless life done properly: the certified stand delivering the full 15W with magnetic alignment, the case and the adapter preserving the speeds, the overnight optimization managing the chemistry, and the travel pieces extending the routine beyond the bedroom. Set up certified, place the stands where the phone lives, and the wireless mode becomes the primary — with the cable waiting for the hurry moments. The MagSafe options and their comparisons live in this charging guide, and the same charger roundup covers the stands, the banks, and the adapters that complete the wireless setup.

FAQ

How fast does MagSafe charge the iPhone 14? The certified MagSafe chargers deliver 15W — reaching roughly 50% in an hour and full in two-to-three hours depending on conditions. The heat and the case thickness affect the speeds; the optimized overnight charging makes the duration irrelevant for the bedtime routine.

Do I need a MagSafe case for wireless charging? For the full magnetic experience, yes — the MagSafe-pattern case aligns the charging and holds the accessories; regular cases charge at reduced wireless rates or weaken the magnetic hold. The bare phone works perfectly with the MagSafe charger's magnets.

Is MagSafe charging bad for the iPhone 14's battery? No — the battery management governs the chemistry identically for wireless and wired, with the optimized overnight charging protecting the longevity. The wireless mode's warmth is managed by the certified accessories; the health tracked in the Battery settings either way.

I recently came across a new platform while browsing, and I was surprised by how smooth and fast the overall experience feels compared to others I've tried before, especially in terms of loading speed and usability

https://5999betbook.com

https://bplwinbook.com

https://87kbetbook.com

https://8777bdtbook.com

https://jeetwinbook.com

https://baji777book.com

https://139.144.111.43/o5999betm4vqi9/5999bet-reference

https://blog.martron.me/f5999betg3lf6e/5999bet-reference

https://blog.gcn.sh/n5999bet23z9zo/5999bet-reference

https://blog.katamari.social/l5999beth0k6xf/5999bet-reference

https://139.59.35.73/l5999betvjs117/5999bet-reference

In case you've ever wondered about what's equivalent between US and UK chocolate, here's a guide. I have eaten chocolate extensively in both countries and so can hopefully enlighten anyone who is curious. I'm sure more will come to me later at which point I shall update.

Cadbury's <–> Hersheys

There's several Cadbury's brands available in the US, such as Dairy Milk, Caramel and Fruit & Nut. However, if you look at the wrapper, you'll discover that they are manufactured under license by Hershey's and they've made sure to give it their distinct “tastes completely inedible” flavour to it. It's worth trying once because they have also faithfully reproduced the Cadbury's flavour in there, so it really is quite disgusting.

You can find imported Cadbury's bars in some stores and on Amazon in the US but some of them (like the above Dairy Milk/etc.) can be harder to find as Hersheys sues importers trying to get around their inedible filth.

Hersheys itself

No UK counterpart, it's such bad chocolate that I don't really consider it an edible food, it's more of a decorative wax. I find it offensively bad.

Mars <–> Milky Way

For whatever reason, the sort of thing you'd consider a Mars bar in the UK (nougat with caramel on top) is a Milky Way in the US. They're very approximately the same, but the US Milky Way is a bit bigger, and softer nougat. My dad notes “they're how Mars bars used to be”.

Occasionally you can buy Mars bars in the US, I don't know why.

Milky Way <–> Three Muskateers

The Milky Way in the UK is just a small bar of fluff. In the US the Three Muskateers is a huge bar of fluff, and the fluff is heavier. It seems they never put it through the “this is actually a health food” marketing attempt Mars did in the UK so it remains a giant bar of nougat. Similar to the Milky Way Mars Bars, my dad also notes “this is how Milky Ways used to be”.

Three Muskateers Truffle Crisp

For a time in the US Mars sold this strange bar, which was kind of like a Twix in that it was two fingers each of which contained a crunchy thing with a soft thing on top, all wrapped in chocolate, but instead of biscuit the crunchy part was a toffee similar to the type used in Cadbury's Crunchies, and the soft part was nougat instead of caramel. These were also marketed as a “health food” by implying they were low calorie as is Mars' tradition but they were cancelled shortly after being introduced, which is a shame as they were very tasty.

Maltesers <–> ???

For some reason Maltesers aren't generally available in the US. Sometimes you'll find them (in huge buckets) in Costco and if you get vouchers from Mars corporate they'll have the Maltesers logo on them amongst the other well known brands, so I'm really not sure what's going on.

There's a few things that look like Maltesers like Milk Duds but they all taste terrible.

Galaxy <–> Dove

This one's easy – Dove chocolate is just Galaxy chocolate, though the latter is slightly more greasy for some reason. They even use the same font in their packaging, though “promises” are more of a thing in the US. Available with caramel inside/etc. just the same, though I think the caramel may also be better in the US, Galaxy Caramel caramel is a bit thin.

Minstrels

Not available in the US, they're like giant M&Ms. M&Ms themselves are obviously available in both countries though in the US they're made with high fructose corn syrup and last I checked the UK versions were not, so I assume that just makes the US version worse in some occult way.

## Easter chocolate

Why won't it correctly format the above header? Ah well.

Easter eggs

Americans don't really “get” easter eggs, which is a huge oversight. Instead they do stuff like buy little reusable cardboard eggs and fill them with random (often bad) chocolate promises and such. Easter eggs are objectively better.

I did see an easter egg in one of those big “excess inventory” shops like Marshalls, but it was clearly a “novelty”. They also had a giant chocolate American football around superbowl season. I assume the chocolate quality of these was extremely low.

Hershey's also sometimes sells a chocolate easter egg, using Cadbury's branding, but as usual it's inedible.

Cadbury's Creme Eggs/Mini Eggs

Hershey's also make these under license. They taste terrible and are nothing like the UK versions beyond the vague concept of “some kind of shell with some kind of filling”. They're somewhat easy to recognise as even the packaging is kind of sad and weird compared to Cadbury's UK graphic design.

So it's been about ten years since I last posted on this thing, guess I should give it another shot 😛

My #web server hosts a bunch of websites, and I've been watching crawlers scan it for a while. Some of them are pretty mysterious (“Thinkbot” indeed? And it suggests you block its IP while using a decently large IP range), others are obvious (ChatGPT, Google's non-search user agents).

I certainly don't want to encourage LLMs and “AI” (and I hate calling it that, it's nothing of the sort) so I took a very basic attempt at blocking it, by finding a blog post of someone else doing the exact same thing as a starting point.

At this point I'll give a small warning – the list I started with included common scripting language user agents like the ones used by Python and Go. At first glance this makes sense, since some bots will indeed be written with those and not bother setting a custom one, but on the other hand there's plenty of legitimate apps that do the same. The one it took me three months to notice was BlueSky, which uses go and yet my PDS-based account still “worked”, it's just that all the posts I made during that time disappeared into the ether (they're still in the PDS's database but you'll never see them visiting bsky.app). So don't do that!

So I had a bunch of useragents blocked, and nginx will respond 418 I'm a teapot. I add more user agents as I see them appear (e.g. the aforementioned Thinkbot) but I notice that the crawlers are hugely preferring an issue tracker I have installed on one site. My assumption is that they've been programmed to prefer forum-like web apps in the hope that they'll have more “human” content with less LLM pollution.

To support this theory I've noticed a number of smaller but active forums, still using more oldschool (better, as they're more reserved with things like DHTML infinite scrolling) forum software, all started using Cloudflare around the same time, regularly challenging users to the point that posts were often getting lost as Cloudflare apparently has no provisions to save POSTs they decide to interrupt. It's interesting since some of these forums are very anti-big-#internet and looking for a web 1.0 experience, and so are pretty anti-Cloudflare other than the need for anti-bot protection.

Sadly, I'm not really sure what the solution is. Since they're targetting such specific subsets it does feel like there might be an opportunity to poison the well, but it'd need to be in such a way that's transparent to the real users.

When I was young, my dad encouraged me to learn to #program. He sat me down with various computers, which had BASIC (Sinclair Research BASIC in the ZX Spectrum is quite an experience to program - its symbols are tokenised so each single keystroke can type an entire command, with a bunch of modifier keys) or maybe some ancient versions of Turbo Pascal on an IBM XT.

While trying to make platform games, point and click adventure games, text adventure games, simple windowing systems and trying to get some sounds out of Soundblaster-compatible cards on my old 286, I was always interested in the idea of the development of an actual OS. My dad had told me about how #DOS was a layer between the hardware and the software, and had shown me Sun Sparcstations running X-Windows at his work, as well as Windows 3.1, so I was aware of the existence of all these different systems, even though I couldn't get to use many of them.

In addition to this, my dad worked as an electronics engineer for some time, so I was also exposed to 8-bit #microcontrollers, random hardware and a general interest in electronics. This made things like low level drivers even more interesting, so it's no surprise that I'd spend time thinking about what my own OS might look like, sketching random little windows and things. Of course, 12 year old me didn't really appreciate the complexity in a modern OS!

Saying that, hobby OS development has become a popular pastime amongst software engineers – the existence of websites like osdev.org, /r/osdev, the educational xv6 and the many OS projects on Github show that it's something plenty of people are interested in.

So, as the years have gone by, I've still had the notion, but didn't really do much. The more I learned about OS development and software in general, the more I knew was required, whilst still not really getting started. I had particular concerns about things like virtual memory, where you need to be able to manipulate your page tables from within the linear world of memory as defined by your page tables, which is just mind bending when you're first starting out. After a while of thinking about it though, I found things started to fall into place, and if you take it one step at a time, things start to work.

For my OS, I have some ideas I want to play with:

• Avoid process-oriented computing Most operating systems bundle applications together, which generally include everything up from an OS interface level up to their UI. I want a data and/or task-oriented OS, where smaller components are tied together to perform everyday, and unusual, tasks, resulting in more code reuse, more powerful problem solving for end users even without programming and providing for distributing tasks over multiple machines on the network.
• Micro-kernel as much as possible These components can be drivers or pure userspace tasks, but from an API perspective, they should look the same. As much as possible will be in userspace to ensure maximum stability – and if a task dies, components can attempt to recover by restarting the task (and in the case of network distributed processing, moving those tasks onto another machine)
• No “compatibility layers” Though it'll probably put off new users, I don't intend to have any sort of standard libraries to make file, device or UI access work. Though these are useful for running existing applications, I want my OS to be something different, with APIs to match. The only exceptions will be to allow self-hosting, so there will be shims to allow things like gcc to work that aren't part of the OS, but the toolset.
• Encrypted, versioned file system Speaks for itself! Everyone deserves privacy, and to be able to recover their files.
• Built in shell is an object-oriented BASIC system This ties in to my belief that computing is for everyone – anybody should be able to write a little app, a script or whatever they need to perform their basic tasks at home and work. In the '80s most home computers had built in BASIC, allowing people to tinker, but computing has been slowly moving away from this. I'd like my OS to bring this flexibility back, allowing people to use the computer to its full potential and self educate.

I have other ideas, but those are the “big” ones for now!

So, I've decided to start a blog. I might never update it, much like my LiveJournal, but I felt the site needed some refreshing since I haven't had time to update it in recent years.

To begin with, I've uploaded my original internal 360 controller driver source to github. A few people have asked for this over the years, but I already had it in internal source control (it's old enough that it was still in Subversion even though I'd moved over to git) and I was always afraid of actually getting around to it. However, I bit the bullet and there it goes! I do still intend to work on it, but it's hard to find time.

Other than that, I always have some random project I'm thinking about, so perhaps I can blog about that. Recently I've been playing with hobby OS development, so there's plenty of drama there.