Tagged: Free and Open Source
There are many use cases where I want to share the links with other devices from a Desktop. One specific use case is solved by read-later setup I have. It’s the case where I want to read something later, preferably in offline mode. The content also gets archived. The other important usecase is that I want to share the link for quick access on a different machine, like a link to the Metabase dashboard or a link to the plantuml diagram, etc. This is where ntfy and Greasemonkey work very well. I have a userscript that pickups up the current document URL and title and posts it to ntfy topic.
I am slowly moving to LineageOS on my personal phone. The most important features I use on that phone are Email, Messaging, Mapping, and Alerts. I have found decent alternatives for Email, Messaging, and Mapping. Alerts or Notifications are something I depend on a lot; currently, they are Google or Apple features. I could settle down for pulls (I get a few alerts by way of RSS feeds), but push would be great. Especially for alerts from my home or servers. Hence was looking for it. NTFY suited my needs from all angles. Therefore I took some time to deploy it.
I use my tpx as a travel machine; at home, it’s mainly used remotely. As in, I connect to it either through ssh or through a remote desktop and work on it. I wanted RDP and not VNC, mostly because I want to have a session on the remote desktop with the same profile etc. And also allow others to log in using their profile. Somewhat akin to SSH logins.
consistent. Email template insertion is one of them. It can be done easily using phrases in AutoKey. But phrases support only simple text. But I do like HTML emails sometimes. So this is my hack.
It was an exciting week. Many things got done, and it was a reasonably successful week.
Badges are ubiquitous on the web. Any website that has some social component has badges. Audible gives you badges based on your listening. StackOverFlow gives you badges based on your participation etc. The problem with these badges is that they are not portable and not verifiable. For example, if you are on a site where you want to show or prove the badge that you have acquired on StackOverFlow, then it’s not possible. OpenBadge solves this.
