Show newer


Okay thank you!

I'll get right on that. SDF has always been like a badge of honor so it just makes more sense to me that it be on my resume as available here instead of anywhere else.

Thanks again!


tallship boosted
tallship boosted
Really, what I want to say here is shame on #Amandine_Le_Pape and #Matthew_Hodgson, the BDFLs and creators of Matrix, for even allowing #Element to be available in the Google Playstore - Is the Irony lost on you?

But I can't. I understand. Because it was, at the time, the only vehicle they could use to popularize Matrix.

But that time is passed, #Google, #Faceplant, #InstaSPAM, #Whassup , #Twatter, and many others are hemorrhaging profusely; exsanguination through the mass panicky evacuations of its userbase to some nobler, loftier, fairer and deserving places on the Internet, so don't fret folks, this is a sign of very good things bourne out of the Evil that are the monolithic silos that have stolen, packaged, inventoried, and distributed your identity and privacy.

These types of occurrences are merely the deadly grasping at straws, or anyone on the surface of the water who tries to reach out to these drowning, diabolical industries - make no mistake, they are the person drowning who will pull you down with them if you accept their apologies or peace offerings.

Go somewhere else away from them, don't worry, and be happy.

In the meantime, install #Element or #Schildechat at F-Droid and be done with any and all of those text and video chat systems that the evil silos gave you, like the witch, offering the poison apple.

Matrix does it all and respects your ultimate privacy in the process.

Matrix is used, and indeed its use is ebraced by the governments and military of #France and #Germany - BIG TIME, just one of those governments inked a deal with Matrix in the largest ever financial communications contract of its kind (Yes, EVER!).

It's also used by the U.S. Government - because they need to have that which they seek to deny you.... Complete and total privacy in private, #encrypted #communications.

Here are the stated beliefs which form the principles upon which #Matrix is founded. ***I too, believe in these things***:

We believe:

* People should have full control over their own communication.
* People should not be locked into centralized communication silos, but instead be free to pick who they choose to host their communication without limiting who they can reach.
* The ability to converse securely and privately is a basic human right.
* Communication should be available to everyone as a free and open, unencumbered, standard and global network.

So, when you #believe in perverse, subversive ideals such as those, well.... Of course they're going to #cancel_culture you and do their best to #deplatform you Just like all of the others recently, and this my friends, this is how a paradigmatic shift in culture is spawned.

Google no can haz #Cheezburgerz! 🍔

#tallship #Vger #privacy #security #encryption

tallship boosted

If you're looking for functionality, then #Friendica comes the closest to the base functionality that #MySpace and Faceplant capitalized upon.

I think that perhaps @hamishcampbell days it best with respect to the #addiction factor - #Dopamine is a powerful thing - just look at the having industry and the... Well, just consider that.

#Diaspora is not an #ActivityPub based system as of this juncture in time, and regarding the differences between how a post looks between say, Friendica and #Pleroma, or even Pleroma and other #Mastodon-esque platforms like #Misskey, etc., There are differences between all of them related to the features that one supports, and another doesn't.

This is a positive, market based incentivization for innovation.

Things will continue to evolve as long as there is interest in a platform and new ones come along all the time - there's no reason, for example, why #Planetary can't support its native #SSB while at the same time offering optional #Matrix protocol and ActivityPub integration, affording its users with a measure of interoperability within those spaces.

Looking back over just the last six months is quite encouraging when you consider the interplatform interactivity that users can take advantage of between projects like #PeerTube, #Pixelfed, #Funkwhale, #Lemmy, and the so-called microblogging platforms in the #Fediverse like Misskey, Mastodon, and Pleroma; while Friendica often serves as a bridge to those using Diaspora protocol and even the largely defacto deprecated #OStatus.

I think the time to begin migrating from the monolithic silos is **yesterday**, and continuing into **tomorrow**.

If all that someone wants is to communicate with their highschool buddies and neighbors, perhaps the best choice is indeed #Faceplant?

The Fediverse implies many different emerging and continuously maturing platforms that speak an assortment of federating protocols - not just ActivityPub, each with their own strengths and weaknesses, and with development being community informed and inspired.

Anything that resists that last very important point (community driven), simply gets forked, and that to happens all the time - success is based on merit.

What were really taking about here isn't which platforms are ready at this moment for the non-apathetic, concerned userbase to begin their egress from the monolithic silos, but rather, how we can facilitate the ingress of onboarders in becoming comfortable using rapidly evolving platforms that obviate #Faceplant, and #Reddit, and #YouTube, and #Twatter, and #InstaSPAM, and #Whassup, and #Pinterest, and... ad nauseum.

I hope that helps! :)

Remember, You can haz #Cheezburgerz! 🍔

#tallship #Vger #privacy #security #encryption



Also this, by him, in that same thread:

If someone starts a project to create a truly open Sync server for Chromium then I would consider packaging it for Slackware of course. The Brave project has built a Sync server for their Chromium-based Brave browser:


But like Mozilla's original Weave sync server, I would like for a Chromium Sync server to be written in such a way that it can be self-hosted. I only trust myself.


As AlienBOB points out in the article below, you merely need to set GOOGLE_API_KEY, GOOGLE_DEFAULT_CLIENT_ID and GOOGLE_DEFAULT_CLIENT_SECRET variables in your .profile or .bash_profile and you're good to go with their public key.

No biggy, and you can still use your 32 bit Chromium packages just like before (there's a lot of people running 32 bit systems still)

I was just informed by someone that they can no longer finger for my .plan here at SDF.

I tried it myself and it now appears to only work when ssh'd into an SDF server, returning nothing from outside.

Geez. That's been on my resume for a long time. Does anyone here know how long has the port has been blocked? I know it was working as late as 2019 coz it came up in an interview.

tallship boosted
Matrix protocol is enjoying a huge groundswell in its adoption. This is however, somewhat independent of the fueled kneejerk reactions of people - not so much by virtue of their realizations of having been commoditized, but rather, an opportunity for them to simply venture onto better, greener pastures.

#Matrix is not without barriers to onboarding, but neither is #OpenPGP where email is concerned - one either takes a few minutes to understand the basics of how a newer platform functions from the user perspective or they remain commoditized - many folks find that kind of apathetical complacency no longer acceptable.

I thought I'd share a bit of balanced observation here, and although it is not without its subjectivity, it is pretty spot on:

FOSS doesn't care if you adopt or use it. There aren't necessarily any budgets or a Board of Directors to answer to, and it can exist lying intact dormant, until someone else comes along to pick up the torch. If it is useful, someone will use it. If it threatens to #disrupt some aspect of the #proprietary, #closed_source world, it still doesn't care.

FOSS projects can be freely hosted or as part of a sponsored endeavor of big venture capitalists - it still doesn't care and that's why it is such the great disruptor and bringer of #democratization of computing and communication to the once insignificant and downtrodden #fodder of the #monolithic_silos, users (participants) who willingly traded their #dignity for a friendly face, like the yummy children boiling in the witches cauldron inside the gingerbread house.

It is common knowledge that these #monopolies are now understood as having their existence facing that of #extinction.

You can't legislate #FOSS, anyone can do with it what they wish to, whether it is legal under your country's regime or not. You can throw people in jail, but guess what, FOSS is still #free, it still exists, and it still doesn't care.

I hope that helps! :)

#tallship #Vger
Thanks for the linked article goes to @garritfra
You can haz #Cheezburgerz! 🍔

tallship boosted
@dzwiedziu @apps

Yes it's a very common occurrence for folks to associate Mastodon as the Fediverse itself - I myself did this initially, and truth be told, it wasn't all that far from accurate.

Initially, GNU Social was one of the earliest implementations of a server platform heralding the beginning of the Fediverse - based on the OStatus protocol, then came ActivityPub and other server platforms, Mastodon actually doing the most for the Fediverse as far as it being accessable and pretty (with that really cool logo they have of the happy elephant).

Diaspora was an early Fediverse player with promise, but with it's own protocol so it is still rather overlooked and doesn't incorporate ActivityPub out of the box, instead relying upon its own federating protocol (But Friendica bridges that Gap, so I can actually do some stuff like interact with folks on Diaspora from within Fedilab... to some degree).

Most platforms initially tried to adopt the use of both OStatus and ActivityPub but both Mastodon and Pleroma have since dropped OStatus. I think otther platforms that don't have ActivityPub integration will soon start to lose their viability, as OStatus appears to be on it's way out and replaced, in large part, by ActivityPub.

Where I believe the biggest differences can be made, is in the support of "Fediverse" in general, by applications, rather than particular server platforms, and Fedilab goes a long way toward that goal.

Of course, supporting more platforms means more development as well as a larger APK, so there's that ;)

As far as development, however, contributions to the project can be made here and will certainly make a HUGE difference in the longevity, as well as keeping development aggressively active :)

They don't push this, as the folks on the Fedilab dev team are rather modest, but I do, so I recommend that we all give something, whatever we can, however much or little, because every little bit helps, and in the end, if benefits us "the users", most of all.

Developing #Fedilab has been mostly a labor of love and for the #Fediverse itself, and they've had to brave some pretty sickening haters due to their stance on keeping free software free (as in Libre), as things have turned out pretty much as they are supposed to with the users themselves and the server admins deciding for themselves what kind of view into the Fediverse they want, and that's where those choices need to be made, not in applications that cripple the freedoms that even those we most oppose, and perhaps despise, should themselves enjoy.

Here's the link where we can all contribute to the continued development of Fedilab and the rest of the Fediverse suite of applications and services that they continue to improve:
tallship boosted
Great news, and it would be a simple thing to put support for gopher:// URIs back into browsers the same way that ftp:// still is.

Nevertheless, this is a welcomed announcement! 🚀

#tallship #Vger #FOSS #ipfs #decentralization

You can haz #Cheezburgerz! 🍔

tallship boosted
Out of concern for the health and safety of our organizers, volunteers, and
the wonderful SCALE community — and in line with recent “Stay at
Home” orders issued by the #California State government — we sadly will
not be holding SCALE in any capacity this year.

We will miss seeing everyone this year, but cannot wait to come back March
2022. Be sure to lookout for more updates from us soon.

If you are missing our #SCALE content in the coming months, you can find
previous years talks on our channel:

Take care of yourselves and we will see you safely in Pasadena in 2022.

#tallship #Vger #Linux #Wuhan
I no can haz #Cheezburgerz? 🚫

tallship boosted

That's not actually a subdomain. It's merely a hostname.

Years ago companies like cPanel bastardized the term to describe the deployment of additional virtual host websites within the same DNS zone and origin, and it became the popular way of describing adding yet another host record to a domain.

It's not a subdomain any more than having the hostname "www". Other popular hostnames, by convention alone, are "mail", "webmail", and "ftp", among many others.

All you did was create a single A record for a hostname in a DNS zonefile and pointed it to an IP address.

To create a subdomain, one MUST "delegate" "Authority" to a child zone with two or more NS records (except in very special circumstances noted below) , referring anyone who asks to the DNS nameservers for that child, which in turn will return the results for that child domain.

If you're scratching your head, it's very commonplace so think of it like this:

SLD.TLD is administered by Joe at the university. Mary is the administrator for the entire math department on campus.

Janet runs the mathlab.

Joe delegates authority of the subdomain math.SLD.TLD to Mary with the two NS records pointing to the DNS servers she administers, and in her zonefile Mary delegates the subdomain 'lab' to Janet in the same way.

Janet has four machines in her lab and assigns an A record for each of them. Those hosts are:

www.lab.math.SLD.TLD (the webserver)

mail.lab.math.SLD.TLD (the mail server)

janet.lab.math.SLD.TLD (Janet's workstation)

student001.math.lab.SLD.TLD (workstation)

Janet also installs a NextCloud server and a WriteFreely instance on the webserver, and assigns the following hostnames corresponding to those websites with A records pointing to the IP address of the webserver (www) where she had created those virtual hosts in the Apache or Nginx config file:



"TLD" is the Top-Level Domain under the root, which is expressed as ".", but usually assumed without having to use it syntactically in all notation. The Top-Level Domain is administered by the Internet Registry.

"SLD.TLD" is the Second Level Domain name registered by Joe for the university under the Top-Level Domain "TLD" at the registry.

math.SLD.TLD is a "3rd level domain", a subdomain of SLD.TLD, the "Authority" of which, was delegated to Mary by Joe.

lab.math.SLD.TLD is a "4th level domain", a subdomain of math.SLD.TLD, the Authority was delegated to Janet by Mary.

I personally use the shorthand, 3LD and 4LD to keep things easy to read.

Everything else (www, mail, janet, student001, nextcloud, and writefreely) are just hostnames. Period.

The webserver listens on its IP address for three hostnames to answer to, and serve pages via HTTP protocol from the corresponding virtual hosts configured for that server. Those three virtual hosts are:




These three hostnames are virtual hosts on a webserver, configured as "VirtualHost" containers (Apache) or Server Blocks (Nginx). They are not subdomains by any measure, but do exist in the 4LD (subdomain) of lab.math.sld.tld.

Operationally, everything is case insensitive. I only added the caps for emphasis. Most of everything is converted to uppercase by the DNS Servers, however. The reasons for this goes back to the original Jeeves server in the mid eighties.

So the next time some one click install, self-professed so-called *webmaster* says that hostnames are subdomains, you'll know that they're full of shit and don't know what the fuck they're talking about.

I did blur the distinctions between zones and domains for the purposes of this discussion, in order to make things easier to digest. If you want more information you can consult the Internet RFCs, which are the definitive authoritative source, but a great online resource that is an easy read is:

Although this hasn't been updated in about 15 years, I would also highly recommend the old gold standard O'reilly book, DNS and BIND, by Cricket Liu and Paul Albitz, the latter of which is one of the original developers of BIND:

Having worked with DNS since 1985 when we officially deployed it on the ARPANET/MILNET, I've seen a lot of confusion and misrepresentation surrounding this simple, yet core concept of internetworking.

There have been very few changes in the core concepts of DNS since Jon Postel and Paul Mockipetris published the first RFCs on it, mostly relating to the addition of TLDs and then moving the .ARPA TLD to be used only for reverse DNS in the zone. Paul also wrote Jeeves, the very first DNS server, that we continued to use until about 1987 or so.

I should mention that there is the notion of a 'pseudo' subdomain, with it's own $ORIGIN contained in the parent zonefile, but I won't go into that here and suffice it to say this this not what you did when you thought you had created a subdomain.

The only use case I've ever seen for pseudo subdomains are when infra is being built but the AUTH nameservers haven't been fully deployed yet - like if a school needs to delegate Authority but they're infrastructure didn't have the resources for additional nameservers.

This way, using include files, the administrator of the child domain can affect changes within only their zone, and permission is usually granted so that they can use sudo to affect a reload of named (or whatev DNS server they're using) without having to involve administrators of the parent domain.

You'll see this in things like school districts where the budget can't accommodate the costs of additional DNS servers for each elementary and highschool, as an example, so the tech person at those schools can deploy and retire the ever changing inventory of computing devices at the satellite campus.

In any case, the first link I left you above includes an accurate treatment on how to do just that.

It's certainly NOT what a cPanel server or any web hosting control panel is even prepared to do - they just add new A records for the new hostnames.

I hope that helps! :)


#tallship #Vger #DNS #subdomains #zone #BIND #Jeeves #hostname #recursion #resource_record #delegation #Authority #ORIGIN #SysAdmin #named #virtual_host #web_server #apache #nginx #server_block
tallship boosted

Simple. Just install NextCloud on the VPS and when you edit your existing Nginx conf file you add in the server block for the NextCloud server.

Say, one server block for the hostname wf.mybox.tld (already existing) and one new server block for nc.mybox.tld.

If you're running Apache, same thing, except they're called VirtualHost containers.

Create the new A RR and if you have IPv6 an AAAA RR pointing to the servers IP for the hostname nc.mybox.tld. you know how to do this because you've already done the DNS for the wf virtual host already, and you've made a server block for nc already on your home LAN.


$ sudo systemctl reload nginx

Done. Easy Peasy! 🤘😎🤘

Depending on what other services you want your NextCloud server to deliver you might need to open more ports on your firewall with UFW, but you already have 443 open for wf so it will also work for nc.

You can add as many other websites and services as you have resources for too 🙂

You can even install a Pleroma server, but the server block for that will be configured as a reverse proxy because it runs as it's own daemon on another port.

Where your at at it, you might as well install a local SMTP and an IMAP server for mail, but that you're kewl with editing your DNS zonefiles, and a caching BIND server like named to handle all the local requests, and pointy your
/etc/resolv.conf to it on order to speed things up a little bit.

You'll need at least three more DNS RRs, an A (and possibly an AAAA) RR, an MX RR, and couple of TXT RRs for SPF and DKIM.

For those last two records there are plenty of online tools to automatically generate, for example, your Domains SPF record.

Again, Easy Peasy.

All instructions above assume you're running Debian GNU/Linux. Frinds don't let frinds run ewb00ntew. But Slackware, Arch, Gentoo, SuSE, and any of the BSDs are excellent platforms too.

You can haz #Cheezburgerz! 🍔

I hope that helps! :)

tallship boosted
@PonyPanda @Oblivia @ethot @screamingfrog

Here's that landing page I mentioned:

h/t to for doing such a fantastically beautiful job on it. Having things that look really nice goes a long way toward making n00bs feel that something is accessible :)

tallship boosted
FOSS and Privacy as Standard Method series:

Here's a little sump'in sump'in. A bit of light reading that helps explain how FOSS can have a vested interest as your servant rather than packaging you as its product, as most closed source proprietary platforms do:

#tallship #Vger #FOSS #open_source @OpenSource #Cheezburgerz! 🍔
tallship boosted
tallship boosted
tallship boosted
tallship boosted
I created a little landing page to help onboard normal people to the Fediverse.

The goal is not to list every single server, but rather direct newcomers to a small handful that would broadly appeal to most people (if I didn't include your server, sorry, nothing personal). This will hopefully make it easy for people who know nothing about the Fediverse to quickly choose a server that generally suits their moderation preferences without being overwhelmed by the number of options.

Show older
Mastodon @ SDF

"I appreciate SDF but it's a general-purpose server and the name doesn't make it obvious that it's about art." - Eugen Rochko