lucidiot/rsrsss
lucidiot
/
rsrsss
2
1
Fork 0
Code Issues Releases Activity

Post about tempr.email

This commit is contained in:
~lucidiot 2024-02-20 22:37:00 +01:00
parent 58c4cbd2e0
commit 8b2e77288c
1 changed files with 34 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
feed.xml
View File

@ -2309,6 +2309,40 @@ return <type id="{$i}" name="{$type}" count="{$count}" />
<p>And if you were expecting actual tombstones from this namespace, well do know that <a href="https://www.eunicetoday.com/taxonomy/term/462/feed" target="_blank">RSS feeds for obituaries</a> are a thing. You're welcome.</p>
]]></description>
</item>
<item>
<title>tempr.email</title>
<pubDate>Sun, 18 Feb 2024 16:13:21 +0100</pubDate>
<guid isPermaLink="false">tempr-email</guid>
<category domain="https://envs.net/~lucidiot/rsrsss/">Feed</category>
<description><![CDATA[
<p>Thanks to marketing and analytics, temporary email addresses are too often necessary to keep some amount of control over your inbox. <a href="https://tempr.email/" target="_blank">tempr.email</a>, originally discard.email, is a service that provides such addresses, with a rather wide range of domains as well as the possibility to use your own custom domain. While it is very likely that all of the listed domains are included in lists of temporary email domains used by some websites to block them, you can still hope that at least one of these domains is going to work as the lists used by websites may not be fully up to date. If I need a temporary address, and can't find any credentials on <a href="https://bugmenot.com/" target="_blank">BugMeNot</a>, I will probably be using tempr.email.</p>
<p>I recently discovered that it has <abbr title="Really Simple Syndication">RSS</abbr> 2.0 and Atom support, to let you monitor for emails received at your trash address. To activate this, you need to use an address on a domain that supports locking addresses with a password. Those domains are marked with the <code>(PW)</code> suffix on the homepage. Pick an address that is unlikely to have already been used, and you can then set a password on the web UI. The password is removed after 3 months of inactivity.</p>
<p>Once you have a password, you can access the RSS and Atom feeds using the following URLs:</p>
<ul>
<li><code>https://tempr.email/en/rss/[email address]:[MD5 hash of your password]</code></li>
<li><code>https://tempr.email/en/atom/[email address]:[MD5 hash of your password]</code></li>
</ul>
<p>For example, if your address is <code>nope@gmai.com</code> and your password is <code>hunter2</code>, then your feeds will be the following:</p>
<ul>
<li><code>https://tempr.email/en/rss/nope@gmai.com:2ab96390c7dbe3439de74d0c9b0b1767</code></li>
<li><code>https://tempr.email/en/atom/nope@gmai.com:2ab96390c7dbe3439de74d0c9b0b1767</code></li>
</ul>
<p>Note that if you are trying to use <code>md5sum</code> to compute the MD5 hash, do not forget to use <code>print</code> or <code>printf</code>, not <code>echo</code>, because <code>echo</code> will add a line break character that will also be hashed.</p>
<figure>
<pre># Wrong hash!
$ echo hunter2 | md5sum
6a0f0731d84afa4082031e3a72354991 -
# Correct hash
$ printf hunter2 | md5sum
2ab96390c7dbe3439de74d0c9b0b1767 -
</pre>
<figcaption>Hashing the password with <code>md5sum</code></figcaption>
</figure>
<p>That's neat. I like the idea of emails to RSS feeds, since it lets you centralize even more things into your feedreader. There are obvious security concerns here with the automatic password removal, or the fact that MD5 hashes are used, which could imply passwords are stored as MD5 hashes, or worse, a <a href="https://plaintextoffenders.com/" target="_blank">plain text offender</a> status. But it doesn't sound like it would be that difficult to secure your feed a little harder and get any email inbox as an RSS feed.</p>
]]></description>
</item>
</channel>
<access:restriction relationship="allow" />
</rss>