604 karma · joined November 2, 2008
https://github.com/bengtan
https://twitter.com/bengtanAU
----
Interesting Things -- A curation of interesting stories and links from tech, biz, science and others. Weekly email newsletter.
https://bengtan.com/interesting-things/
----
Author here.
This is a follow-up on a previous posting (https://news.ycombinator.com/item?id=26293424)
What do you guys think?
Happy to answer any questions or comments.
Thanks for reading!
Author here.
This is a follow-up on a previous posting (https://news.ycombinator.com/item?id=26293424)
----
If you don't mind me hijacking the conversation, I'd like to ask the following questions to the wonderful HN community:
* What do you think about the name change to Untracker?
* What do you think about Untracker (as a product)?
* What do you think about Untracker being open source but requiring self-hosting?
* What do you think of the discussion about Github Sponsors and the Payment Decision Point?
* What do you think about Untracker's freemium/monetisation/sponsorship model?
What do you guys think?
If you have any feedback, comments or questions, I'd love to hear it.
Thanks for reading!
Author here.
Happy to answer any questions or comments.
This blog post is a bit outside of what I normally write about. Hope you guys find it interesting.
> Only issue I see is that this something that should be directly integrated into email clients, not something I would get a third party app for
I agree that it would be better integrated as part of an email client. But that's nothing something I can do. So I'm trying to do the next best thing.
> (how do we trust you to forward emails to - I wouldn’t for work purposes, but would definitely consider for personal purposes).
I agree about the trust issue as well. Which is why I say ... only send publicly available email newsletters.
I don't expect people to forward private/confidential emails. Nor do I want them to.
> It’s privacy-by-obfuscation instead of privacy-by-abstention. But it does prevent your web browser/IP address/location from being leaked.
> Is the starting HTML really that bad?
I think the mailing list service providers just don't care. If they did, they would easily see that extremely long blocks of random text (ie. a link) in plain text kills the readability.
I agree that there are both sides to the argument.
> you could include in the processed email both the original link (tracked) and the destination. Then, you as a reader can decide if you want to be tracked (and give feedback to the publisher) or not.
That's what I initially tried to do, but it was too hard to make it work when the link was an image (or a social media icon) instead of text. I could give it another try but it will have to be another time.
Author here.
Happy to answer any questions or comments.
----
If you don't mind me hijacking the conversation, I'd like to pose two questions to HN:
> Alternatively, I considered calling it ‘UntrackMe: Remove tracking from email newsletters’. Which sounds better?
and
> I don’t know if it’s worth the effort to do this. Do many people still read emails in plain text?
What do you guys think?
Thanks for reading!
Thanks anyway.
However, I'm wondering whether there's any automated way to do this.
I don't really want to be doing 10-20 keypresses manually for each link.
I asked this on reddit and wanted to ask here too, but didn't want to post text and attract the 'self post' penalty. So I posted a link instead.
But here's the text (from reddit) anyway:
----
Hi,
I subscribe to email newsletters which contain hyperlinks. I'd like to be able to hover over a hyperlink and see what the URL is before deciding whether to click on it.
However, the hyperlinks are something like this:
https://ben-evans.us6.list-manage.com/track/click?u=b98e2de8...
and I can't easily work out where the hyperlink links to.
(FWIW, this link redirects to: https://www.reuters.com/article/us-usa-cyber-florida-idUSKBN... )
Is there some way which lets me find out the destination URL without me having to click on it first?
I don't like clicking on links in emails without seeing where it leads to. For example, if I can see that it's a dubious looking domain, then I would be more careful in case it's a phishing site.
FWIW, I use Gmail so a Gmail specific solution (browser extension?) could work for me. Seeing the link by hovering over it seems natural to me, but I'd consider alternatives too.
Thanks all for reading!
The topics in the story apply to use of any password manager, not just 1Password.
Whilst I'm sure we all know that we should use password managers, it's another thing to hear a first-hand anecdotal account where they made a significant difference.
(Disclaimer: Submitter (but not author))
* I'm not a big fan of Google's ubiquitousness and power, but
* I think a 'link tax' is not the right way to go, but
* I think Microsoft is being opportunistic here.
In this case, the enemy of my enemy is not necessarily my friend.
Hi,
My previous major gig was an Engineering Manager/Software Engineer hybrid (and occasional executive) at a 100% remote US startup for 5 years.
I also have a smattering of side projects.
I have wide ranging experience with software and technology.
I'm a self-motivated person and always learning new things.
I'm a creative thinker who is able to take a multi-disciplinary approach to solving problems.
I don't just do 'software', but also the business, legal, social and startup issues around software. (I'm well-read on startup literature.)
I'm a problem solver. Give me a problem and throw me in the deep end. You don't have to keep checking on me. I'll find a way out. I'll either solve the problem or provide you with the necessary information to make an informed decision.
I specialise in debugging hard problems which no one else wants to do.
I keep myself busy. You can see from my work history that, if not employed, I always have a side project happening. But don't let that deter you. I'm always willing to shuffle my priorities for the right opportunity.
Thank you for reading and hope to hear from you.
(No recruiters please.)
Remote: Yes
Willing to relocate: Doubtful but not ruling it out
----
Technologies:
I've been around for quite a while and done something of everything but here are some of the more relevant:
* GoLang, Java, JavaScript, TypeScript, PHP, Python
* Web development, LAMP, jQuery, Mysql, Sqlite, Symfony, Amazon AWS
* ReactJS and the usual javascript ecosystem
* React Native, native Android app development
* Good at debugging hard problems (especially those from the field)
* See resume for full list (including soft skills)
* See resume for work history and open source projects (ie. sample code)
----
Resume: https://github.com/bengtan/resume
Email: ${username} + '1' + '@' + 'gmail' + ${dot_com}
(continued below ...)
* GoLang, Java, JavaScript, TypeScript, PHP, Python
* Web development, LAMP, jQuery, Mysql, Sqlite, Symfony, Amazon AWS
* ReactJS and the usual javascript ecosystem
* React Native, native Android app development
* Good at debugging hard problems (especially those from the field)
* See resume for full list (including soft skills)
* See resume for work history and open source projects (ie. sample code)
My previous major gig was an Engineering Manager/Software Engineer hybrid (and occasional executive) at a 100% remote US startup for 5 years.
I also have a smattering of side projects.
So I know what it's like to work for a tech startup.
I specialise in debugging hard problems which no one else wants to do.
Resume: https://github.com/bengtan/resume
Email: ${username} + '1' + '@' + 'gmail' + ${dot_com}
Do you mind if we talk? Please email me at ${username} + '1@' + 'gmail' + ${dotcom}
Thanks.
I wrote (and am still writing) Gig'o'Books (http://www.gigobooks.com) -- Accounting for gigs and side income.
I'm the first user (ie. dogfooding).
Thing is ... I'm sure there's a lot of people with gigs who would find it useful but for some reason, I'm having trouble finding them.
It's a convertible 2-in-1 on a stand that I got from eBay. The stand folds flat when packed into a suitcase.
Advantages:
* Much more ergonomic - no more neck strain
* Screen is closer to the eyes (to take advantage of the high DPI)
Thanks for your feedback.
> it's hard to eventually productize something and build a business, if that's your goal.
True, but hopefully once it gets enough eyeballs, a monetisation route will reveal itself.
I have two prospective ideas:
* Charging a one-off fee (in the range of $40-$80?) for a premium desktop edition of the software. Sorta-like COTS. This dovetails nicely with the 'non-cloud' idea.
* Just slap advertising on the web edition and hope it works :)
> The space is also complicated with regulations that are not easy to translate from one country / state to another. So an open source approach may not work perfectly.
Agree, but I'm adopting a 'wait and see' approach.
> However, I'd love to see some Open Source options that can piggyback on existing services, e.g. QBO api, so we can avoid paying the advanced features that are expensive, a lock-in and leaves something to be desired for customizability.
Oh, interesting! I didn't know QuickBooks had an online API. Thanks, I'll look into it.
Ack.
I acknowledge that the name could lead to misunderstanding.
Actually, the name is supposed to be a play on 'gig' (as in, a synonym for side project). I'm planning on rebranding it so it's more 'gig-o books' than 'gigo books'.
Thanks for the heads up, though.
> "I'll create the software X to fit my own specific requirements/needs, then I'll see if anybody else wants to use it as well (which would mean that that niche of people have the same needs/requirements), and if that's the case then I can decide if to put more energe/effort/$ into it otherwise it will just be something useful for myself" > > ..., right?
At a high level, yes.
(At a lower level, well, there will be variations on the same basic idea. The devil is in the detail.)
> I think that for that to work the important detail about the concept&implementation is that the SW must be complete > ... > and that the full functionality will be always available, even if in the worst case I don't have an Internet-connection.
Yes, GigoBooks is intended to be desktop linux/mac/windows software that runs entirely offline. If the OS doesn't change, it can keep operating forever.
> Btw., the GigoBooks app does not currently allow to save data, or did I overlook some menu-entry?
You're looking at the online demo which is necessarily functionality-limited because web browsers don't allow access to local files.
The 'REAL' thing is a desktop app which does allow saving data to local (sqlite) files (and yes, there are additional entries in the menu for this).
I don't quite understand.
> I'm fairly certain this process will be entirely automated by QB in the next 5 - 10 years, QB Cloud almost already is
QuickBooks, Xero, FreshBooks etc. already have entry-level online SaaS solutions. I'm aware of that.
So I don't quite understand by 'will be entirely automated by QB in the next 5 - 10 years'. 'What' will be automated?
If you care to elaborate, I'd be interested in hearing more.
Mostly agree! Specific comments below.
> I have found that it is important not to be afraid of doing market research, surveys, conducting interviews or observations of existing people in action with existing solutions.
Don't disagree, but I wanted to build something first, even if it's just proof-of-concept.
But now that I have a prototype, yes, I'm reaching out to get opinions. Blogging is part of that effort.
(Personally, I don't really like the idea of putting up a landing page to collect email addresses for 'vapourware'. When I say 'personally', I'm not passing judgement on people who do it. Just that ... I sort-of don't like doing it myself.)
> Since you’ve already decided to build this anyway, you aren’t concerned about competition - so what do you have to lose from seeing if other people want it? [1]
Agree. This is part of the effort of putting it out there and seeing what sticks.
> I see from the website the author is taking early access adopters, so maybe they are doing this. Actually I like the approach of doing this in the open and blogging about it, it was more the original blog post that triggered my reaction.
Ack. Ack. Understood.
The website is just a blog that I put up in a hurry so I have a place to do some blogging. I didn't spend a lot of time on it yet. It's definitely not the 'final' website (and obviously, it's a bit unfocused).
But I'll look into it. Thanks for reporting this!