mortallywounded

I tried Obsidian for a while and the whole "second brain-thingy" until I watched a video about complex procrastination (basically, using tools like Obsidian as a means of not doing actual work).

https://www.youtube.com/watch?v=baKCC2uTbRc

Can you not "lock down" a smart phone to emergency calls + whitelist of numbers (mom, dad, etc)?

I'd prefer my kids to keep their phone, but only able to contact me during school hours (otherwise the device is as useful as a brick).

ublock origin seems to work fine still

Because Albanians help boost numbers on videos where monitization is viable, thus making the platform look more appealing to advertisers.

Sounds like you have your priorities straight? Do what makes you happy and to hell with everyone (and everything) else.

You don't need to sound interesting or have things to talk about. If you're finding you are not "happy" with what you have, that's another discussion.

I only experience "slow down/freeze up" with Windows and to a lesser extent, Mac based operating systems. I have never felt that way with a Linux install.

Ebiten (Go package) compiles for all OSes, Switch and web via Wasm as well. The binaries are little fat but it's really nice :)

> "those are the people who can't let go of their beloved, outdated stacks"

... said the nextjs/vercel/graphql/whateverishotthisweek developer. Ironically, your stack will be outdated next week.

I suppose you're right-- the feeling was irreplaceable, but I guess the service itself not so much.

The math exercises and lessons for kids has been very helpful preparing my young ones for common-core bullshit.

Irreplaceable, until you're self (/un) employed.

ahem if I was into tinfoil theories, I'd wonder if Cloudflare knew more about the attack =P

Oh? You want that attack to stop? It's going to be big number.

Ouch, if you're using gulp/grunt/browserify or anything that wasn't invented six months ago then you're doomed anyway :)

This is such a common issue with npm and bundler it was an inside joke/meme at every company I worked at.

Person A: "Hey, so I ran bundle update and it's not working."

Person B: "You updated the dependencies? WHY WOULD YOU DO THAT!"

I have considered:

1) Adding a credit card after sign up as part of the flow.

2) Adding a mobile number and verifying via SMS.

I don't particularly want to do either as it's more friction up front for everyone... but seems like it's where it will lead.

My service isn't very expensive (one of the lower ones in the industry).

The origins of these people are often problematic countries (places I couldn't accept a payment from even if I wanted to).

Some of these individuals (~30%?) seem to be coming from legit domains and verify their email but don't appear to be the target audience. They often try to pay without using the service. I believe these people have compromised mail servers and are trying to test stolen credit cards.

I'm not greedy.

I did a fair amount of my master's degree in computer science online. With that being said, it wasn't very easy. The tests were legit. The classes were "pre-recorded" by the instructor, but every year had new recordings. We were able to ask questions in an online forum and/or via messaging with the teacher or the TA.

It felt like my undergraduate studies. It sounds to me like schools have gotten a bit softer and/or your school is really bad.

With that being said, take it for what it is if you don't have any other options. Dive deep into your textbooks, learn as much as you can, look into outside resources, keep on coding. You'll come out better on the other end of it.

A nice story-- I built my own SaaS (in the middle of year seven now). A similar story... I even read Rob Walling's book and even went to a local Microconf.

The numbers grew slowly and have pretty much plateaued. It's my dream job, and I can't imagine going back to work for anyone else.

I do have an existential dread though--- mainly, "what if my revenue goes to zero?" and I constantly think about how to improve the service or build another service on the side.

Though, it's still better than the dread that comes with being employed and potentially laid off.

It's quiet most of the time. The fan comes does come on when it's being worked. The only time it annoys me is when I load up Youtube search results and I scroll fast down the results page. For whatever reason, it gets the CPU going (possibly the autoplay/preview of videos, lack of hardware decoding, etc).

I primarily use it with a USB-C dock and two external monitors, which may contribute to the CPU/graphics load being worked more than usual.

I'm pretty certain Satoshi's identity is known, although not publicly stated and/or confirmed by anyone. I believe a handful of the early developers had very strong suspicion as to who was behind the name, but never pursued a confirmation of it.

My money is on Len [1]. The sheer number of coincidences, crossing of rare skill sets and interests, time, place, penchant of pseudo anonymously publishing things and happened to take his own life <2 months after Satoshi's final gloom-filled message, "I’ve moved on to other things and probably won’t be around in the future".

[1] https://evanhatch.medium.com/len-sassaman-and-satoshi-e483c8...

It's a tale as old as time. The NSA did it as well [1]. "Here's an example implementation with some example random seeds wink wink."

[1] https://www.schneier.com/blog/archives/2007/11/the_strange_s...

I love quitting. I quit most things I start. I wish I didn't-- I'd be far more successful. Life is short and you're lucky to do one thing well, so stop quitting.

I have the Lemur Pro (best for "most people" on the list).

It has been the best Linux-laptop I have ever had. I've been using it for a year and a half now as my daily driver.

Alternative theory, it was simply a mistake.

Party A explains how to send bitcoin to them but used a well known wallet address in their documentation/guide (Satoshi's).

Party B didn't use Party A's address and committed a bad case of copy-pasta.

Is January 5th a day of relevance in Bitcoin's history? Could it be an homage of some kind?

Hopefully not near your home-- when the cartel comes to the GPS coordinates ;p

Pascal programmers never die. They go procedure and don't return.

I get it-- that will enable you to resolve the clash (or at least make it possible to detect and do something about it). However, it does feel messy/ugly when compared to how HTMX is generally portrayed (do some action, an HTML fragment in response). Now, you'll return an HTML fragment and/or an optional head element to merge? It feels a bit yucky, but I understand why it will be done.

A cleaner approach may be leveraging the HX-Trigger response header in some way? I feel like the app version could be specified and if it changes, HTMX would know and could trigger an event that could be specified by the user.

I don't really like either solution.. perhaps the head merging would be more correct, but damn it feels off =/

I'm in love with the idea of making games-- it got me into programming. It's an absolute blast to do.

There's nothing quite like grabbing SDL2 and going HAM for a few days. Some of my fondest memories are with lazy foo's tutorials :)

https://lazyfoo.net/

There's a glaring issue with HTMX and I'm not sure how it can be resolved gracefully. Other related libraries solved this issue already (Turbo and Turbolinks). However, HTMX only returns HTML fragments and doesn't track head changes.

It's not easy to explain.. but imagine if a user loads your webpage. Then the web page loads your assets are loaded (JS, CSS, etc).

Then imagine a new deployment happens that introduces new styles and/or HTML for a given resource.

The page that is loaded in the user's browser does not have the new styles and doesn't know they were updated. If the user interacts with the resource the page styles will break.

This was fixed in Turbo and Turbolinks by introducing "data-turbo-track="true"" to a resource like a CSS sheet. When the server responds with a fresh page the head can be compared and a full reload can happen if the asset was updated.

In HTMX, the page is just broken.

edit:

Currently, you would have to manually hack around this... like long polling for the current app version or returning it in every XHR request and adding a middleware to HTMX to do the check and pop up a "your page is out of date..." message.