[-] Kissaki@programming.dev 4 points 1 week ago

got it; arse

It would certainly be an issue if you didn't have one

[-] Kissaki@programming.dev 4 points 1 month ago

I'm a bit confused. If you're a Junior dev, don't you have mentors in your team, in your company? They will know the projects and environments of what is needed in that environment.

"give me a specific, clear idea of what skills I might need to have" depends very much on context and goals.

[-] Kissaki@programming.dev 4 points 1 month ago

But did it reach test or production environment yet? Or will it die in development environment.

[-] Kissaki@programming.dev 4 points 1 month ago

Valve is generously providing backing for two critical projects that will have a huge impact on our distribution: a build service infrastructure and a secure signing enclave.

[-] Kissaki@programming.dev 4 points 1 month ago

Damn, that's a long list. Looks like a lot of work to collect and prepare.

I was looking for more of an overview of it and selected them from the headlines:

  1. 2014: Completely broken IndexedDB implementation
  2. 2015: 100vh (100% viewport height) means a different thing in mobile Safari to everywhere else
  3. 2016: with overflow:hidden CSS is scrollable on iOS
  4. 2017: Safari incorrectly blocks localhost as mixed content when accessed from an HTTPS page
  5. 2018: OS 11.2.2 broke WebAssembly
  6. 2018: Safari 11.1 broke MessageChannels
  7. 2019: Audio stops playing when standalone web app is no longer in foreground
  8. 2019: PWA in iOS uses old assets after publishing new servicerWorker/assets
  9. 2020: Add Fullscreen API to iOS (& display fullscreen)
  10. 2021: Safari shipped blob.stream(), crashes with a NULL pointer exception
  11. 2021: Appending an element to the shadow DOM in many cases hard crashes the browser process
  12. 2021: LocalStorage is broken when a page is open in more than one tab
  13. 2021: IndexedDB APIs hangs indefinitely on initial page load
  14. 2021: Fetch request streaming is implemented just enough to pass feature detection, but it doesn't actually work
  15. 2021: IndexedDB API information leaks
  16. 2023: Notifications API: support for the badge, icon, image and tag options
  17. 2024: On-screen keyboard does not show up for installed web apps (PWAs) when focusing a text input of any kind
  18. 2008: Focus events for non-input elements behave differently in Safari to every other browser
  19. 2012: Using border-image with border-style: none is rendered completely wrong
  20. 2014: WebKit doesn't calculate padding-top/-bottom: n% correctly
  21. 2014: Pointer events should allow for device-pixel accuracy
  22. 2017: Support for 120Hz requestAnimationFrame
  23. 2018: Some Fetch requests incorrectly completely skip the service worker
  24. 2020: Safari 14 shipped a broken replaceChildren() method, which caused glitches in Construct.
  25. 2020: When leaving current scope of PWA, back button incorrectly reads "Untitled"
  26. 2020: Safe-area-inset-bottom still set when keyboard appears
  27. 2020: Support for background-attachment: local has suddenly completely disappeared
  28. 2021: IntersectionObserver and ResizeObserver fire in incorrect order
  29. 2021: Mousemove events fire when modifier keys are pressed, even if the mouse isn't moved
  30. 2021: Scrolling in home screen apps incorrectly latches to document
  31. 2022: WebM Opus support is inconsistent in Safari
  32. 2022: Installed web app with viewport-fit cover causes overscroll issues, breaks position fixed and -webkit-fill-available
  33. 2023: iPadOS: Viewport doesn't correctly restore after dismissing software keyboard for installed web apps
  34. 2023: iPadOS: window loses focus when dismissing the keyboard, breaks Page Lifecycle API
  35. 2024: Svh and lvh are incorrect on iOS in third party browsers

DOM query

let a = ''
for (let x of document.querySelectorAll('h3 a[title]')) a += x.title + "\n"
a

[-] Kissaki@programming.dev 4 points 3 months ago

At work, we recently talked about AI. One use case mentioned (by an AI consulting firm, not us or actually suggested for us) was meeting summaries and extracting TODOs from them.

My stance is that AI could be useful for summaries about topics so you can see what topics were being talked about. But I would never trust it with extracting the or all significant points, TODOs, or agreements. You still need humans to do that, and have explicit agreement and confirmation of the list in or after the meeting.

It can also help to transcribe meetings. It could even translate them. Those things can be useful. But summarization should never be considered factual extraction of the significant points. Especially in a business context, or anything else where you actually care about being able to trust information.

I wouldn't [fully] trust it with transforming facts either. It can work where you can spot inaccuracies (long text, lots of context), or where you don't care about them.

Natural language instructions to machine instructions? I'd certainly be careful with that, and want to both contextualize and test-confirm it works well enough for the use case and context.

[-] Kissaki@programming.dev 4 points 3 months ago

the ability to override menu keys is really a long-running flaw in browser UI

They have a reason to do so here though. OP evaded their search box and couldn't find the content. Because it's not fully rendered. Because code files can get big, and rendering them to DOM with inline highlighting and hover actions, sidebar with infos, and interactivity becomes a performance problem. So they implement partial rendering / virtual scrolling.

[-] Kissaki@programming.dev 4 points 4 months ago

I was tempted to disagree, but the Patreon subscription paywalls is a very good point. Are we doing less free work for the public good (or at least accessible to the public), or is it a prevalent niche that's very visible, without influence on those that volunteer work like before?

The thought I had before that was that maybe the creative output changed. People build in Minecraft and VRChat, in hosted platforms. This may be different to before, where mods were separate things and communities.

I still see a lot of voluntary open work. But I'm not confident in assessing it's prevalence or shift.

[-] Kissaki@programming.dev 4 points 4 months ago* (last edited 4 months ago)

It's upcoming, and the time distance is increasing. They still have time.

[-] Kissaki@programming.dev 4 points 4 months ago

Can you search for the search?

[-] Kissaki@programming.dev 4 points 8 months ago

We are beginning a staged dissolution process that will allow our over 600 collectives the time to close or transition their work. Dissolving OCF will take many months, and involves settling all liabilities while spending down all funds in a legally compliant manner.

  1. And it's not sustainable?

Open collective always looked successful, popular, sustainable, professional.

Really unfortunate for those 600. March 15 is very short term.

March 15 is the last day to accept donations. You will have until September 30 to work with us to develop and implement a plan to spend down the money in your fund.

[-] Kissaki@programming.dev 4 points 10 months ago

One time passwords

Forgotten after one use

view more: ‹ prev next ›

Kissaki

joined 1 year ago