HN user

geonnave

207 karma
Posts15
Comments74
View on HN

Super cool! I had a very similar idea recently: I wanted to have on-demand podcasts about one's surroundings as you explore a new place (also taking into account a small list of user interests). I did a prototype [1] with the OpenAI APIs but the generated results were too shallow and not as interesting. It seems you prepared it with more carefully curated content, smart. My city is covered by Audiala, will give it a try!

[1] https://github.com/geonnave/roadcast

Selecting text

(...) there is a completely new gesture, double tap. Wait, there is actually a third gesture long press, which also works.

TIL about the double tap -- always used the long press to select text. It is interesting that the author refers to long press as an alternative. Do most people use double tap for that?

LoRa[WAN] is too limited for this use case. MTUs range from 51 to 242 bytes, and packet loss increases with packet sizes and distance. In addition, it lacks a built-in mechanism for reliability (e.g. ACKs). In other words, lots of headaches, unless your use case is sending non-critical telemetry data up to a few hundreds times per day.

For more information I recommend this paper [1] (unfortunately behind a paywall).

[1] https://ieeexplore.ieee.org/document/8030482

For those also wondering what is ETL and dbt:

ETL (Extract, Transform, Load) is a process that involves extracting data from various sources, transforming it to fit operational needs, and loading it into a database for analysis. dbt (data build tool) is an open-source software tool that enables data analysts and engineers to transform and model data in the data warehouse, streamlining the transformation part of the ETL process.

The way the author begins the article makes you think Google is trying to s/HTTP/$NEW_PROPRIETARY_PROTOCOL/, although they just mean s/HTTP/HTTPS/.

My experience is completely different. I have successfully used GPT-4 to:

- write a contract for the sale of my motorcycle: put all details, names and numbers with labels on a spreadsheet, paste on the chat and ask for a contract, then edit.

- learn french: I told gpt "when I write wrong stuff in french, always let me know and teach me the correct ways". Then, after a few weeks I asked for a .csv with the stuff that he corrected so I could import into Anki, which actually worked.

- coding on a daily basis: I am learning Rust on my new job, so I ask it things all the time, it helps me a lot.

You just have to file a note explaining that you could not vote -- we call it "justifying the (non-) vote" / "justificar o voto". As of the current election, the it can be done on a mobile app.

For the "Learning resources" section, I would also recommend checking ION¹. I have tested a few DID Methods including Sovrin, Veres One, and ION, and the latter is the most spec-adherent and well-implemented, apart from receiving funding from companies like Microsoft and TBD (which is proposing web5 in the first place). And yes, it is the only DID Method to receive support from big tech (was incubated within Microsoft, then donated to the Decentralized Identity Foundation), and it also happens to be a technically better solution.

Why I think it is better: (1) don't need a new blockchain (re-uses Bitcoin's); and (2) implements DIDs / DID Documents with all needed features (e.g. last time I tried, Sovrin's implementation did not support serviceEndpoints!)

¹ https://identity.foundation/ion/

² https://www.coindesk.com/markets/2021/03/25/microsofts-ion-d...

A nice addition would be either (1) support other languages or (2 - simpler) the ability to edit the field titles (e.g. change from "Network name" to "Nome da rede").

Clearly and unsurprisingly this is to compete with Substack. Great move.

Now, regarding character limits, beyond linking to a personal website or having a newsletter, I have seen avid content creators posting images containing small essays directly on Twitter to allow a deeper in-app reading experience.

Maybe this should be a next, and less trivial, problem for Twitter to work on.

Indeed, the main problem of trust is the third party and agreement.

The DID and VC standards have an interesting approach. Use self-signed public keys, and third-party-signed credentials. To prevent MITM use credentials, to encrypt channel use the keys.

The agreement part, however, remains difficult because the protocols are always evolving.

Maybe in a few years we'll get it solved, just like Bitcoin solved double-spending without centralization?

My two cents:

1. Have a medium/long term goal, and then structure the topics you want to learn around that.

2. Plan and execute projects that exercise the topics you want to learn.

If finding the goal (1) is a problem, maybe start with solving that problem.