Template-C++ is not C++ after all /s

I would separate concerns. For the scraping, I would dump data as json onto disk. I would consider the folder structure I put them into, whether as individual files, or a JSON document per line in bigger files for grouping. If the website has good URL structure, the path could be useful for speaking author and or id identifiers in folders or files.

Storing json as text is simple. Depending on the amount, storing plain text is wasteful, and simple text compression could significantly reduce storage size. For text-only stories it's unlikely to become significant though, and not compressing makes the scraping process, and potentially validating completeness of scraped data simpler.

I would then keep this data separate from any modifications or prototyping I would do regarding modification or extension of data and presentation/interfacing.

Unless you continuously change you IP I don't see how locking DNS resolution behind a signup would solve it. You only need to resolve once, and then you know the mapping of domain to IP and can use it elsewhere. That mapping doesn't change often for hosted services.

Any wall you build up will also apply to regular users you want to reach.

It can't be the terminal that decides what inhibits and what doesn't. It must be the user or programs themselves.

How would implementing it in the terminal rather than shell look like? As a user choice? I don't see how that's reasonably possible.

Reading the other comments it seems like there's already inhibit commands.

If the shell does not provide a command or alias, or they can't because the inhibit API is system dependent, it's on the user to define. The user could define a fg alias or command, fg for foreground, which executes the command with inhibition.

The follow-up quotes

In your specific case, the problem is your employer is on that list [of sanctioned entities]. If there's been a mistake and your employer isn't on the list, that's the documentation Greg is looking for.

I would consider ~~three~~ four approaches.

1. Commit and push manually and deliberately

I commit changes early and often anyway. I also push regularly, seeing the remote as a safe and remote (as in backup) baseline and reference state.

The question would be: Do I switch when I'm still exploring things in the workspace, without committing when switching or moving away from it, and I would want those on the other PC? Then this would not be enough.

2. Auto-push all local git references into a separate space on the git remote

Git branches are refs, commit pointers, just like other refs are. And they can be put under arbitrary paths. refs/heads/ holds branches. I can replicate and regularly update all my branches under refs/pcreplica/laptop/*. And then on the other PC, list or fetch those, individually, or all of them, regularly automatically, or manually.

git push origin refs/heads/*:refs/pcreplica/laptop/*
git ls-remote
git fetch origin refs/pcreplica/laptop/*:refs/laptop/*

3. Auto-push the/a local branch like you suggested

my concern here would be; is only one branch enough? is only the current branch enough?

4. Remoting into the other system

Are the systems both online? Can I remote into / connect into it when need be?

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

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

git has 17 million options

proof needed /s

I wonder how many it actually is.

It baffles me when people use flex layout when it's clearly visually a grid layout. Nothing here is flexing with varying element sizes and auto-fill-wrap-break of items.

A colleague of mine prefers flex too. But to me, grid is so much more intuitive and simple.

https://css-tricks.com/quick-whats-the-difference-between-flexbox-and-grid/

No readily-compilable project is still a worthwhile barrier. So I don't think it's a bad argument.

If it's about open-source licenses, it typically allows that kind of repackaging. Which is not the case for closed-source/proprietary.

extending the list

• You don't need JavaScript to build web pages
• You don't need JavaScript to publish web pages

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.

600. 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.