beejjorgensen

@beejjorgensen@lemmy.sdf.org

• ⁨Comment⁩ on ⁨Reddit’s getting more popular—and profitable⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  I don’t care what they do as long as they do it over there.

• ⁨Comment⁩ on ⁨Massive E-Learning Platform Udemy Gave Teachers a Gen AI 'Opt-Out Window'. It's Already Over.⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  I switched to in-person teaching a couple years ago and am glad I did. It’s been a challenging time as an instructor finding ways to make sure I’m added value.

• ⁨Comment⁩ on ⁨Youtube has fully blocked Invidious⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Not that; I just write free books on how to write software.

• ⁨Comment⁩ on ⁨OpenFreeMap - a public vector tile server for OpenStreetMap⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Supporting on GitHub. Just a few bucks a month. It won’t take many of us to get to $175/mo.

• ⁨Comment⁩ on ⁨Youtube has fully blocked Invidious⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  I do pony up for other services (not YT Premium because I won’t give Google any money) and support a significant number of creators via Patreon, giving them more money by far than they’d ever see from me from ads. And I’ve spent thousands of hours on my own dime making written content and giving it away for nothing with no ads or tracking. So yes, I agree.

• ⁨Comment⁩ on ⁨Telegram Removes Z-Library Posts ‘Due to Copyright Infringement’.⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  It should never be illegal to link to infringing content in the US. First Amendment should apply if they have any sense.

• ⁨Comment⁩ on ⁨Youtube has fully blocked Invidious⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  We need a competitor badly.

• ⁨Comment⁩ on ⁨Flying through Seattle's hacked airport⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  We were there 6 days ago. Mostly fine except they couldn’t change the monitor at the gate to show the proper destination. I wonder if it was this!

• ⁨Comment⁩ on ⁨Google avoids “link tax” bill with deal to fund California journalism and AI⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  It should never be illegal to link to a thing. To host illegal content, sure, that should be illegal. But making it illegal to say where some illegal thing is located is asking for all kinds of trouble.

• ⁨Comment⁩ on ⁨Google avoids “link tax” bill with deal to fund California journalism and AI⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  I can’t find the link, but I read that some Canadian news organizations were using URL shorteners to post their own news to Facebook to get around the block.

• ⁨Comment⁩ on ⁨Trump promotes family's new crypto platform, 'The Defiant Ones'⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  But the sweaters!

• ⁨Comment⁩ on ⁨Why are so many leaders in tech evil?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  And in politics, too!

• ⁨Comment⁩ on ⁨Apple now sending up to $395 payments to butterfly keyboard MacBook owners - 9to5Mac⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  “Sorry, Tennessee! And Oregon. And Minnesota. And Alabama. And…”

• ⁨Comment⁩ on ⁨Twilio kills off Authy for desktop, forcibly logs out all users⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I switched to Aegis when google authenticator didn’t allow exports. It’s simple and it works.

• How does a car cigarette lighter work?www.lumafield.com ↗
  Submitted ⁨⁨3⁩ ⁨months⁩ ago⁩ to ⁨technology@lemmy.world⁩ | ⁨24⁩ ⁨comments⁩
• ⁨Comment⁩ on ⁨What's the best website to learn and practice SQL?⁩ ⁨⁨11⁩ ⁨months⁩ ago⁩:

  They most definitely do.

• ⁨Comment⁩ on ⁨I wrote a program for my boss. How legal is to to write the program again and make it FOSS?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  You can absolutely write a Star Wars knockoff, though. You just can’t call it that. There’s some gray line in there somewhere.

• ⁨Comment⁩ on ⁨US Question. Will the people that have to wait until 70 to get Social Security ever get what they paid in to it back out before they die since men's life expectancy is only 77 now?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  You can start collecting at 62 and get 70% of your computed payout, which I will be doing.

  The math is too hard for me given inflation and all that, but since social security rarely seems to have enough money, I’d guess they’re still paying out more than they take in…?

• ⁨Comment⁩ on ⁨What are the recommended scripting languages for complex shell scripts beyond bash?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  A shell script can be more concise if you’re doing a lot of shell things. Keeps you from having os.system() all over the place.

  Things like “diff the output of two programs” are just more complex in other languages.

  I love rust, but replacing my shell scripts with rust is not something I would consider doing any more than I’d consider replacing rust with my shell scripts.

• ⁨Comment⁩ on ⁨[Help] why local user.mail overrides global user.mail in git?⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  “The expert has failed more times than the beginner has even tried.” 😊👍

• ⁨Comment⁩ on ⁨"The ultimate SO_LINGER page" - an old article about weird problems when you close TCP connections⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  So the page says:

  And this does in fact happen - even though some of your data was still waiting to be sent, or had been sent but not acknowledged: the kernel can close the whole connection.

  But Stevens says:

  By default, close returns immediately, but if there is any data still remaining in the socket send buffer, the system will try to deliver the data to the peer.

  The SO_LINGER socket option lets us change this default.

  And, referring to the default close behavior:

  We assume that when the client’s data arrives, the server is temporarily busy, so the data is added to the socket receive buffer by its TCP. Similarly, the next segment, the client’s FIN, is also added to the socket receive buffer (in whatever manner the implementation records that a FIN has been received on the connection). But by default, the client’s close returns immediately. As we show in this scenario, the client’s close can return before the server reads the remaining data in its socket receive buffer. Therefore, it is possible for the server host to crash before the server application reads this remaining data, and the client application will never know.

  Also:

  If l_onoff is nonzero and l_linger is zero, TCP aborts the connection when it is closed. That is, TCP discards any data still remaining in the socket send buffer and sends an RST to the peer, not the normal four-packet connection termination sequence.

  I’m having trouble reconciling this with the article’s position that data will be discarded by the sender OS with a plain non-SO_LINGER close().

  I can see how the sender might be blissfully unaware that the receiver program might have crashed after the data had been sent and the connection had been closed, but before the data had arrived at the receiver program. And that’s where some kind of application ACKing mechanism might be in order.

  I can also see that the receiver OS might happily collect the data and shutdown the socket correctly and then the sender app thinks everything is fine, but the receiver app has crashed and will never see the data.

  But neither of those conditions result in the receiver app in the example showing less than 1,000,000 bytes received unless there’s an error.

  What am I missing?

• ⁨Comment⁩ on ⁨So Much for ‘Learn to Code’ - In the age of AI, computer science is no longer the safe major.⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  I hypothesize the failure of AI in this arena will be due to the fact that English is a shit programming language. It can take many times the amount of English to be precise compared to the equivalent computer code.

• ⁨Comment⁩ on ⁨Passkeys are generally available on GitHub⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  What’s the backup login mechanism when you lose your biometric sensor? How do you pair with the new sensor?

• ⁨Comment⁩ on ⁨A question about passwords | characters used in them⁩ ⁨⁨1⁩ ⁨year⁩ ago⁩:

  Every time I find a site like this, I assume the programming is bad and the security is poor. (They don’t know how to sanitize input? They don’t know how to hash passwords?) It’s a good reason to use random passwords on every site for when that one is compromised.