HN user

mawise

1,511 karma

Building a healthier independent social web: https://havenweb.org

Posts62
Comments243
View on HN
havenweb.org 1mo ago

Retro-Tech Parenting

mawise
353pts245
havenweb.org 1mo ago

Retro-Tech Parenting

mawise
2pts0
www.nytimes.com 8mo ago

How Afraid of the A.I. Apocalypse Should We Be?

mawise
2pts0
github.com 11mo ago

Show HN: Haven – Selfhost a private blog instead of using Facebook

mawise
2pts0
havenweb.org 1y ago

Age Assurance and Bluesky

mawise
4pts1
calnewport.com 1y ago

An Important New Study on Phones and Kids

mawise
2pts0
papers.ssrn.com 1y ago

Negative Impacts of Smartphone and Social Media Use on Adolescent Mental Health

mawise
2pts1
optimistsbarn.substack.com 1y ago

How to Be a Techno-Optimist for Animals

mawise
2pts0
havenweb.org 1y ago

Private Social Media Doesn't Need to Worry About Censorship

mawise
2pts0
havenweb.org 1y ago

Private Social Media Doesn't Need to Worry About Censorship

mawise
4pts0
www.thebroadcastbridge.com 1y ago

Using TV for GPS Backup in the USA (2023)

mawise
2pts0
havenweb.org 1y ago

The Lie That Facebook Sold You

mawise
14pts1
havenweb.org 1y ago

What comes after Web 2.0?

mawise
1pts0
havenweb.org 1y ago

What comes after Web 2.0?

mawise
2pts1
osteophage.dreamwidth.org 1y ago

If You've Signed Up for Bluesky, You've Signed Up for Offloadable Moderation

mawise
3pts3
www.pikapods.com 1y ago

PikaPods – Instant Open Source App Hosting

mawise
19pts5
github.com 1y ago

Show HN: I built an animated 3D bookshelf for ebooks

mawise
263pts57
reactionwheelforcefeedback.com 2y ago

Reaction Wheel Force Feedback for VR

mawise
2pts0
reactionwheelforcefeedback.com 2y ago

Reaction Wheel Force Feedback

mawise
1pts0
havenweb.org 3y ago

Bluesky, Mastodon, SSB, and the Social Networks of New Protocols

mawise
5pts0
havenweb.org 3y ago

Bluesky, Mastodon, SSB, and the Social Networks of New Protocols

mawise
2pts0
about.instagram.com 3y ago

Threads: A New Way to Share with Text

mawise
2pts1
www.rssboard.org 3y ago

RSS Autodiscovery (2006)

mawise
145pts46
www.rssboard.org 3y ago

RSS Autodiscovery

mawise
2pts0
snarfed.org 3y ago

Translating/bridging across multiple protocols and identities (via federation)

mawise
32pts3
developer.tbd.website 3y ago

The Practicality of Decentralized Identifiers

mawise
2pts1
havenweb.org 3y ago

Private Comments, or Why I’m Down on Webmentions

mawise
1pts1
havenweb.org 3y ago

Private Comments, or Why I’m Down on Webmentions

mawise
2pts0
aaronparecki.com 3y ago

OAuth Support in Bluesky and at Protocol

mawise
3pts1
support.google.com 3y ago

Google Analytics opt-out browser add-on

mawise
4pts0

I've been using .lan, referenced in rfc6762[1] as a good alternative to the multicast .local

We do not recommend use of unregistered top-level domains at all, but should network operators decide to do this, the following top-level domains have been used on private internal networks without the problems caused by trying to reuse ".local." for this purpose:

      .intranet.
      .internal.
      .private.
      .corp.
      .home.
      .lan.

[1]: https://datatracker.ietf.org/doc/html/rfc6762
Your ePub Is fine 1 month ago

Sharing my experience as a tinkerer, sideloader, and recent Kobo owner.

I used a Kindle for ages, always in airplane mode and only sideloading content. Honestly, it was a pretty good setup.[1] But it seemed like it would be harder to setup this way on newer devices, so when mine finally failed, I got a Kobo Clara BW. I was thrilled I could boot it up in "sideloader mode" and not even register it or enable wifi.

I noticed poor typography on my epubs, learned about converting to kepub so I did that (which helped). It was a familiar flow to what I was used to converting to azw3 for the Kindle. My remaining typography gripe with kepubs is that it treats a word+em-dash as a word for inserting space in full justification. Em-dashes generally don't have spaces on either side, this often looks like a space has been inserted only to the right of the em-dash.

I went down the rabbit hole of NickelMenu and other readers including KOReader and Plato, and even tried (and mostly failed) to vibecode my own opds client app. (because KOReader which has one built-in felt overwhelming)

My current sense is the device feels so much more like it is mine. I have much more flexibility to tinker with it. It is not as polished as the Kindle and the Adobe rendering feels stupid, but that's also a sharp edge that only the side-loading community will hit, most of whom use Calibre which can auto convert to kepub for them. Everyone else is buying books from the Kobo store and getting them delivered as kepubs.

So in the end, I'm a big fan of the Kobo devices.

[1]: Except you cannot remove a wifi password if you aren't in range of that wifi signal. I had a rude experience when my two-year-old was fiddling with my Kindle at my in-laws' house and turned on the wifi where there was still a saved credential. An update triggered immediately and I was frustrated for days that everything in the UI changed.

I consider myself pretty pro-privacy, but there is so much dragnet surveillance and legitimate breaches of the fourth amendment that I have a hard time getting up in arms over a company complying with a valid search warrant that is scoped to three hard drives (and which required law enforcement to have physical possession of the drives to begin with).

This is so much more reasonable than (for example) all the EU chat control efforts that would let law enforcement ctrl+f on any so-called private message in the EU.

The article goes back and forth between bloggers who "are doing well" (ie: making money) and efforts that are non-commercial. It comes across as asking humanity to put more effort into writing and publishing in a non-profitable space while the blogging incentives are profit. I still think the unexplored space for blogging (and the LLM-proof space) is _private_ blogging--for friends and family. But maybe Facebook killed that space off, who knows.

Slow social media 10 months ago

Um, I'm building this? [1]

The one key element I added was privacy. If your posts are private to your social group then there is no mechanism to try appealing to a broader "viral" audience. Also--if it is decentralized then the company (or person in my case) building it can't change their mind and start selling your data/eyeballs.

I have a LOT of thoughts in this space. Lots of people think they want some sort of healthier social-media alternative, but we're fighting against systems that are so finely tuned engagement monsters that is hard compete to protect your attention and time.

Herman- I'll reach out to you by email!

[1] https://havenweb.org

Yeah, I don't really grok the focus on MF2 given the wide adoption of RSS/Atom, but the social reader concept isn't one I've seen anyone else advocating for. It also suffers from the same spam problem of anything else that allows public submission of content. I've been exploring it more in the context of _private_ blogging were you already have a layer of access control.

Is there a Github API for creating issues? I also maintain a free, open-source app and would love to make it easy for a crash to give users a button that opens a Github issues form--allowing users to see what crash data is populated and submit it if they want.

Oh cool, it's like RSS consumption for video content (I think). I worry that since it isn't using blessed APIs it would get shut down by the platforms if it gets much traction. Also "trust me instead of them" can be a tough sell to the privacy-focused crowd. I'd love something that makes it trivial effort for the creators to directly publish on more open platforms--more like RSS publishing for video content. But youtube gives you discovery and a cut in the ad revenue, so I'm not sure how to get the incentives to align...

It's funny; as I've been working on Haven[1], one of my guiding lights is what Facebook _could have been_[2]. To that end the opening section is really inspiring. This is describing a world where digital tools enhance your friendships. I think that's still possible and still a worthwhile goal--I just don't think it can be done by an entity with a corporate incentive structure. Those incentives will always tend towards enshittification[3].

[1] https://havenweb.org

[2] https://havenweb.org/2022/11/02/facebook-lie.html

[3] https://en.wikipedia.org/wiki/Enshittification#

1M Users 2 years ago

I've got to chime in here, because of how much this overlaps with the project I've been working on called Haven[1].

A lot of these problems go away with a decentralized/open-source private model. If your posts aren't public then there is no spam. If everyone runs their own node of open-source (or better yet: open-protocol, ie RSS) software, then there is no centralized entity able to have incentives of profiting off the platform.

Information propagation speed is a good call-out as dangerous. Even with all the spam/shilling/trills removed, it still leads to the girl who's having a great time on her snowboarding trip until she posts pictures on Instagram and drops into a foul mood because not enough people immediately liked her posts.

I'd love to connect and share thoughts, feel free to reach out[2]/

[1] https://github.com/havenweb/haven

[2] https://havenweb.org/contact.html

I've been working on Haven[1] as an open-source self-hostable alternative to give control back to people. I actually wrote a blog post about how the move from "see what your friends/family are doing" to "just keep scrolling" was a pretty blatant bait-and-switch[2]. I think any alternative will fail in the same ways as Facebook has unless there are different incentives. I'm hoping that by making Haven open source and decentralized there won't be a path for me to make money off of it (beyond maybe hosting fees?) if it gets broader adoption.

[1] https://havenweb.org

[2] https://havenweb.org/2022/11/02/facebook-lie.html

I ran into this building search for a family tree project. I found out that Rails provides `ActiveSupport::Inflector.transliterate()` which I could use for normalization.

What about a cross between IPFS/Nostr and RSS? RSS (or atom) already provides a widely-adopted syndication structure. All that's missing are signatures so that a middleman can re-broadcast the same content. Maybe with signatures that's really reinventing SSB[1]. But if we think of the network in a more social sense, where you're connecting to trusted peers (think: irl friends), maybe the signatures aren't even that important. All that's left then is to separate the identifier for the feed from the location--today those are both URL--so you can fetch a feed from a non-authoritative peer.

[1] https://en.wikipedia.org/wiki/Secure_Scuttlebutt