> If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
That section (and similar in section 6d) is not about the written offer of source code. The written offer of source code is instead covered in section 6c.
> c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.
So according to the legal theory expressed in this thread so far, nobody can sue anybody and there's no obligation to provide source code. The copyright holder couldn't sue because the license was followed (an offer was provided) and the end user couldn't sue because the offer doesn't have to be followed up on.
Or, instead of theorycrafting reasons why it shouldn't work, you could "just" sue them and see if the judge agrees.
> Trusting LaTeX to automatically distribute tables and figures produces not-very-readable documents with tables and figures interrupting content (e.g. page 12).
The positioning of the table on page 12 is completely inline with how tables/figures are placed in books and academic figures. The rule is that all displayed tables/figures should either be placed at the top or bottom of a page. Ideally, they should be placed on the same page as they are first mentioned in the text, but if this is not possible, it is acceptable to push them to subsequent pages.
Interestingly, the author did manually specify `[ht!]` options for the table, and not for some other tables further in the chapter.
Personally I'm most excited about "Don’t look up: There are sensitive internal links in the clear on GEO satellites" with Nadia Heninger & Annie Dai. Harald Welte's "ISDN + POTS Telephony at Congress and Camp" covers how they're doing telephone infrastructure at congress/conference itself, and will surely be interesting too:
> Just like at this very event (39C3), the last few years a small group of volunteers has delpoyed and operated legacy telephony networks for ISDN (digital) and POTS (analog) services at CCC-camp2023 and 38C3. Anyone on-site can obtain subscriber lines (POTS, ISDN BRI or PRI service) and use them for a variety of services, including telephony, fax machines, modem dial-up into BBSs as well as dial-up internet access and video telephony.
Some of the more "celebrityish" talks tend to be popular by reputation, but content is often reused a lot, e.g. "10 years of Dieselgate" kind of falls into that. Watched the original, and the followup, and I think also the followup-followup, eventually it's worth checking out new topics instead, even though the presenters could not be faulted in any way.
When I was a prof, I used to get a lot of emails. My system was that every few hours I would go through all new emails in my inbox and archive all of them in the following fashion
- Some emails required a one line immediate response. I did that.
- Some emails required a longer reply. I tagged them (in Thunderbird) as ToDo and archived them.
- Some emails had information I would need at a later meeting. Tagged as TempInfo and archived.
- Most emails were read once and archived.
Now, inbox is zeroed. Next, can attack items in ToDo one by one, and untag them, so the ToDo list is always short. Similarly, as soon as the relevant meeting finished, untag TempInfo emails.
Now, I work somewhere where Slack is used, resulting in an endless deluge of messages that cannot be controlled.
This is not true for batteries at all. Just take a look at [1]. Many of these battery chemistries are in wide use. Batteries have several performance metrics: total storage, peak/avg power, round-trip efficiency, lifetime, capex, opex,etc. The relative value of these metrics is different for different applications, so we end up with many different types of batteries being used.
Grid level batteries have another very important metric. The actual possibility of buying a particular types of batteries from friendly nations. Simpler technologies like this CO2 battery have a huge advantage here.
Of course it's true for batteries. There's a huge number of potential battery types, most of which never make it out of the lab, never mind to market. Most on your list there are in are in tiny niches.
To steelman the point you're making: perhaps the short term storage niche will fracture into smaller niches, in which different technologies could coexist. This also happens in ecology. For example, in one simple experiment with bacteria, it was found two species coexisted, but on closer examination it was found one species persisted in the top of the flasks, the other in the bottom.
> Every time I've used as a CAD GUI program I would get to this point where I would need to alter a single dimension by 0.25mm and realize that _all_ of my fastener holes, cutouts, etc have to be nudged with the keyboard or mouse to accommodate it.
I am just starting to learn CAD and FreeCAD - also dabbled a bit in OpenSCAD. But I do know that FreeCAD has Spreadsheets [1] and Configuration Tables [2] which allows you to define your model parameterically and changes values as needed.
It’s a fantastic feature and works really well, my problem is I can never invest the required time to learn the interface. It all falls apart when I need to switch modes to move something or whatever. With scad can usually knock whatever I want together pretty quickly without having to relearn how to use the tool.
Spreadsheets are really slow in FreeCAD. I'd suggest you look into Varsets [0] if you don't need some of the fancier capabilities that spreadsheets provide.
Yes, VarSets are definitely better (more granular dependency recalculations).
The little-known Configuration Tables aspect of Spreadsheets is absolutely worth using, though, and has no equivalent in the VarSets scheme at this point. Once you get that set up it is great fun.
The thing is, in cold places, it is possible for the temperature to remain consistently cold for several days on end, day and night. In hot places, even if day time temperatures approach 50 degrees, at night the temperature will almost certainly be below 35 degrees. So you can always go out at night and be fairly comfortable temperature wise.
> If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.
Similar clauses in Sec 6.
[1] https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html
reply