mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#ipfs

0 posts0 participants0 posts today

#discord IS LITERALLY THE PROBLEM!

I'm shure fecking #dread has better moderation and I'd rather use #MicrosoftTeams + #Slack cuz those at least have proper #moderation tools.

  • And I'd rather subscribe to the #LKML and see my inbox getting hosed than using any shitty #SaaS!

Case in point: I'd rather #SelfHost all my comms infrastructure than to ever use something like Discord or any other #GDPR-violating SaaS that is just enshittification.

I'd rather recommend people to instead choose a tool that does everything but horrible to go with multiple smaller & good tools

Check @alternativeto and @european_alternatives for options.

I just read that nps.gov erased Harriet Tubman from a page about the Underground Railroad. I want not only to #archive copies of websites, but to use #cryptography to prove that this was the content fetchable from the real page at a date in the past. #provenance Why aren't there FAQs about how to do this already? I've just seen sciop.net which appears to be using both #BitTorrent and #RDF to advantage; and #ArchiveTeam appears to be doing distributed fetching at scale with their ArchiveWarrior thingy. But how should anyone trust that I don't tamper with the pages I fetch and archive? Or what if I just want free backups, so I pass off my photo archive as part of #memoryhole 'd DEI policies? And where's #ipfs or #dat or #hypercore ?

Here’s a short guide on how I host websites and single-page applications on the InterPlanetary File System (#IPFS). It covers running a node, #pinning data, #HTTP gateways, the InterPlanetary Name System (#IPNS), and how to get memorable URLs using #DNSLink.

(I've recently published some #browser #tools and #demos on the IPFS and thought you might be interested too. Feedback welcome!)

ipfs--howto-data0-one.ipns.dwe

ipfs--howto-data0-one.ipns.dweb.linkHow to host static websites on IPFS

I've published another #browser demo on the #IPFS: a web-based mail user agent prototype (from 2021).

"We could build something better in a just weekend! And it'd even fit into the memory of a C64!" – That's what I told a friend when they complained about today's slow, bloated #webmail #frontends. And I did, in… let's say an extended weekend:

A modern, mostly-featured yet minimal webmail prototype weighing in at just ~40 kB gzipped (incl. all #HTML, #JavaScript, #SVG)

webmail--demo-data0-one.ipns.d

Screenshot of the app
webmail--demo-data0-one.ipns.dweb.linkModern but minimal (40kB) web mail app demo

Now that I've got the #IPFS #hosting dialed in, I'm going to (re-)publish some other #browser #demos:

**MP4 Terminal**: An experimental meta tag editor for .m4a audio files with a nerdy amber #CRT #terminal style interface

I built it in 2023 to explore the #FileSystemAccessAPI which unfortunately still is #chromium-only. Still happy with the user interface though ;-)

mp4--terminal-data0-one.ipns.d

Screenshot of the app
mp4--terminal-data0-one.ipns.dweb.linkOld-Terminal-Style MP4 Tag Editor and Audio Player

One of the problems of #IPFS is that they never decide if they want to be "cool" or useful. The result is that their publications and products are riddled with buzzwords and self-compliments, but often forget the goal of IPFS.

The typical goal of IPFS is to be able to send a reference to content, instead of a reference to a server. But to see the *real* goal we have to think of **why** we do that.

One reason to send IPFS is to ensure that the content you get is the right one. If (1/7)

63% of my followers are #discoverable, only 34% are #indexable (by #searchengines). Most new followers are still coming from my prev. #mastodon #instance, #fosstodon.org. Might be the local timeline, it was way more interesting/less random than here.

Want to know about your followers, too? Check out this tool I’ve built (hosted on the #IPFS). It’s a non-commercial side project; not collecting any data – simply sharing what I’ve built:

fedi--followers-data0-one.ipns

(Last plug for a while, I promise)

Screenshot of the app
fedi--followers-data0-one.ipns.dweb.linka privacy-friendly fediverse followers explorer as local-only static web app.

My esteemed followers, you have posted a total of 375,809 statuses to the #fediverse. 22% of you have posted in the last 24h. You are a chatty bunch! ;-)

Check out my new #sideproject: *fedi-followers*. A privacy-friendly fediverse #followers explorer as #localonly #staticwebapp, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

fedi--followers-data0-one.ipns

Screenshot of the app
fedi--followers-data0-one.ipns.dweb.linka privacy-friendly fediverse followers explorer as local-only static web app.

I've built a thing.

Sometimes my follower count seemingly fluctuates at random. To understand why, I dug into the #MastodonAPI and created "fedi-followers":

A privacy-friendly #fediverse #followers explorer as local-only static web app, decentrally hosted on the #ipfs. See who's actually following (and unfollowing) you over time and much more.

fedi--followers-data0-one.ipns

Screenshot of the app
fedi--followers-data0-one.ipns.dweb.linka privacy-friendly fediverse followers explorer as local-only static web app.