[–] 3 points 6 months ago

I would actually go further and say that the law should be that any person that releases a software application, if they want patent protection on that software, they have to submit the source code to some sort of international repository.

And that goes for any update or variation as well. And should the business shut down or cease supporting whatever hardware that software works on, then that source code loses its patent protection and becomes public domain.

  • source
  • parent
  • context
  • [–] 5 points 6 months ago (1 child)

    There needs to be a law that when companies do this, they are required to give a path to root access, so FOSS devs can provide alternative apps, firmware, and OS.

  • source
  • [–] 5 points 6 months ago

    Oh Fuck off.

    You are literally just being a cunt.

    Your anecdotal evidence does not change the fact that thinkpads have been one of the best selling laptop platforms in the world for literal decades.

    Your attitude is "welp you fucked up cause you didn't get what I got and coincidentally fuck you!"

    Gtfo, your assholery serves no purpose.

    Need some help ?? 1
  • source
  • parent
  • context
  • [–] [S] 4 points 7 months ago* (last edited 7 months ago) (2 children)

    Wow, 2026 and you still don’t know about Thinkpads?

    It’s not about getting help. It’s about getting software. But in any case, I don’t think a shitty trend vindicates the bad players on the bandwagon. They should still be called out, named, and shamed. It’s our duty.

  • source
  • parent
  • context
  • [–] 4 points 9 months ago (1 child)

    XTAR PB2SL V2. It's basically a 2 cell lipo charger that doubles as a powerbank. I've got one and it works well. It has a mode that keeps the output "awake" when powering small devices which is handy for electronics projects too. My only complaint is that the batteries are a little too accessible, so I'm hesitant to fly with it.

  • source
  • [–] [S] 1 point 11 months ago* (last edited 11 months ago)

    Another question for you: You’re asking for an app to be created to catalog these sites that would support 802.11b.

    Both those with and those without 802.11b.

    Are you proposing a smartphone app?

    It’s an abstract proposal for an app that runs on a mobile device. A well designed app would run on old and new devices. New devices would have some advantages, like being able to detect 802.11be. So a 2025 device would be able to collect more useful details than a 2018 device.

    I think your “As Far As I Can Tell” is really the key part here. It sounds like you do not have a background in enterprise IT as a number of your points are missing the knowledge that would come with that and lead you to an incorrect conclusion.

    Most public APs are not enterprise deployments. Some public libraries outsource to Cisco, but a vast majority are SOHO routers sitting under the counter of a cafe or bakery. If the Cisco pros have to do considerably more work, I don’t give a shit about that. The app is collecting facts that matter to users. It makes no difference whatsoever to the collection of the relevant characteristics how much labor the Cisco pros are doing in their deployment.

    A public resource should obviously have inclusivety as a goal.

    100% inclusivity isn’t realistic. Its just not possible to design as system with infinite requirements. Sure, YOU are asking for only 802.11b, but if the requirement is 100% inclusivity then someone else can next come along and require IR or some other non-standard or deprecated technology.

    No one said anything about absolutes. Of course it’s absurd to claim that in the absence of absolutes we should not collect inclusivity and availability data. It’s the opposite of what you imply. It is in fact the absence of absolutes that make this app useful.

    Its not elitist if the entire solution is slowed to an unusable speed because the impacts of a single 802.11b user has on the entire network.

    Yes it is elitist if you would then exclude that 802.11b user from service. Even if you have some absurd/bullshit idea that everyone in a cafe needs to stream high-definition video with no buffering, it’s still elitist to exclude those who have 802.11b and a decent buffering mechanism in their app for whatever they are doing.

    It becomes useless to everyone.

    Nonsense.

    I’m not. I’m talking about the IT budgets. There isn’t an infinite amount of money for IT.

    There is no sensible place in the app to give a shit about the budget of the supplier. The app collects facts. One might hope that high budgets will yield high availability and inclusivity which the data would naturally effectively reflect. But in the end that’s incidental -- not a problem for the app.

    Okay so now you’ve just increased the cost of every access point because it has to accommodate a separate radio which didn’t before. This goes back to IT budgets. There are much better uses for that money such as installing more access points in other areas for even greater access for more folks.

    Cheap Asus SOHO routers handle this. Again, the app makes transparent the quality of the deployment. Bad quality deployments are rightfully exposed.

    No, you’re not understanding because you’re missing an IT background. Problems with service generate support calls. Support calls mean staff have to service this calls. This means you either have to grow your support staff, or burden your engineers with more work preventing them from performing more upgrades or improvements elsewhere. Further, these service calls would be something like “my wifi is horribly slow, or drops all the time”, when those are problems of congested spectrum that there’s nothing that can be done about that. You can’t tell your neighbors to get a better shielded microwave. You can’t limit the number of users in a specific area so the spectrum doesn’t get overloaded. So you’d have unhappy users, unhappy engineers, and a whole bunch of money spent that doesn’t accomplish the goal of getting the most people online with the finite budget available to IT.

    If you want to dodge 802.11b deployments because you’re afraid a neighbor will use a leaky microwave oven while you’re trying to access the net, the data generated by the proposed app supports your use case. The same data for finding inclusive APs can be used to find elitist APs.

    I didn’t say server side. I meant client side. If you had created this app where it would be known that users with old out-of-date client hardware would be congregating, a malicious actor would have a field day exploiting them.

    Stop nannying people. Every user has their own use cases and with that implies a security posture and threat model that is right for that individual. Fuck you for trying to dictate to others what their security posture must be without even knowing their use case.

    It’s also naïve to claim “out-of-date client hardware” is inherently too insecure for the task at hand. New software fixes old bugs and brings new bugs. Bugs are exploited by malicious actors. New software is rich in unknown bugs -- the kind of bugs you cannot control for. Old software is rich in known bugs and vulns, the kind that you can control for. This is why wise users do not “chase the shiny” and prefer to deal with the devil they know. It is rightfully the choice of the user in control of their own assets how they want to secure themselves.

  • source
  • parent
  • context
  • [–] 1 point 11 months ago (1 child)

    Another question for you: You're asking for an app to be created to catalog these sites that would support 802.11b. Are you proposing a smartphone app?

    Proactively unticking the 802.11b box requires more maintenance overhead AFAICT.

    I think your "As Far As I Can Tell" is really the key part here. It sounds like you do not have a background in enterprise IT as a number of your points are missing the knowledge that would come with that and lead you to an incorrect conclusion.

    A public resource should obviously have inclusivety as a goal.

    100% inclusivity isn't realistic. Its just not possible to design as system with infinite requirements. Sure, YOU are asking for only 802.11b, but if the requirement is 100% inclusivity then someone else can next come along and require IR or some other non-standard or deprecated technology.

    Marginalising some people because some other ppl have the false perception of better performance is both absurd and elitist.

    Its not elitist if the entire solution is slowed to an unusable speed because the impacts of a single 802.11b user has on the entire network. It becomes useless to everyone.

    It’s wrong to put chronic upgraders with new tech in the “tight budget” category. The tight budget category is for those with old devices.

    I'm not. I'm talking about the IT budgets. There isn't an infinite amount of money for IT.

    That’s not how it works. Different radios get different SSIDs.

    Okay so now you've just increased the cost of every access point because it has to accommodate a separate radio which didn't before. This goes back to IT budgets. There are much better uses for that money such as installing more access points in other areas for even greater access for more folks.

    It’s also really grasping at straws to claim all those people on cordless non-GSM phones are having notable intereference issues. Bluetooth is only used in a <10 meter range (usually much less in practice), so also grasping at straws there.

    No, you're not understanding because you're missing an IT background. Problems with service generate support calls. Support calls mean staff have to service this calls. This means you either have to grow your support staff, or burden your engineers with more work preventing them from performing more upgrades or improvements elsewhere. Further, these service calls would be something like "my wifi is horribly slow, or drops all the time", when those are problems of congested spectrum that there's nothing that can be done about that. You can't tell your neighbors to get a better shielded microwave. You can't limit the number of users in a specific area so the spectrum doesn't get overloaded. So you'd have unhappy users, unhappy engineers, and a whole bunch of money spent that doesn't accomplish the goal of getting the most people online with the finite budget available to IT.

    Citation needed that there is a credible server-side vuln relevant to a public access point.

    I didn't say server side. I meant client side. If you had created this app where it would be known that users with old out-of-date client hardware would be congregating, a malicious actor would have a field day exploiting them.

  • source
  • parent
  • context
  • [–] [S] 1 point 11 months ago* (last edited 11 months ago) (2 children)

    They aren’t usually naïve. Their goal isn’t to support the oldest random gear.

    In that case, the naïvety is in their goal (as opposed tech naïvety). A public resource should obviously have inclusivety as a goal.

    Its to provide a specific good experience for the majority of their users

    Marginalising some people because some other ppl have the false perception of better performance is both absurd and elitist.

    usually on a tight budget

    It’s wrong to put chronic upgraders with new tech in the “tight budget” category. The tight budget category is for those with old devices.

    and with low maintenance overhead.

    Proactively unticking the 802.11b box requires more maintenance overhead AFAICT. You have to make the effort to configure it with less cabability then you have the overhead of answering complaints and user support questions about why Bob cannot see the SSID.

    Accommodating 802.11b is almost never part of the defined requirements.

    Bad requirements.

    The good reason to disabled 802.11b on your access point is that if a device starts talking in 802.11b, most equipment will have the entire SSID slow down to accommodate it.

    That’s not how it works. Different radios get different SSIDs.

    802.11b also rides exclusively on 2.4GHz, a frequency band that is very full these days with things like bluetooth, cordless landline telephones, and even microwave ovens.

    Please find me a microwave oven that does not function because of 802.11b signals in the area. Of course what you want to say is that the oven causes a problem for the 802.11b user, when in fact an 802.11b user will gladly risk that unlikely interference over getting no service at all. 802.11b has error correction, so there is no legit concern of data corruption. It’s also really grasping at straws to claim all those people on cordless non-GSM phones are having notable intereference issues. Bluetooth is only used in a <10 meter range (usually much less in practice), so also grasping at straws there.

    That sounds like a fantastic way to build a database of known vulnerable users to exploit because of use of security vulnerability riddled older devices/OSes.

    Citation needed that there is a credible server-side vuln relevant to a public access point.

    Suppose a public library announces: we support 802.11b (among other standards) and we have no captive portal. Please describe the vuln and threat agent who would exploit it.

  • source
  • parent
  • context
  • [–] 1 point 11 months ago (3 children)

    Copious access points are deployed by naïve admins who are oblivious to the fact that not everyone runs the latest gear.

    They aren't usually naïve. Their goal isn't to support the oldest random gear. Its to provide a specific good experience for the majority of their users, usually on a tight budget, and with low maintenance overhead. Accommodating 802.11b is almost never part of the defined requirements.

    When an 802.11b device cannot see a signal, it’s because some asshat proactively disabled 802.11b.

    The good reason to disabled 802.11b on your access point is that if a device starts talking in 802.11b, most equipment will have the entire SSID slow down to accommodate it. Most folks aren't keen on having their fast wifi session slow to an 11Mbs crawl. 802.11b also rides exclusively on 2.4GHz, a frequency band that is very full these days with things like bluetooth, cordless landline telephones, and even microwave ovens. It can make for a miserable experience that the only cure for is to NOT use the 2.4GHz band, meaning also no 802.11b.

    🔧the fix💾 An app that records SSIDs, their location, and all the detectable exclusivity characteristics.

    That sounds like a fantastic way to build a database of known vulnerable users to exploit because of use of security vulnerability riddled older devices/OSes.

  • source
  • [–] 1 point 1 year ago*

    I think you're misunderstanding me. What I'm saying is literally "go for it", and proposing what I think is the best way of doing it.

    You're free to just start adding internet_access:captive_portal tags with whatever values you want to cafes you've surveyed, as long as you don't break internet_access tags it's fine. OSM tags are folksonomy, after all. I think if you care about it this is the least you can do.

    Getting it on the wiki would be more difficult - it would require a detailed proposal and an RFC. That's good in a way, it would force you to think about different values this key might have, and how consumers might handle it. You should probably also do this, so if others also want to do the same you can agree on which keys and values to use.

    The most difficult part is going to be getting any data consumers to handle the key in any way. Unless you go ahead and make good-quality patches for a lot of apps (and have the energy to push them through), the best you can realistically hope for is for the key to show up in some obscure menu of "other tags", likely not even searchable. This is the main reason why it's going to be pretty much useless for the near future.

    Believe me, I've been on a few cheap trips like that when I was younger. Back then very few cafes even had public WiFi, and despite internet_access key being already defined, the easiest way to find a cafe with internet was to just walk about - almost none of it was mapped. You can expect the same to be true for your proposal for a long, long time - at least a decade or so, even if it gets accepted.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago* (1 child)

    What I mean is that this tag is extremely niche, requires local survey, takes some effort to survey, is not very specific, and probably not useful for most people, even with old phones.

    Most people probably don’t have old phones. But almost everyone who does would benefit. Only those who never need to connect on the go would not benefit. Those with new phones would also benefit if the information has good granularity, which I will explain below.

    Mention of old phones was a human-to-human abstraction. Vulnerable groups of people are being marginalised. The DB would not use the term “old” or “new”.

    What most importantly needs to be captured at the simplest level is:

    • Internet access: null (unknown)
    • Internet access: none (verified)
    • Internet access: discriminatory
    • Internet access: non-discriminatory

    The discriminatory connection can be regarded as such for many different reasons, some deliberate (captive portal w/SMS verify), many incidental (captive portal coded by a JavaScript fanatic with no sense of standards or interoperability).

    It requires quite a bit of technical knowledge to even know what a captive portal is,

    Only if this is a purely manual process. Captive portals are trivial to auto-detect.

    it also requires going inside the establishment, asking for a Wi-Fi password,

    Only if there is a p/w. This would be a minority of cases.

    figuring out if this captive portal can be used with an "older phone" (this is the unspecific bit),

    Non-trivial indeed for anyone with a newer phone. An app could work out what tech is being pushed. But it may be impossible for an app to determine what tech is relevant to passing the captive portal. So accurate granular data would likely rely on manual intervention.

    All this while we still don't have opening_hours for the majority of amenities, and I'd guess the vast majority of POIs worldwide are not mapped at all.

    This is really irrelevant. Volunteers contribute what they want. And rightfully so. Opening hours could be made less labor intensive with an AI app that encodes the hours based on a photo. But in any case, having some type of missing info is no justification for preventing people from adding other missing info.

    What I would propose instead of changing the internet_access key itself, is to define a new key like internet_access:captive_portal, with defined values of

    • yes: a captive portal is there but doesn't require personal info, e.g. one that shows you ads
    • phone_number: requires just a phone number which you can confirm is yours, is a legal requirement in many countries
    • id: requires some form of ID but no phone number, sometimes can be a legal replacement for the phone number
    • no: no captive portal

    This just adds new info instead of changing the already-understood internet_access key,

    I’m not sure why I would be fussy about whether it uses one attribute or another. DB experts would likely and rightfully want to ensure the info is not redundant or having potential for contradiction.

    Captive portals come in countless forms: userid+pw, Tel#, GSM-only # for SMS verification, email, ToS agreement, and any combination of those. What’s important is some captive portals are non-discriminatory (no info required and also does not push JavaScript frills that breaks things).

    If an AP is 802.11b w/out captive portal, that is a trivial case where it’s safe enough to yield a “non-discriminatory” tag.

    But TBH even this is completely impractical and will be useless for the stated purpose.

    Only if you do it wrong.

    Just trying a few different cafes until you find one where the internet works for you is a much better strategy than trusting a stranger to correctly fill in some obscure key.

    Try to step outside of yourself and your own privileged lifestyle and envision yourself in the shoes of marginalised travelers. You land in a foreign city on a cheap day trip. You have ~8-10 hours to experience the city before getting back on the bus or train. You might know you can go to McDonalds to get connected reliably, but you’re failing to exploit effeciently using precious time in a city that has more to offer than you can experience.

    You might decide you want local pancakes, not McDonalds pancakes. There are ~10 places marked as having pancakes. Seven have “Internet”, and are scattered around a 7km area. If you go from one to the other on foot, you can easily blow ~20% of your day on a hunt, and still come up empty-handed. If just one pancake shop has “non-discriminatory Internet”, you can make that your 1st attempt and have a good chance at getting a no-bullshit connection while also getting pancakes.

    But you have to understand that even if you push this through and it appears on the wiki, this is mostly just for fun.

    Helping marginalised people function is more than “just for fun”. Blocking it amounts to being part of the list of problems that force people to upgrade phones and add to the world’s e-waste.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago (2 children)

    You seem to want to oppose bloat.

    No, far from it. I am all in favor of making the map as detailed as possible.

    What I mean is that this tag is extremely niche, requires local survey, takes some effort to survey, is not very specific, and probably not useful for most people, even with old phones.

    It requires quite a bit of technical knowledge to even know what a captive portal is, it also requires going inside the establishment, asking for a Wi-Fi password, connecting to it, figuring out if this captive portal can be used with an "older phone" (this is the unspecific bit), and adding that info to openstreetmap.

    All this while we still don't have opening_hours for the majority of amenities, and I'd guess the vast majority of POIs worldwide are not mapped at all.

    This means it is highly unlikely to be used almost anywhere, and this means in turn that no data consumer will properly support it.

    What I would propose instead of changing the internet_access key itself, is to define a new key like internet_access:captive_portal, with defined values of

    • yes: a captive portal is there but doesn't require personal info, e.g. one that shows you ads
    • phone_number: requires just a phone number which you can confirm is yours, is a legal requirement in many countries
    • id: requires some form of ID but no phone number, sometimes can be a legal replacement for the phone number
    • no: no captive portal

    This just adds new info instead of changing the already-understood internet_access key, it's way more specific than "customers with new phones" (since it is easy to check), and allows you to figure out if you can connect or not in most cases. You can approximate whether you can use wifi with an old phone by checking for internet_access:captive_portal = no, you can see if you need a sim card by checking that internet_access:captive_portal != phone_number, etc.

    But TBH even this is completely impractical and will be useless for the stated purpose. Just trying a few different cafes until you find one where the internet works for you is a much better strategy than trusting a stranger to correctly fill in some obscure key.

    This doesn't mean that I'm against adding something like this; after all, I have mapped all trees in my local park, including species, and regularly map cairns while I'm out hiking. But you have to understand that even if you push this through and it appears on the wiki, this is mostly just for fun.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago (3 children)

    When you are offline in an unfamiliar region, the most important information at your disposal is where you can reliably get online.

    You seem to want to oppose bloat. Internet access is what makes a lean map feasible. It enables you to supplement whatever info is needed. But of course if you are offline, and the map fails to effectively bring you to reliable Internet acess, then everything needs to be in the map because the map is all you have.

    So your stance makes no sense. A lean map requires rich reliable info about Internet access in the very least.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago*

    Captive portals could check the age of the phone by looking at the user agent string in the HTTP headers. I’m not sure how often that happens, but at several cafes my AOS 5 device would detect a captive portal and then simply render a giant red padlock that covers the screen.

    Certainly a majority of the DoS I experience is simply a broken captive portal. The browser renders fewer objects than intended by the web devs, who recklessly assume all browsers are bleeding edge latest that can handle whatever coding frills they deploy. E.g. the screen might say something like “click ‘agree’ to gain access”, but then there is no button, tickbox, or object labeled ‘agree’. A bus or train captive portal will render a nice looking travel-related landscape image, and nothing else. No text. No buttons. Just an image. People with fancy phones would of course get some kind of object they can interact with. One supplier presents an agreement tickbox, but tapping on the box does not cause the box to tick.

    I’m not sure what the red padlocks are about. Maybe the devs know they created a discriminatory shitshow, and they choose the dress up the dysfunctionality by detecting browser age and throw up a red padlock instead of trying.

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago*

    Yeah, it would not be trivial to establish a thorough criteria that covers all variables which mappers would then pay attention to. It would be more sensible to simply have a flag that says “dysfunctional for old phones” and if any device cannot connect due to being too old, it should be sufficient to set the flag.

    There are countless ways incompetent IT folks can fuck up Internet service for the general public. It would be unsurmountable to catalog all such foolish/elitist implementations. But some of the info can be automated. A mapper who is at a location could run a tool that does a wifi scan. The mapper could select the relevant SSID for the establishment, and some basic info could be captured just from that: WEP/WPA/open.. and if open then presence of a captive portal could be auto detected.

    If such an tool were made to improve maps, it could also double as enriching a DB for navigation use (for those who navigate offline and/or refuse Google location tracking).

    Have you tried asking in some osm community?

    No. Thanks for reminding me. I was planning to crosspost there.

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago*

    Indeed GSM is irrelevant because GSM towers cannot relate to any particular business. GSM standards are much less of a problem. When the country decides to abandon LTE, all non-5G phone owners are fucked nationwide.

    It’s a Wi-Fi problem. Captive portals are the biggest problem, and the most obnoxious problem because it’s an artificially created problem as a consequence of incompetence. I only had captive portals in mind when writing the OP, but there are also situations where someone configures an AP to not use 802.11b (for example) and then old hardware does not even see the SSID. My laptop cannot connect at some public libraries for this reason. Then WPA versions /could/ be an issue, I think, but I have not encountered that.

  • source
  • parent
  • context
  • view more: next ›