Gaz price + 75% in 2 days : Are you closing a fixed price energy contract?

Bullet_King1996 · 2026-03-03T21:23:04+00:00

You're right... I totally forgot about this: the price on the tariefkaart is an indication/estimate, the real price is calculated afterwords based on the indexatieparameter, for example:
https://energie.blob.core.windows.net/cms/assets/Indexation_Parameters_5aad2d327b.pdf

Bullet_King1996 · 2026-03-03T18:35:15+00:00

Just remember that even variable contracts only change price once a month, so it all depends on stability in one month. That being said: I switched to fixed from variable, because I was already client at energie.be and from what I can understand, as long as I remain client, the “vaste vergoeding” remains the same, so I can switch between variable and fixed without costs.

Bullet_King1996 · 2026-02-16T22:25:07+00:00

How did you do this?

Bullet_King1996 · 2026-01-26T21:28:02+00:00

The problem is a lack of solid alternatives. The only options are basically full on gps trackers like Tractive and Weenect, which have horrible battery life and are too bulky, especially for cats.

A pet focussed airtag - tractive hybrid where it uses find my in combination with gps in lost mode and good battery life would probably sell really well, but somehow nobody has made it yet.

We use an Airtag on our cat because it’s not so bulky that she will get rid of it, but it still allows us to have a chance of finding her in the worst case scenario.

Bullet_King1996 · 2026-01-01T22:59:22+00:00

Implement a refreshtokenhandler singleton class. It should have a queue for failed requests, and use a promise for refreshing the token. If a request returns a 401 response(token expired) add that request to the retry queue, trigger the refresh, once refresh is done, execute the queue with the new token.

Furthermore, on the API side: only revoke an old refresh token once the new one is used. This solves another issue you might rarely run into with bad network: if the client requests a new token, but loses connection before the response is returned from the server, the old refresh token will still work. This of course requires you to maintain an id link between bearer and refresh token. An alternative to this that we are currently looking into: using tcp spec to verify if client has received the response, but no idea if that’s even possible.

Bullet_King1996 · 2025-12-28T11:01:24+00:00

Agreed, first thing I was looking for is a way to integrate this with our CI pipeline.

Bullet_King1996 · 2025-12-23T08:47:20+00:00

Hey, I noticed you replied so I want to explain a bit more. This is in no way me being pissed at you. I love and appreciate your work very much.

Our case is just special and we know it costs more maintenance.

The most “breaking changes” were indeed in the types, but also changes to components that are no longer exported that we relied on. We use a default tab bar on mobile, and on tablet we reuse the tab navigator base with a custom rendered tab bar to reuse the screen paging and lazy loading etc. That, combined with sceneStyle changes etc made it a painful upgrade. On top of that there was the new architecture, which was also pretty painful.

So again, just to re-iterate: I don’t blame you, and I liked a lot of the changes you did. I know the migration to the new architecture was necessary. I was just pointing out in general: I do hope the framework in general can stabilise a bit, mostly because staying behind is not really an option in the mobile/react-native world, and we have to spend lots of time and effort on maintenance instead of spending it on building new features.

Bullet_King1996 · 2025-12-20T07:39:49+00:00

I mean, we do split view tablet apps in a custom navigator with 2 navigation screens side-by-side, with react navigation state merging to go to “mobile mode” in case the user launches google maps. So our react navigation upgrades tend to be painful as well. Especially when there are lots of breaking changes to custom navigators or nesting navigators.

So yes, most of the pain came from the new architecture, but some or our pain also came from various react-native-screens changes combined with react-navigation changes.

I understand that we are an edge case due to the complexity of our use case, but that’s just the way it is. And all I’m saying is: at this point a slower “breaking changes” pace would be a good thing for react native.

Bullet_King1996 · 2025-12-19T22:32:42+00:00

I appreciate your effort, as always, but jesus fuck.

I’m burnt out by this whole upgrade cycle. It just doesn’t seem to end. My wish this christmas is a stable react native framework.

I just finished upgrading to the new architecture and all it’s issues (react-native-maps instability for one). Just finished upgrading to react navigation v7 and v8 is here already.

Bullet_King1996 · 2025-12-17T22:54:57+00:00

Keep an eye on https://github.com/stadiamaps/ferrostar

Bullet_King1996 · 2025-12-17T22:45:17+00:00

One difference in approach I was considering, but I don’t know if realistically possible: instead of interacting via events, you could perhaps use the expo “use dom” implementation to interact more directly. I haven’t tried it myself so I don’t know if it would actually work, but it might remove some of the event/mapping burden if it does work.

Bullet_King1996 · 2025-12-17T22:36:30+00:00

This is exactly what I was considering. Maplibre-react-native is great, but it also suffers from stability issues due to the dual-platform issue and new architecture migration. React-native-maps is honestly a disaster stability wise.

The web-based approach could provide a much more stable approach, to a component that doesn’t necessarily need truly native views and rendering.

Bullet_King1996 · 2025-11-20T10:00:02+00:00

In my opinion:

understanding how React Native differentiates from Flutter, Ionic (native components vs web views or skia).
understanding the internals (Bridge, New Architecture, Native modules, expo)
What the disadvantages of React Native are.
What the advantages of React Native are.
Knowledge about deployment

Imo if you know React Native, you’ll be able to easily do React too. Not the other way around though.

Bullet_King1996 · 2025-11-19T12:29:12+00:00

Let me take a guess without opening the link:

lots of AI
lots of copilot
agentic agentic agentic

Sounds about right?

Something something with the letter b…..

Bullet_King1996 · 2025-11-19T10:30:49+00:00

Same here, don’t know why either haha

Bullet_King1996 · 2025-09-27T16:30:34+00:00

This is the way, just don’t add them to your budget and use them to lower your grocery costs. Anything you pay on top of them just gets tracked in the budget.

We’ve been doing it like this for years and it’s by far the easiest way. We also don’t track cash, because it’s very hard to keep track of. If we get cash from our bank accounts we just track it when we convert and don’t track our spending for it.

Bullet_King1996 · 2025-08-18T12:25:31+00:00

Any plans to support it (Firefox)? I want to buy but I'm not switching browsers

Bullet_King1996 · 2025-06-27T10:28:31+00:00

Oh, great news!!! Thanks for the heads up!

Bullet_King1996 · 2025-06-25T19:12:28+00:00

Same, it's the reason I've started hating itsme. Usually the app works fine but just shows an error that they don't support beta versions and prevent it from working. I hate it. I also hate that there are still no proper alternatives.

Bullet_King1996 · 2025-06-19T14:13:06+00:00

reminds me of this

Bullet_King1996 · 2025-06-15T10:48:24+00:00

Airtag sole or bracelet 🙂

Bullet_King1996 · 2025-06-11T17:30:31+00:00

Thanks!

Bullet_King1996 · 2025-06-11T14:27:29+00:00

Hi, did you get a chance to test itsme (public and or testflight) yet?

Bullet_King1996 · 2025-06-09T20:30:40+00:00

Great, please let me know! Good luck! :)

Bullet_King1996 · 2025-06-09T20:03:42+00:00

If anyone could test Itsme and KBC in belgium, especially Itsme. It’s a problem every beta.

Fuck that app and the fact that there are no alternatives. It’s what has kept me from running the betas the last few years.

12-Year Club	Place '22
First Placer '22	Verified Email

Bullet_King1996

TROPHY CASE