- tap “Options” under “1 photo selected” top of sheet.
The first choice there is:
Format:
[√] Automatic
[] Current
[] Most Compatible
Choose Automatic for the best format for the destination or Current to prevent file format conversions. Photos and videos may convert to JPEG, PNG, and H.264 formats if you choose Most Compatible.
Most Compatible will put a jpeg on Drive for example, I just verified myself.
I wouldn’t kneecap a OS project I wish to be adopted by licensing it GPL. Look at glibc which basically can’t practically support static linking.
You make any of your OS standard libraries GPL and they need to suck to use and can’t statically link your code without being forced to also be licensed GPL.
WRT kneecapping, history has shown that companies will bleed the commons dry and they need to be legally strong-armed into contributing back to the free software projects they make their fortunes off of.
Virality might suit the ego, but it doesn't make for a healthy project when its primary users are parasitic.
> history has shown that companies will bleed the commons dry and they need to be legally strong-armed into contributing back to the free software projects they make their fortunes off of.
Software is not a scarce good. Let companies use free software without contributing back as much as they wish; it doesn't affect others in the least. There is no bleeding of the commons here, because even if companies take as much as they can without giving back, it doesn't reduce the resources available for others.
Software is rarely finished, and development has real costs.
When that development gets silo'ed away in proprietary systems, that is potential development lost upstream. If that happens enough, upstream becomes starved and anemic, and with forks only living on in silos.
Apple, for example, has made trillions of dollars off of FreeBSD. To this day, FreeBSD still does not have a modern WiFi or Bluetooth stack.
Meanwhile, AMD, Intel, Microsoft, and even Apple, etc have full-time engineering roles and teams dedicated to upstreaming their improvements to Linux. And there are paid engineers at these companies that ensure WiFi and Bluetooth work on Linux.
Companies do worse than bleeding of the commons: lock down weak-licensed software and lock in users and devices. It totally reduces users ability to benefit from FOSS and reduces funding for developers.
Not literally no signal/service, right? More likely “I have a few bars but data doesn’t seem to work… calls often won’t initiate unless 911?” thing you get when there’s too many devices connecting to an overburdened tower, in a network that needs more cells or something, and QoS/qci says no?
If it’s a population center someone would probably have put up a tower on their land ll
Come to Munich, go into any of the large old buildings, the central stairwells usually are phone dead zones. Truly dead.
Or try to go and hike in the Alps. Shit service, but as soon as you walk into Austrian territory, you'll suddenly have service.
Or try taking a train from Munich to, say, Landshut. You'll lose signal about 5 minutes after the train passes through the outskirts of Feldmoching.
Or try driving a car on the A8 highway to Salzburg in Austria. You'll lose signal about 5-10 minutes after passing Holzkirchen.
Or try taking a train from Passau to Wels in Austria. Passau is directly near the border. You will have a shit service right until the train passes the national border and Austrian towers take over.
The reason isn't technical. The Passau and Alps example shows it - identical geography, identical mountainous areas with about zero population... but wildly different attitudes in regulation.
> If it’s a population center someone would probably have put up a tower on their land ll
Here, you get death threats if you even propose putting up a tower on your land [1], in the UK nutjobs set a 5G tower ablaze [2].
I stand corrected. I didn’t realize you could be a MIMBY for cell towers and also not currently have service.
Any organized resistance I’ve witnessed myself in the US has been something like an HOA saying no not tucked right here where our home values could take a hit or a view obstructed, please put it down the street or … anywhere else.
But if you had no cell service and your call dropped as you backed out of your garage or you tried to sell your house and the buyers phones suddenly had no service or they couldn’t get on the Internet at the open house, that’d feel like pretty concerning missing infrastructure.
> I don’t think anti-5G wackos have dented a thing.
They have, at least here in Germany. We have a shitload of what we call "weiße Flecken", zones with zero service, of about the size of half of Schleswig-Holstein [1]. While a lot of these is in forests and mountainous areas, the zones in settlements are mostly due to the whackos and their organized campaigns.
I have no phone signal in my village, a few miles from a major town. I have to use WiFi calling to talk on the phone. Our local politician campaigns against it, it is such an issue. Especially since analogue phone lines are due to be turned off soon. We still have a working red phone box though!
I travel around a bit in the area and blackspots are very common
In the context of “cheap mobile data devices are widely accessible” I don’t think the distinction matters. If you’re relying on your £1 sim to trigger your solar battery charger and it doesn’t, then it doesn’t matter if you technically had signal or not.
How did you save me a click? Those bits were in this article. The guy that located the original report saved me some time.
You could only save somebody time if they skipped the content and started doing comments on HN anyhow, but that’s not all the information either, just a couple key points.
Are you me? I always go back and get it on a next try, and maybe also like tried to bail when I saw it was the wrong card after double side buttoning, which maybe means I need to reset the state of the payment screen, but then need to wait, double click again, change it the right way, wait for the glorious beep…
The parent poster is not making a legal statement. They copied/pasted the first line of the Readme. I made the clarification that the note is a legal disclaimer, not s technical requirement, so people, including the parent poster, are not confused.
The standard screen was 80 by 25. There were two addresses you needed to know 0xb000 for monochrome displays and 0xb800 for color. For monochrome you could just blast characters/attributes to the address and everything looked great. For color you had to add a little bit of assembly so writes didn't happen when the monitor was doing certain things (or else you would get some flickering). The little hacks were all well known.
Then you could build your own 'windowing' system by just maintaining separate screen buffers and having a little bit of code to combine for buffers when writing the actual hardware.
In the early days everyone code was synchronous and code would start listening for keyboard events and react and repaint in a very ad hoc fashion. Mouses made things a bit more complicated as you needed to maintain a persistent model of the UI to process their events.
So the UI code was simple and easy to work on, but you had to squeeze these programs into tiny memory footprints so you would spend a lot of time trying to find more memory. One of the bigger projects I worked on had a memory manager that relocated blocks to create contiguous space but since there was no OS support for things that like the code was actually updating pointer in the heap and stack - which was a great source of complicated bugs. Whoa onto anyone that tried to use a linked lists in such an environment.
But yeah, it was a fun time.
Unless the program specifically allowed for it, you couldn’t change the size (video mode, really) without exiting and restarting the program after changing modes on the DOS prompt.
Remember, the video hardware rendered text mode full-screen, and it had to be reconfigured to change to a different number of lines and columns. Only specific sizes were supported.
You called an "interrupt," which was basically a system call. That changed a bunch of timing registers within the video hardware. For a long time you basically could only do 40, 80 columns of text and 25, 43, or 50 lines. With some trickery you could get the video hardware to output 90 columns and with even more trickery you could get 60 rows.
If you made a custom font you could also have more diversity in the number of rows too but this was rarely done.
Eventually different text modes became available with higher resolution video cards and monitors. 132 columns of text were common but there were others.
There were a bunch of predefined modes in the video BIOS, and with a little bit of assembler you'd issue an interrupt (a system call really) which would change the video mode. Then as the parent comment said, you could write to video memory directly and your writes would either be interpreted as ASCII character/attribute pairs in a text mode, or colour palette indices in a graphical mode.
Most games at that time used mode 13h which was 320x200 with 8-bits per pixel which therefore indexed into a 256-colour palette (which could itself be redefined on the fly via reading from and writing to a couple of special registers - allowing for easy colour-cycling effects that were popular at that time). Here's a list of the modes: https://www.minuszerodegrees.net/video/bios_video_modes.htm
It ran the DOS text screen in VGA graphics mode, with soft-loaded fonts, but this also permitted all kinds of extra modes -- iff your DOS apps supported them. Some just read the screen dimensions and worked, some didn't.
I’m referring to this:
- select something in Photos, then Share.
- tap “Options” under “1 photo selected” top of sheet.
The first choice there is:
Format:
[√] Automatic
[] Current
[] Most Compatible
Choose Automatic for the best format for the destination or Current to prevent file format conversions. Photos and videos may convert to JPEG, PNG, and H.264 formats if you choose Most Compatible.
Most Compatible will put a jpeg on Drive for example, I just verified myself.
reply