Blog
¶ 1 Leave a comment on paragraph 1 0 Do not delete this page. Page content is generated with a custom template.
¶ 1 Leave a comment on paragraph 1 0 Do not delete this page. Page content is generated with a custom template.
Posted in | Comments Off on Blog
The recent flood showed how reliable electricity, alternative connectivity infrastructure and community network remains crucial at the times of crisis. In addition digital literacy and affordable connectivity should be given priority during crisis.
A concise opening could be: Digital and Internet resilience involves maintaining essential communication both in normal conditions and during crises. It also depends on people’s ability to obtain timely, reliable information, use secure digital services, and exercise their rights without surveillance or exclusion.
Australia’s minimum-age restrictions and proposed digital duty of care should be distinguished. The restrictions concern accounts on specified age-restricted platforms, rather than all social media use. We could describe the duty of care as proposed legislation with a date. Official information records its introduction to Parliament in October 2026, while account restrictions took effect on 10 December 2025 (https://www.infrastructure.gov.au/media-communications/internet/online-safety/digital-duty-care).
The Asian Digital Safety Accord is described as a proposal. We should perhaps identify it as a proposal presented by a named contributor (?) to avoid implying regional endorsement or adoption.
The India-Australia comparison oversimplifies Aadhaar by discussing fingerprint and iris recognition without mentioning other authentication options. Aadhaar also supports face and OTP authentication (https://uidai.gov.in/ml/authentication).
IPv6, RPKI and DNSSEC are grouped together as protections whose benefits arise only with widespread adoption. Could be technically misleading. IPv6 is an addressing/network protocol; RPKI and DNSSEC address different security problems. We can separate their functions and avoid suggesting that partial deployment has no benefit. RPKI-based route-origin validation, for example, supports routing decisions on participating networks (https://www.rfc-editor.org/rfc/rfc7115).
The EU AI Act exclusion is broadly described correctly, but needs precision. It concerns systems insofar as used exclusively for military, defence, or national security purposes; mixed-purpose situations require more care.
An accurate sentence would be:
The EU AI Act excludes AI systems insofar as they are supplied or used exclusively for military, defence, or national-security purposes.
A military connection does not automatically exclude every use of a system. If it is also supplied or used for civilian purposes, the civilian application can fall within the Act.
For example, using an AI system for civilian hospital services is different from using it exclusively for military operations (eur-lex.europa.eu).
The wording suggests that military AI operates without enforceable international rules. This is too broad. International humanitarian law already applies to AI used in armed conflict. We can distinguish existing legal obligations from proposals for additional, AI-specific rules. The International Committee of the Red Cross (ICRC) makes this distinction explicitly ( https://www.icrc.org/en/article/faq-artificial-intelligence-in-military-domain).
The claim that most AI systems are built and controlled outside Asia-Pacific is unsupported as written. “AI systems” also covers far more than major generative AI platforms. The underlying concern holds true however that underrepresented communities often have limited influence over AI development and governance.
Website content © APrIGF Document Platform 2026. All rights reserved.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gat_gtag_UA_1450632_51 | 1 minute | Set by Google to distinguish users. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Source: https://comment.rigf.asia/blog/
Comments
Comments are closed
0 Comments on the whole Page
0 Comments on paragraph 1