<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>OpenAGPS</title>
    <subtitle>OpenAGPS project site</subtitle>
    <link rel="self" type="application/atom+xml" href="https://openagps.net/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://openagps.net"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-11-07T00:00:00+00:00</updated>
    <id>https://openagps.net/atom.xml</id>
    <entry xml:lang="en">
        <title>Initial NLnet funding Phase is Over</title>
        <published>2026-11-07T00:00:00+00:00</published>
        <updated>2026-11-07T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-5/"/>
        <id>https://openagps.net/blog/update-5/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-5/">&lt;p&gt;Hi everyone! Another update from us:&lt;/p&gt;
&lt;p&gt;Since the last blog post a lot of things have happened. Sorry for the silence here, however, there was a lot of activity on &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps&quot;&gt;GitLab&lt;/a&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/mohs8421&quot;&gt;Thomas Kosel&lt;/a&gt; from Fre(i)e Software GmbH joined the team, bringing a considerable amount of Rust expertise to the table:
&lt;ul&gt;
&lt;li&gt;Thomas started implementing a &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/porygon&quot;&gt;SUPL server&lt;/a&gt; (yes, we returned back to asn.1, so our SUPL implementation &lt;em&gt;will&lt;/em&gt; be compatible with existing SUPL services) from scratch&lt;/li&gt;
&lt;li&gt;As asn.1 implementation, we are using &lt;code&gt;rasn&lt;/code&gt; now which delivers satisfying results. That said: OpenAGPS SUPL is now a Rust component.&lt;/li&gt;
&lt;li&gt;Only blockage we are facing still is decoding issues and incompatibilities between &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/porygon&quot;&gt;Porygon&lt;/a&gt;&#39;s Python implementation and &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/porygon&quot;&gt;SUPL&lt;/a&gt;&#39;s Rust implementation, but this is in the makings...&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/sggua&quot;&gt;Serhii Horichenko&lt;/a&gt; became the initial tester with zero background knowledge on OpenAGPS and did a cold water dip into the pool.
&lt;ul&gt;
&lt;li&gt;Thanks for being the first outside who put together a &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/esp32-c3-ublox&quot;&gt;base station hardware&lt;/a&gt; according to our documentation.&lt;/li&gt;
&lt;li&gt;The &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/base-stations/bs-esp32-ublox/&quot;&gt;docs have since then see much improvement&lt;/a&gt;, thanks to Serhii&#39;s feedback and contributions.&lt;/li&gt;
&lt;li&gt;Also, big cudos for updating the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/&quot;&gt;OpenAGPS architecture&lt;/a&gt; schematics and making it finally right.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;Alex Richards&lt;/a&gt; assisted during the whole phase of the SUPL server/client/protocol development with expertise, code reviews and other feedback.&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/RaoulKramer&quot;&gt;Raoul Kramer&lt;/a&gt; was hightly busy around managing the project and reaching out to the new, potential OpenAGPS community:
&lt;ul&gt;
&lt;li&gt;A &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/&quot;&gt;new website&lt;/a&gt; based on &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://www.getzola.org/&quot;&gt;Zola&lt;/a&gt; (static site builder) has been set up. The site now combines general information on the project, our blog, a community overview section and documentation pages that are pulled in from the actual code repositories (deduplication of information).&lt;/li&gt;
&lt;li&gt;Hardware parts for seven more base stations have been ordered and shipped to Serhii for being put together (and will then forwarded to new potential OpenAGPS community members, base station hosters of the first hour).&lt;/li&gt;
&lt;li&gt;Reorganize the budget plan, act as point of contact to NLnet and coordinate the work of the team.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/sunweaver&quot;&gt;Mike Gabriel&lt;/a&gt; (myself) from (Fre(i)e Software GmbH) joined the team providing quality assurance, and providing project &amp;amp; release management expertise regarding OSS projects where needed. He also helped out with website fine-polishing and &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://sunweavers.net/blog/node/161&quot;&gt;announced the birth of OpenAGPS&lt;/a&gt; on his personal blog (which appeared today on &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://planet.debian.org&quot;&gt;Debian Planet&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You probably already know, but this project has been funded through &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl/mobifree&quot;&gt;NGI Mobifree Fund&lt;/a&gt;, a fund established by &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;NLnet&lt;/a&gt; with financial support from the European Commission&#39;s &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://ngi.eu&quot;&gt;Next Generation Internet&lt;/a&gt; program. Learn more at the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl/project/OpenAGPS&quot;&gt;NLnet project page&lt;/a&gt;. Hosting for this project is generously sponsored by &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://leaf.cloud/&quot;&gt;Leaf Cloud&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;&lt;img src=&quot;https://nlnet.nl/logo/banner.png&quot; alt=&quot;NLnet foundation logo&quot; width=&quot;20%&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Sadly, the initial NLnet funding project phase is now over; all of the money has been used up.&lt;/p&gt;
&lt;p&gt;So, we might go into a bit of hiatus until new funding opportunities come up (a follow-up NLnet funding application has been sent just in time before the deadline).&lt;/p&gt;
&lt;p&gt;The project for now switches to an after work / spare time project, unless people realize the worth of having an open alternative to AGPS / SUPL on this planet.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/sunweaver&quot;&gt;Mike Gabriel&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>OpenAGPS - The New Kid on the Block</title>
        <published>2026-11-07T00:00:00+00:00</published>
        <updated>2026-11-07T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-6/"/>
        <id>https://openagps.net/blog/update-6/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-6/">&lt;h3 id=&quot;the-situation-today&quot;&gt;The Situation Today&lt;/h3&gt;
&lt;p&gt;The domain of assisted geo location services has been left to a few big tech providers. When using GPS on mobile devices, most of us send info on our approximate device location (based on cell tower IDs seen by our devices around us and the cell towers&#39; signal strengths) mostly to Google&#39;s SUPL service in order to facilitate a faster GNSS/GPS lock on the satellites flying above us.&lt;/p&gt;
&lt;p&gt;Without assistance, retrieving a GNSS/GPS lock on sufficient satellites includes &quot;finding&quot; those satellites and once found retrieving data (in bytes/sec) from them. In some regions, this leads to waiting periods of up to 45 minutes, before a mobile devices has gained a lock on sufficient satellites (3 or more).&lt;/p&gt;
&lt;p&gt;In Assisted-GNSS/GPS, &quot;other&quot; information (such as cell tower IDs) gets used to estimate what GNSS/GPS satellites are currently passing over one&#39;s location. With AGPS, the mobile devices retrieve information via a so-called SUPL server, containing two details: a list of potential satellites above and their dataframes. Esp. providing those dataframes over the device&#39;s internet connection (and not via the GNSS/GPS receiver downloading it from the satellite itself) speeds up the lock-on process of the mobile tremendously (several seconds to a few minutes).&lt;/p&gt;
&lt;p&gt;However, for this mechanism to work, your device will share your IMSI (although not needed for AGPS), a list of cell towers around you and their signal strengths with the provider of the SUPL service, revealing your approximate position. In total, this allows SUPL providers to re-identify each mobile device and create motion profiles of each such device (and its owner). If the SUPL service is hosted by one main provider (i.e. Google SUPL), there is a lot of valuable information available to them for free that they can commercialize.&lt;/p&gt;
&lt;p&gt;Currently, there is only one mitigation method available to hide one&#39;s location info from the SUPL server(s) at e.g. Google: using a SUPL proxy server implementation (available as OSS, provided by and used in e.g. GrapheneOS). A SUPL proxy still depends on the big tech service provider(s) for SUPL as it merely proxies SUPL requests from mobile devices through to the proprietary SUPL services, at e.g. Google, but the mobile device is being camouflaged behind the SUPL proxy in use.&lt;/p&gt;
&lt;h3 id=&quot;the-solution-to-all-of-this-openagps&quot;&gt;The Solution to All of This: OpenAGPS&lt;/h3&gt;
&lt;p&gt;OpenAGPS, on the contrary, will be a fully independent implementation from proprietary service providers, and it will refrain from collecting and commercializing end users’ data. It will be driven by individuals of the OpenAGPS community. There will likely be one central service that the OpenAGPS project plans to host and operate (the Porygon frontend/backend, OpenAGPS&#39;s GNSS Almanach service), but except from that SUPL servers can be self-hosted by individuals, companys or other communities. The requesting mobile devices&#39; IDs will be hidden from the Porygon server (like with existing SUPL proxy implementations), so that the only centrally operated component (the Porygon Almanach server) does not know who is requesting what geo position information (and thus cannot collect such data, neither derive info about where requesting devices are located).&lt;/p&gt;
&lt;p&gt;In addition, with a large OpenAGPS community, it is imaginable (in theory) that there will also be multiple central Almanach servers available on the internet (with parallel networks of base stations attached to each GNSS Almanach server).&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/&quot;&gt;Checkout the OpenAGPS architecture schematics and our website/documentation to learn more.&lt;/a&gt;&lt;/p&gt;
&lt;h3 id=&quot;collecting-satellite-data&quot;&gt;Collecting Satellite Data&lt;/h3&gt;
&lt;p&gt;The OpenAGPS project is not simply a software that admins/users can install, it needs kind of a huge and global community to operate/host/house its base station network.&lt;/p&gt;
&lt;p&gt;The challenge with providing a community-driven AGPS service on the internet is that up-to-date (real-time!) GNSS/GPS satellite position data is not available for free download. Almanach data can be obtained per region from various organisations, but then their datasets are often days to weeks old, thus too outdated. GNSS/GPS satellites are not geo-stationary, they circulate around the planet. Their position is dependent on the current date-time. A globally spanning network of GNSS/GPS base stations will do the trick here. We will need a community that harvests the needed satellite data in real time and makes it available through the Porygon Almanach server to all OpenAGPS users.&lt;/p&gt;
&lt;p&gt;The OpenAGPS project will depend on at least one community member every ~40-50 km² to operate a so-called OpenAGPS base station: These base stations are stationary, need to run 24/7, and they will harvest GNSS/GPS statellite data information from the satellites above in real-time and share this data with the (central) Porygon server, continuously. The Porygon server will create a timestamp-dependent &quot;map&quot; of all seen satellites and extrapolate locations between base stations&#39; Almanach data updates.&lt;/p&gt;
&lt;h3 id=&quot;help-making-openagps-a-success-host-a-base-station&quot;&gt;Help making OpenAGPS a Success: Host a Base Station&lt;/h3&gt;
&lt;p&gt;To make OpenAGPS a success, we need volunteers who are willing to host (actually: house) an OpenAGPS base station at their home or work place (or both). Users will only be able to use their self-hosted OpenAGPS SUPL server with their mobile devices (instead of e.g. Google SUPL), if we manage to establish sufficient coverage with those base stations in the area of interest, so that the OpenAGPS Almanach will get populated with sufficient satellite position data.&lt;/p&gt;
&lt;p&gt;If you&#39;d like to host/house such a base station, please &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/community/&quot;&gt;get in touch&lt;/a&gt; and &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/base-stations/&quot;&gt;check the docs&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;support-this-project-by-co-funding-it&quot;&gt;Support this project by Co-Funding it&lt;/h3&gt;
&lt;p&gt;If you realize that you have an interest in this project and would like to improve your level of digital sovereignty in your government, organization, at your home, etc. then consider sending financial support to the project. If you want to support us, please get in touch with Raoul Kramer at &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://betabreak.net&quot;&gt;BetaBreak&lt;/a&gt; or Mike Gabriel at &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://freiesoftware.gmbh&quot;&gt;Fre(i)e Software GmbH&lt;/a&gt;. If you are a software developer and would like to contribute to OpenAGPS, also get in touch and let us meet at &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://fosdem.org&quot;&gt;FOSDEM 2027&lt;/a&gt;.&lt;/p&gt;
&lt;h3 id=&quot;credits&quot;&gt;Credits&lt;/h3&gt;
&lt;p&gt;A huge thanks to the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;NLnet Foundation&lt;/a&gt; for funding this project&#39;s bootstrap phase. Follow-up funding has been applied for, so please keep fingers crossed!&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;&lt;img src=&quot;https://nlnet.nl/logo/banner.png&quot; alt=&quot;NLnet foundation logo&quot; width=&quot;20%&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/sunweaver&quot;&gt;Mike Gabriel&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>The first major roadblocks</title>
        <published>2025-08-19T00:00:00+00:00</published>
        <updated>2025-08-19T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-4/"/>
        <id>https://openagps.net/blog/update-4/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-4/">&lt;p&gt;Hi everyone! Another update from us:&lt;/p&gt;
&lt;p&gt;As you may know, the goal of this project is to implement a SUPL-compatiable AGPS assistance server. Now, there are some unexpected technical challenges here that I felt were enough to announce here given that they are basically blocking a lot of testing and development:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;SUPL uses ASN.1. This is okay, there are open-source ASN.1 toolchains, but the one we were using (python-asn1tools) seemingly does not properly decode some messages from modern devices. This is a problem, as any decoding errors are, from its perspective, fatal.&lt;/li&gt;
&lt;li&gt;Most other ASN.1 toolchains are not featured enough to get close to properly being able to compile the ASN.1 specification for SUPL. There is &lt;code&gt;asn1c&lt;/code&gt;, but it is old, and seemingly has problems compiling for me (that or I just couldn&#39;t get it to work properly myself), and I would also personally rather use a programming language like Python for things like this.&lt;/li&gt;
&lt;li&gt;I wasted a lot of time trying to get the Python library to work (I am not super experienced with ASN.1, so I was mostly trying stuff, hoping that it would start working), and a lot more time to being demotivated from it&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This means we are (temporarily!) going to try something else: making our own assistance protocol. We already had ideas of doing this - ASN.1 may be standardized, but if someone wants to implement something using it, it can be a huge pain, compared to something like protobuf, or even JSON-encapsulated messages.
Hopefully, I can wire something simple up soon, but don&#39;t expect anything too quickly, since any protocol I hammer together will likely be based around the best way to sideload AGPS data into the testing devices I have (basically, a Fairphone 4, and a Volla 22), and I&#39;ll need to look into how to best do that (any help with that is welcome, as always!).&lt;/p&gt;
&lt;p&gt;If you are interested in potentially hosting a GPS base station - or are in a position to otherwise contribute GPS frame data - feel free to contact me, my contact info is on my &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;GitLab page.&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As always, any updates to code will be posted onto the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps&quot;&gt;OpenAGPS gitlab page.&lt;/a&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;Alex Richards&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Infrastructure + Porygon (in theory) up!</title>
        <published>2025-06-01T00:00:00+00:00</published>
        <updated>2025-06-01T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-3/"/>
        <id>https://openagps.net/blog/update-3/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-3/">&lt;p&gt;Hi everyone! Slightly delayed compared to what we hoped for, but we finally have more things to announce:&lt;/p&gt;
&lt;p&gt;We set up &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/infra&quot;&gt;some automated infrastructure scripts&lt;/a&gt; that create and start our OpenStack instances - hosted on &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://leaf.cloud/&quot;&gt;leaf.cloud&lt;/a&gt;.
&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/porygon&quot;&gt;Porygon&lt;/a&gt; is now also packaged as a Docker container, which makes automatically starting it in the instance relatively simple.
The &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;http://api.openagps.net/docs&quot;&gt;API&lt;/a&gt; is still very simple (but enough that pointing a base station at it should not error out), however (when it is up, we give no guarantees, and at the moment, updates take it offline), you can see the API docs &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;http://api.openagps.net/docs&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;If you are interested in potentially hosting a GPS base station - or are in a position to otherwise contribute GPS frame data - feel free to contact me, my contact info is on my &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;GitLab page&lt;/a&gt;.
We have also begun writing more &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/&quot;&gt;documentation&lt;/a&gt; in general, this includes some (not yet fully finished) &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://openagps.net/docs/base-stations/&quot;&gt;documentation on setting up a base station&lt;/a&gt;.
The firmware on the base station has been functional for a while now, although it is a bit complicated to setup. We aim to make this easier at some point in the future, although for now, getting the backend up and running is more of a priority.&lt;/p&gt;
&lt;p&gt;As always, any updates to code will be posted onto the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps&quot;&gt;OpenAGPS gitlab page.&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Things will hopefully ramp up a bit from here - at least when exam season is over for me - so stay tuned!&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;Alex Richards&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Where we have been?</title>
        <published>2025-04-07T00:00:00+00:00</published>
        <updated>2025-04-07T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-2/"/>
        <id>https://openagps.net/blog/update-2/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-2/">&lt;p&gt;Hello - It has been a while! Sorry for the radio silence for a bit...&lt;/p&gt;
&lt;p&gt;I (Alex Richards, the main and currently only developer on this) have been very busy with uni and other projects that have been taking time on this - rest assured, this has not been forgotten.&lt;/p&gt;
&lt;p&gt;I personally aim to have more to show within the next week or two - ideally, including some public (but without any guarantees on any uptime or functionality!) APIs regarding positioning via cellular information (and contributing celluar information).&lt;/p&gt;
&lt;p&gt;If you are interested in potentially hosting a GPS base station - or are in a position to otherwise contribute GPS frame data - feel free to contact me, my contact info is on my &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/electrodeyt&quot;&gt;GitLab page&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;As always, any updates to code will be posted onto the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps&quot;&gt;OpenAGPS gitlab page.&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Sorry for things being this slow - as said, I am pretty busy with things, along with other personal things going on - I will however try my best to write blog posts whenever something interesting happens, so stay tuned!&lt;/p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Hello</title>
        <published>2024-12-06T00:00:00+00:00</published>
        <updated>2024-12-06T00:00:00+00:00</updated>
        
        <author>
          <name>Unknown</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://openagps.net/blog/update-1/"/>
        <id>https://openagps.net/blog/update-1/</id>
        
        <content type="html" xml:base="https://openagps.net/blog/update-1/">&lt;p&gt;Welcome to the OpenAGPS website! This post is mostly acting as a placeholder for future content here; we will be making regular blog posts about development and development progress. At time of writing this blog post, we have started work on developing on a simple GNSS base station/receiver using an &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps/esp32-c3-ublox&quot;&gt;ESP32-C3 and a UBlox M8N board&lt;/a&gt;; expect more updates soon!&lt;/p&gt;
&lt;p&gt;We will be hosting our code on &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://gitlab.com/openagps&quot;&gt;GitLab under the openagps organisation&lt;/a&gt;, feel free to take a look!&lt;/p&gt;
&lt;p&gt;If you don&#39;t know, this project is funded through &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl/mobifree&quot;&gt;NGI Mobifree Fund&lt;/a&gt;, a fund established by &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;NLnet&lt;/a&gt; with financial support from the European Commission&#39;s &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://ngi.eu&quot;&gt;Next Generation Internet&lt;/a&gt; program. Learn more at the &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl/project/OpenAGPS&quot;&gt;NLnet project page&lt;/a&gt;. Hosting for this project is generously sponsored by &lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://leaf.cloud/&quot;&gt;Leaf Cloud&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a rel=&quot;noopener external&quot; target=&quot;_blank&quot; href=&quot;https://nlnet.nl&quot;&gt;&lt;img src=&quot;https://nlnet.nl/logo/banner.png&quot; alt=&quot;NLnet foundation logo&quot; width=&quot;20%&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
</content>
        
    </entry>
</feed>
