@prologic@twtxt.net i’ll email you!

Serasa Experian é uma empresa tão pilantra mas tão pilantra que agora estão descaradamente fazendo spam a partir de emails coletados do registro brasileiro de domínios (Registro.BR) é muito irritante.

Unless your Terms of use update email looks and reads the same as the one I got yesterday from mastodon.social, I don’t wanna know about it, nor do I agree to it.

@movq@www.uninformativ.de > That guy over there in the corner…

I’m literally sitting in a corner chuckles. I rarely get any emails nowadays. But if I do and it is not plain-text, then my Mutt gets to bark at it and I, just… won’t read it. 🤷🏽‍♂️

@movq@www.uninformativ.de make that 4 people! i use plain text when i can because this page convinced me lmfao

@lyse@lyse.isobeef.org … because you, me, and that guy over there in the corner are the only three people left using plain-text email. 🫤 (And probably Stallman.)

@prologic@twtxt.net I will pull the email. The year is about right.

According to a very old email one of my more personal family domains was registered in 2013 making it 12 years old, so I was closed 🤣 my public facing one is much much older 🤣

@ About the URL, since it no longer used for hashing there might be no need to change it. I agree that we keep all the parts that already are out there for the most parts. Instead of a contact field you could also just use links like: link = Email mailto:user@example.dk or link = Signal https://signal.me/sthF4raI5Lg_ybpJwB1sOptDla4oU7p[...]

@andros@twtxt.andros.dev Thanks for consolidating a lot of good ideas. Especially how you have deiced to just extend the mention syntax for location-based treads. This might even be backward compatible with older (pre-yarn) clients.
What about using Z for UTC +00:00- is that allowed in your specs?
Regarding url = I would suggest to only allow one and the maybe add url_old = or url_alt = !?
I’m still not a fan of a DM feature, even thou it helps that i have now been split out into a separate feed file. Instead if would suggest a contact = field for where people can put an email or other id/link for an established chat protocol like signal or matrix.

I also fundamentally do not believe in the notion that Twtxt should be readable and writable by humans. We’ve thrown this “argument” around in support of some of the proposals, and I just don’t buy it (sorry). As an analogy, nobody writes Email by hand and transmits them to mail servers vai SMTP by hand. We use tools to do this. Twtxt/Yarn should be the same IMO.

Just like we don’t write emails by hand anymore (See: #a3adoka), we don’t manually write Twts or update our twtxt.txt feeds. Instead, we use modern Twtxt clients that conform to the specifications at Twtxt.dev for a seamless, automated experience. #Twtxt #Twt #UserExperience

Nobody writes emails by hand using RFC 5322 anymore, nor do we manually send them through telnet and SMTP commands. The days of crafting emails in raw format and dialing into servers are long gone. Modern email clients and services handle it all seamlessly in the background, making email easier than ever to send and receive—without needing to understand the protocols or formats behind it! #Email #SMTP #RFC #Automation

@bender@twtxt.net I use it. It’s not the feature I use the most in the fediverse, but I communicate this way with several friends. For example, it’s the main way I talk to the original creator of the twtxt-el repository, the way people greet me for the first time or the way they notify me of some bugs in the software I maintain. I can even tell you that it’s the main way I talk to some maintainers of the Emacs community. If there are any of you reading my words, speak up!
Why not have the same? There are things I want to say to @prologic@twtxt.net in private, why should I have to send him an email or private IRC? Or an public twt.
Of course, here’s a topic we’ve already talked about: what is twtxt for you? For me it will always be a social network, in microblogging format, but an asynchronous way of communicating. And having a tool to control visibility is basic 😄
I look forward to hearing from you @eapl.me@eapl.me !

@kat@yarn.girlonthemoon.xyz is there anything i can even run or is this like email where you should just use libera and shut up

my main itch with the DMs extensions is that these messages are intended to be private, not public information. That’s why other extensions make sense, but DMs are another kind of feature.
TwiXter, Mastodon, FB and some other services usually hide the DMs in another section, so they are not mixed with the public timeline.

I find the DM topic interesting, I even made an indie experiment for a centralized messaging system here https://github.com/eapl-gemugami/owl.
Although, as I’ve said a few times here, I’m not particularly interested in supporting it on microblogging, as I don’t use it that much. In the rare case I’ve used them, I don’t have to manage public and private keys, and finally none of my acquaintances use encrypted email.
Nothing personal against anyone, and although I like to debate and even fight, it’s not the case here. This proposal is the only one allowing DMs on twtxt, and if the community wants it, I’ll support it, with my personal input, of course.

A good approach I could find with a good compromise between compatibility with current clients and keeping these messages private is ‘hiding’ the DMs in comments. For example:
# 2025-04-13T11:02:12+02:00 !<dm-echo https://dm-echo.andros.dev/twtxt.txt> U2FsdGVkX1+QmwBNmk9Yu9jvazVRFPS2TGJRGle/BDDzFult6zCtxNhJrV0g+sx0EIKbjL2a9QpCT5C0Z2qWvw==

@andros@twtxt.andros.dev how often do you send a private message on the Fediverse? How often do you send PGP/SMIME encrypted emails? Are there other tools that are more suitable for the task? If implementing direct/private messages on twtxt scratches an itch (you know, that hobbyist itch we all get from time to time), then don’t give up so easily. Worse comes to worse, and your feed becomes too noisy, people can simply unfollow/mute.

I really don’t care about direct messages here, but I might be on that bottom 1%!

guys omg the people behind pico.sh are so nice ;_; one of the people running it emailed me to let me know i had what was likely a malfunctioning (or well, not working as intended) script that was spawning the same SSH tunnel over and over and they wanted to give me a heads up.

and i felt SO BAD because i worried i was straining their service or something so i disabled my 4 tunnels (they were serving little SSH games and services) and got back to them.

but i just woke up to THE NICEST EMAIL EVER reassuring me that i was actually using it as intended, it was just my script that was having problems, and they even said that if it was intended to work that way it was fine and they just wanted to let me know!

so i restarted the tunnels but have since added lockfiles as safeguards so that when the script is run it’ll check if it’s already running :D

Twtxt was made for nerds, by nerds.
I’d like to change that. It’s by nerds/hackers, for nerds/hackers and friends of these. It doesn’t have to be hacky all the time, as you don’t need to be a nerd to have a blog.
But, for that to happen, someone has to build the tools to improve UX.

by design there really is no way to easily discovers others
Yeah, I agree, and although there are directories of email addresses, usually you don’t want that, unless you are a ‘public figure’.
I couldn’t say that a microblogging is a “social network” by default, as a blog is not either. At the same time, people would expect to find new people and conversations, as you’d do in a forum.

I think of two features on top of the current spec:

• Clients showing a few posts of what your following are watching but you don’t, so perhaps you find something interesting to follow next. Or that feature of “Your ‘followings’ are following these accounts/people”. (Hard to explain in english, but I hope you get the idea)
  
• Sharing your .txt into some directory, saying “Hey, I have this twtxt URL, I want to be discovered”. I’m thinking of something like the Federated tab on Mastodon.

2 is a great idea, you should suggest it in that blog post.

About 1, well, I think anyone has an email address and only about 5% use a Feed, so it makes sense to offer what most people use 🤔

I have applied your comments, and I tried to add you as an editor but couldn’t find your email address. Please request editing access if you wish.

Also, could you elaborate on how you envision migrating with a script? You mean that the client of the file owner could massively update URLs in old twts ?

that’s a fair point.

Perhaps, since Twitter in 2006 never implemented read flags, every derivative microblogging system never saw that as an expected feature. This is curious because Twitter started with SMS, where on our phones we can mark messages as read or unread.
I think it all comes from the difference between reading an email (directed to you) vs. reading public posts (like a blog or a ‘wall,’ where you don’t mark posts as read). It’s not necessary to mark it as ‘read’, you just jump over it.

Reading microblogging posts in an email program is not common, I think, and I haven’t really used it, so I cannot say how it works, and whether it would be better for me or not.
However, I’ve used Thunderbird as a feed reader, and I understand the advantages when reading blog posts.

About read flags being simple, well… we just had a discussion this morning about how tracking read messages would require a lot of rethinking for clients such as timeline where no state is stored. Even considering some kind of ‘notification of unread messages or mentions’ is not expected for those minimalist client, so it’s an interesting compromise to think about.

@kat@yarn.girlonthemoon.xyz OK YAY SO RESET PASS DOES WORK IT JUST DOESN’T SEND AN EMAIL IT PRINTS IT ON THE PAGE LOL

GUYS HELP I LOCKED MYSELF OUT OF MY ACCOUNT ON WEB AND I COULDN’T GET EMAILS WORKING I’M STUCK POSTING FROM CLI LOLLLL

hey yarn pod hosting friends, how do i enable an SMTP relay in the env settings? i’m trying to get a friend on here and i’m pretty sure my env config is good but it won’t send emails even after restarts which is strange. i have the right hostname for mailjet, user and pass are in there, same with from address, i’m wondering if the port is messing it up bc it has to send from 587?

@prologic@twtxt.net Well I just mirrored yarnd’s JSON in my webfinger endpoint and lookup, so not much else to do for standardization.

And for people who don’t like PHP you can always just go with Added WebFinger support to my email address using one rewrite rule and one static file. or simply putting a static JSON in place for .well-know/webfinger

@eapl.me@eapl.me why not https://domain.com/.well-known/twtxt/:domain/:user ?

the business card test is this can you write it on your business card and have someone you give it to be able to figure it out without added context?

• phone number: yes because everyone knows what a phone number is.
  
• email address: yes, everyone knows an email and their aol or prodigy will let them email.
  
• twitter/x/insta/pintrest handle: no, whats a twitter? do i need to sign up?
  
• domain name: yes its simple and you just type it in a browser right?
  
• twtxt url: kinda? its a bit long and is that a forward slash? or a backward slash?

Lol. “Lighty Encrypted” https://www.pcmag.com/news/hot-topic-breach-confirmed-millions-of-credit-cards-email-addresses-exposed

This morning (and a little bit of the afternoon) the idea of having a full referenced archive of twtxts on the web has consumed me a bit. I am talking about something similar to the email archives one see online, but for twtxts, and a more personal level. Such archive would be available, even if the involved feeds are long gone, because feeds will be treated as received emails.

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

Another new email handling strategy I am applying is agressively deleting everything that I don’t need to keep for some reason.

So I’ve flattened my work and private email inboxes to single inbox folders and I don’t even know anymore what I was thinking before trying frantically to organise everything in sub folders. Labels and search filters are the way forward.

Moved my email back into a single ‘inbox’ folder instead of trying to keep everything organised in sub-folders. Using Vivaldi’s labels instead for organising the messages. Makes sense because I sometimes had trouble if a message needed to be in multiple boxes.

Diving into mblaze, I think I’ve nearly* reached peek email geek.

Just a bunch of shell commands I can pipe together to search, list, view and reply to email (after syncing it to a local Maildir).

EXAMPLES at https://git.vuxu.org/mblaze/tree/README

So far I’m using most of the tools directly from the command line, but I might take inspiration from https://sr.ht/~rakoo/omail/ to make my workflow a bit more efficient.

*To get any closer, I think I’d have to hand-craft my own SMTP client or something.

@movq@www.uninformativ.de Yes, the tools are surprisingly fast. Still, magrep takes about 20 seconds to search through my archive of 140K emails, so to speed things up I would probably combine it with an indexer like mu, mairix or notmuch.

#fzf is the new emacs: a tool with a simple purpose that has evolved to include an #email client. https://sr.ht/~rakoo/omail/

I’m being a little silly, of course. fzf doesn’t actually check your email, but it appears to be basically the whole user interface for that mail program, with #mblaze wrangling the emails.

I’ve been thinking about how I handle my email, and am tempted to make something similar. (When I originally saw this linked the author was presenting it as an example tweaked to their own needs, encouraging people to make their own.)

This approach could surely also be combined with #jenny, taking the place of (neo)mutt. For example mblaze’s mthread tool presents a threaded discussion with indentation.

@lyse@lyse.isobeef.org I’d suggest making the whole content-type thing a SHOULD, to accommodate people just using some hosting service they don’t have much control over. (The same situation could make detecting followers hard, but IMO “please email me if you follow me” is still legit twtxt, even if inconvenient.)

@prologic@twtxt.net Do you have a link to some past discussion?

Would the GDPR would apply to a one-person client like jenny? I seriously hope not. If someone asks me to delete an email they sent me, I don’t think I have to honour that request, no matter how European they are.

I am really bothered by the idea that someone could force me to delete my private, personal record of my interactions with them. Would I have to delete my journal entries about them too if they asked?

Maybe a public-facing client like yarnd needs to consider this, but that also bothers me. I was actually thinking about making an Internet Archive style twtxt archiver, letting you explore past twts, including long-dead feeds, see edit histories, deleted twts, etc.

I wrote some code to try out non-hash reply subjects formatted as (replyto ), while keeping the ability to use the existing hash style.

I don’t think we need to decide all at once. If clients add support for a new method then people can use it if they like. The downside of course is that this costs developer time, so I decided to invest a few hours of my own time into a proof of concept.

With apologies to @movq@www.uninformativ.de for corrupting jenny’s beautiful code. I don’t write this expecting you to incorporate the patch, because it does complicate things and might not be a direction you want to go in. But if you like any part of this approach feel free to use bits of it; I release the patch under jenny’s current LICENCE.

Supporting both kinds of reply in jenny was complicated because each email can only have one Message-Id, and because it’s possible the target twt will not be seen until after the twt referencing it. The following patch uses an sqlite database to keep track of known (url, timestamp) pairs, as well as a separate table of (url, timestamp) pairs that haven’t been seen yet but are wanted. When one of those “wanted” twts is finally seen, the mail file gets rewritten to include the appropriate In-Reply-To header.

Patch based on jenny commit 73a5ea81.

https://www.falsifian.org/a/oDtr/patch0.txt

Not implemented:

• Composing twts using the (replyto …) format.
  
• Probably other important things I’m forgetting.

@movq@www.uninformativ.de could it be possible to have compressed_subject(msg_singlelined) be configurable, so only a certain number of characters get displayed, ending on ellipses? Right now the entire twtxt is crammed into the Subject:. This request aims to make twtxts display on mutt/neomutt, etc. more like emails do.

So.. basically a rehash of the email “unsend” requests? What if i was to make a (delete: 5vbi2ea) .. would it delete someone elses twt?

@mckinley@twtxt.net Thanks for the feedback.

1. Yeah I agrees that nick sound not be part of syntax. Any valid URL to a twtxt.txt-file should be enough and is more clear, so it is not confused with a email (one of the the issues with webfinger and fedivese handles)
   
2. I think any valid URL would work, since we are not bound to look for exact matches. Accepting both http and https as well as a gemni and gophe could all work as long as the path to the twtxt.txt is the same.
   
3. My idea is that you quote the timestamp as it is in the original twtxt.txt that you are referring to, so you can do it by simply copy/pasting. Also what are the change that the same human will make two different posts within the same second?!
   

Regarding the whole cryptographic keys for identity, to me it seems like an unnecessary layer of complexity. If you move to a new house or city you tell people that you moved - you can do the same in a twtxt.txt. Just post something like “I move to this new URL, please follow me there!” I did that with my feeds at least twice, and you guys still seem to read my posts:)

@lyse@lyse.isobeef.org This looks like a nice way to do it.

Another thought: if clients can’t agree on the url (for example, if we switch to this new way, but some old clients still do it the old way), that could be mitigated by computing many hashes for each twt: one for every url in the feed. So, if a feed has three URLs, every twt is associated with three hashes when it comes time to put threads together.

A client stills need to choose one url to use for the hash when composing a reply, but this might add some breathing room if there’s a period when clients are doing different things.

(From what I understand of jenny, this would be difficult to implement there since each pseudo-email can only have one msgid to match to the in-reply-to headers. I don’t know about other clients.)

For following notifications I would say use webmetion refering to the the line in your twtxt.txt as per: https://darch.dk/mentions-twtxt
Or send them an email, so it would be an idea to add a # contact = mailto:me@domain.net to ones twtxt.txt

@movq@www.uninformativ.de, that would be a nice addition. :-) I would also love the ability to hide/not show the hash when reading twtxts (after all, that’s on the header on each “email”). Could that be added as a user configurable toggle?

he emailed my ISP about causing logging abuse. This is the only real ISP in my area, its gonna basically send me back to dialup.

Hey so.. i just got an email from my ISP saying they will terminate my service. Did i break something @abucci@anthony.buc.ci ?

I havnt seen any emails about the outage at work. I know i have the mac crowdstrike client though. My buddy that works at a hospital says they wernt affected.

#bomdia Ciberlândia

Image

you need to send an email @quark@ferengi.one if you want an account. I know that it might not be very profitable. Maybe Odo can disclose it if I give him a new bucket.

@bender@twtxt.net ha! He goes his “poem”:

A string of letters, a forgotten name,
An email crafted, a message to claim.
We hit send with a click, a hopeful sigh,
But a bounce-back arrives, a tear in our eye.

“Delivery failed,” the message reads cold,
The address it seems, is a story untold.
A ghost in the system, a memory’s trace,
Lost in the void of cyberspace.

:-D

My email is such a cluster of noise. The only time i actually use it is to find out I have to do my security training or something. All communication is slack now days.

Self-hosting email not by choice https://ec.je/b/3C2

I’m working on a few things, one of which was to fix up oh.mg and some email stuff

I’ve restarted my home mail server using wildduck.email. No idea why, guess I just needed a thing

it uses the queries you define for add/del/set/keys. which corrispond to something like INSERT INTO <table> (key, value) VALUES ($key, $value), DELETE ..., or UPDATE ...

the commands are issued by using the maddycli but not the running maddy daemon.

see https://maddy.email/reference/table/sql_query/

the best way to locate in source is anything that implements the MutableTable interface… https://github.com/foxcpp/maddy/blob/master/framework/module/table.go#L38

I maintain keys for my email addresses.. but like most in this thread i almost never receive encrypted emails.. other than the BTC exchange i use that sends automated mail encrypted.

Web hosting is being moved to Ouvaton, a French co-op and email not sure yet. Might use them or Nubo a Belgian co-op

SourceHut encrypts all emails if PGP key is uploaded to user profile (can be disabled in settings). Just… wow!

I use NNCP for everything from send/receiving emails, to Telegram/Matrix piping, and Youtube video queuing. So my plan was to upgrade but then one of my cats threw a temper tantrum over food, so I had to deal with that, then I upgraded everything. Finally 😅

@fastidious@arrakis.netbros.com Some of my friends in college were really excited to actually find other fellow nerds in college willing to engage in a key signing party. They used it to send like 3 or 4 inconsequential emails and then just gave up on it.

@movq@www.uninformativ.de keys.openpgp.org is a descent key server. They only publish a key the at has a valid email.

@lyse@lyse.isobeef.org
Bottomline, twtxt is a poor’s man email system. 🤣

Is it me, or Gmail’s web interface is going down the drain? Using Safari—my default browser—often takes two, or three clicks to open an email. If it weren’t because its search is amazing, I would never visit its web interface.

The features that macOS Monterey will bring, albeit minor, will made for a better “quality of living”. I am looking forward to Notes, and the iCloud+ integration (Private Relay, Hide My Email). It also bring macOS cohesively close to iOS. My work 2015 iMac and M1 Mini will get it, so looking forward to it!

@prologic@twtxt.net I know, because fork makes it 100% sure to know who is replying to whom. Just like email’s in-reply-to does (plus the message-id).

@prologic@twtxt.net What if the reply does what fork does, for any replies to the top post, but not the top post itself? You know, like email does. Other than to reply to the top post (for which I use reply), I don’t use reply but fork, to reply to posts underneath because it is the logical thing to do.

@movq@www.uninformativ.de But it makes sense, right? I spend way too much time trying to figure out who replied to whom. I treat twts replies as emails, pretty much.

I wonder how can I set, on Mutt, a shorter subject (elipsed) on the status bar, while reading a email (or a twt).

Based on spam logs, I am (again) considering banning a bunch of TLDs at the server level. Has anyone ever gotten legitimate email from a .work, .casa, or .today domain, for example?

So tired of mobile phone vendor lock in and bad usability for the sake of keeping people in their services. Try printing a file from your email inbox to a Bluetooth printer from your Android phone.

Ah, no; and there we have a good example of finger’s poor discoverability! It matches my email address, though: echo a.9srv.net | sed ’s/./@/’

@prologic@twtxt.net Web Key Directory: a way to self host your public key. instead of using a central system like pgp.mit.net or OpenPGP.org you have your key on a server you own.

it takes an email@address.com hashes the part before the @ and turns it into [openpgpkey.]address.com/.well-known/openpgpkey[/address.com]/<hash>

@prologic@twtxt.net huh.. true.. the email is md5/sha256 before storing.. if twtxt acted as provider you would store that hash and point the SRV record to the pod. .. to act as a client it would need to store the hash and the server that hosts the image.

if you thought emails were great at getting stuff lost, wait til you check out this thing called twtxt

Random link from the archives: http://www.atlasobscura.com/articles/disneyland-yippies-1970?utm_source=digg&utm_medium=email originally archived Tue Jul 25 10:08:28 EDT 2017

Email icon https://www.topic.com/the-accidental-crime-novelist

Email icon https://www.topic.com/the-hidden-history-of-holocaust-money

Email icon https://www.topic.com/giant-mirrors-ocean-whitening-here-s-how-exxon-wanted-to-save-the-planet

Email icon https://www.topic.com/cory-doctorow-how-writing-fiction-can-influence-the-future

The ‘As you know, Bob’ technique for infodumps gets a lot of flak, but all my internal corporate emails from upper management begin with ‘As you know,’, so I think there might be room to make it verisimilitudinous.

Isn’t it great that outlook just prevents people from emailing jar files to each other? Like, it’s not as though people occasionally need to send each other internal proprietary jars that aren’t conveniently hosted.

Email icon https://www.topic.com/mold-eats-world

I love how I just got an email to tell me that something I ordered was shipped. Funny thing is, this email came 2 days after it was delivered to me.

I hope the five people following my ‘misc’ repo on github are happy recieving an email containing only the placeholder commit message ‘xxx’ like 30 times a day.

So tumblr emailed me and told me I had reblogged posts by kremlin psyops socks. Anybody else get this?

How not to replace email https://jamey.thesharps.us/2018/02/16/how-not-to-replace-email/

Somebody wrote an email bot to waste scammers‘ time / Boing Boing https://boingboing.net/2017/11/08/somebody-wrote-an-email-bot-to.html

The scientists persuading terrorists to spill their secrets | News | The Guardian https://www.theguardian.com/news/2017/oct/13/the-scientists-persuading-terrorists-to-spill-their-secrets?utm_source=digg&utm_medium=email

How a tax haven is leading the race to privatise space | News | The Guardian https://www.theguardian.com/news/2017/sep/15/luxembourg-tax-haven-privatise-space?utm_source=nextdraft&utm_medium=email

Some Crypto-Capitalists Just Want to See the World Burn http://gizmodo.com/some-crypto-capitalists-just-want-to-see-the-world-burn-1798667463?utm_source=digg&utm_medium=email

Proactive Paranoia — Real Life http://reallifemag.com/proactive-paranoia/?utm_source=digg&utm_medium=email

Ethereum‘s Biggest Hacking Problem Is Human Greed - Motherboard https://motherboard.vice.com/en_us/article/ywwbvw/ethereums-biggest-hacking-problem-is-human-greed?utm_medium=email&utm_source=digg

The Problems With Internet Platforms Policing Hate - The Ringer https://www.theringer.com/tech/2017/8/22/16180026/charlottesville-politics-hate-speech-internet?utm_source=digg&utm_medium=email

https://www.wired.com/2017/08/the-science-and-philosophy-of-mindfulness-meditation/?utm_source=nextdraft&utm_medium=email

Why Everyone Is Hating on IBM Watson—Including the People Who Helped Make It https://gizmodo.com/why-everyone-is-hating-on-watson-including-the-people-w-1797510888?utm_source=digg&utm_medium=email

Are Index Funds Bad for the Economy? - The Atlantic https://www.theatlantic.com/magazine/archive/2017/09/are-index-funds-evil/534183/?utm_source=digg&utm_medium=email

How Fast Food Chains Supersized Inequality | New Republic https://newrepublic.com/article/144168/fast-food-chains-supersized-inequality?utm_source=digg&utm_medium=email

Why We Can’t Have the Male Pill - Bloomberg https://www.bloomberg.com/news/features/2017-08-03/why-we-can-t-have-the-male-pill?utm_source=nextdraft&utm_medium=email

Nobody Knows What Lies Beneath New York City - Bloomberg https://www.bloomberg.com/news/features/2017-08-10/nobody-knows-what-lies-beneath-new-york-city?utm_source=digg&utm_medium=email