@manlycoffee@techhub.social
@manlycoffee@techhub.social avatar

manlycoffee

@manlycoffee@techhub.social

This profile is from a federated server and may be incomplete. Browse more on the original instance.

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

If you are on Mastodon, or on any other Fediverse platform, your account will have an actor ID.

An actor ID is just a web URL.

On Mastodon, your actor ID is of the form:

https://<domain name>/users/<username>

Now, because an actor ID is a web URL, the following is a perfectly valid actor ID (as long as it represents your account. If it doesn't, then it's not a valid actor ID, associated to you):

https://<domain name>

Yes, you read that right! The above can indeed be a perfectly valid actor ID.

So question for you:

let's say your actor ID is just "https://" followed by your domain name, what would you choose as your domain name and username.

Comment below 👇

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

It's increasingly beginning to feel like a "TikTok for the Fediverse" is not something people want.

Or maybe I'm asking the wrong questions.

#Fediverse

manlycoffee, to random
@manlycoffee@techhub.social avatar

Mastodon doesn't want quote boosts because of some weird concern about harassment, but yet, doesn't have comment control.

If someone comments something idiotic, I have to resort to ad-hominem attacks to shut them up, and then blocking them afterwards

manlycoffee, to random
@manlycoffee@techhub.social avatar

So, turns out, with the AT Protocol, deletion is not really a thing, in the same way that deletion in Git is not really a thing.

Could this mean that I won't be implementing the AT Protocol?

I'm already leaning no.

manlycoffee, to threads
@manlycoffee@techhub.social avatar

The fear and reaction regarding the possibility of Meta enacting "embrace, extend, extinguish" of ActivityPub and the rest of the Fediverse is starting to feel a lot like a self-fulfilling prophecy.

"I can't interact with my friends on Threads from my server that has Threads blocked. I guess I'll just join Threads so that I can finally interact with them on Threads"

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

I started a Discord server to discuss the Fediverse, for those of you who prefer to talk about the Fediverse over chat. https://discord.gg/spTSf8VJ4u

@fediversenews

#Fediverse #Discord

manlycoffee, to meta
@manlycoffee@techhub.social avatar

I have previously expressed how much I am against the EEE argument, but considering that there is this linked post from someone who actually has experience with working at a company that does engage in EEE, I guess I should check my opinions about EEE at the door, shut up, and hear out the concerns from people.
https://mas.to/@andthisismrspeacock/111588768178247161

#Meta #BlockMeta #BlockThreads #AntiMetaFediPact #Fediverse

manlycoffee, to random
@manlycoffee@techhub.social avatar

I will never vote for a politician who attacks the BoC for raising interest rates in the face of higher than 2% inflation rate.

The Bank of Canada has one job: keep inflation at 2%.

They only have one tool for the job: monetary policy, which includes the overnight lending rate.

Yelling at the Bank of Canada for interest rates is like yelling at a tree for having its leaves fall during autumn. They can't help it.

It's also the government's job to manage inflation rate, by keeping a close eye on the economy.

Several things that lead to inflation that we're seeing today:

  • high housing costs
  • supply-chain issues
  • uncontrolled immigration, even in the face of inflation

Inflation doesn't only mean more money in circulation; it also means market can't meet demand.

So combined with supply-chain issues, red tapes behind housing starts, and high immigration all lead to the inflation that we are seeing today.

Governments should have been on top of this.

#canpoli

manlycoffee, to random
@manlycoffee@techhub.social avatar

When I was young, when I reposted things (retweet on Twitter, and Reblog on Tumblr, etc.), I reposted them because I enjoyed viewing that post.

Nowadays, I would say 40% of the stuff that I repost, I repost because I was about to act like a "reply guy" to the author of the post.

I guess my motivation for doing this is a form of substitution.

That is, ditch my bad habit of being useless in someone's comment section, and instead give the author a little bit more exposure to someone who might be more suited at providing a useful response.

manlycoffee, to random
@manlycoffee@techhub.social avatar

I just read "Surgeons Should Not Look Like Surgeons" by Nassim Taleb.

Nassim Taleb describes a competent surgeon as someone who looks rough.

For programming, it's the opposite, I find https://medium.com/incerto/surgeons-should-notlook-like-surgeons-23b0e2cf6d52

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

The whole idea of BlueSky supporting nomadic identities but the rest of the ActivityPub (plus other stuff) Fediverse being unable to do so is such an oversold idea.

A new service using ActivityPub behind the scenes (and not the AT Protocol) can absolutely support nomadic identities, even if the service doesn't treat a whole website as the actor.

It will still use did:plc, same as AT Protocol (BlueSky), but once done so, an application that understands how to work with did:plc can dereference an actor based on the DID.

That said, an existing service will simply not be compatible with this idea, without changing how it operates.

manlycoffee, to random
@manlycoffee@techhub.social avatar

A company claims to have achieved Twitter scale, in record time, when they implemented their Mastodon clone.

Lots of impressive claims, and I'm now highly invested in seeing them release their RAMA platform.

If they did genuinely achieve what they claimed to have achieved, then kudos to them. I have a lot to learn.

Especially their—what I'd argue unconventional—approach to data storage, that is to favour an event-driven, steam-processed architecture.

Most people graduating fresh out of college would typically go with a CRUD approach, reading and writing data into a relational store, and managing business constraints using database transactions.

Heck, let's forget college grads; even people like me would go with the CRUD approach.

Does the CRUD approach scale to Twitter-scale? No way https://blog.redplanetlabs.com/

manlycoffee, to random
@manlycoffee@techhub.social avatar

Feels like TypeScript is meant for large teams, and ironically, these large teams still end up royally fucking things up.

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

So far, it seems like people don't really care whether their Fediverse experience is on a multi-tenanted setup.

Putting it in my own words: they don't care as long as they don't have to put up with weirdos.

Too early to tell about the whole multi-tenanting deal.

#Fediverse

manlycoffee, to webdev
@manlycoffee@techhub.social avatar

Am I missing out by using SSH tunnelling to expose an application on my laptop to the Internet, for development purposes? #SSH #Networking #WebDevelopment #WebDev

manlycoffee, to random
@manlycoffee@techhub.social avatar

I think I've said this before, and I will say this again: something like TikTok is meant for the Fediverse

manlycoffee, to javascript
@manlycoffee@techhub.social avatar

In JavaScript/TypeScript, what is the current trending idiom with "raising an error"?

The throw keyword makes me feel angsty.

Are people still using that?

#JavaScript #TypeScript #NodeJS #WebDevelopment #Programming

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

Earlier I asked what Fediverse software doesn't respect JSON-LD.

That question was grounded in the fact that I wanted any Fediverse software that I write to be fully compatible with almost any Fediverse software.

Honestly, I just gotta bite the bullet and focus mostly on proper ActivityPub software, that uses proper JSON-LD.

#JSONLD #ActivityPub #Fediverse

manlycoffee, to programming
@manlycoffee@techhub.social avatar

Question for people who have written hypermedia APIs or any API that link to other endpoints on the same backend:

what patterns have you used, or are currently using?

My biggest concern is, if an endpoint needs to change, how do I ensure that the links in the API responses also reflect the change in the endpoints?

#api #backend #BackendDevelopment #SoftwareDevelopment #Programming

manlycoffee, to random
@manlycoffee@techhub.social avatar

I feel like posting some seriously dank Twitter roasts that I saw on the Threads app

manlycoffee, to random
@manlycoffee@techhub.social avatar

Rent control was a really bad idea.

A maximum rent increase wasn't grounded in reality, and instead based on the opinions of a central planner. Landlord goes behind on maintenance, and there is a severe diminished incentive for the market to provide rental housing to would-be residents.

Here's what I propose instead.

If a landlord wants to raise rent, and the tenant is unable to afford the new rate, the landlord will cover the difference up to a set amount.

It will go like this:

  • government has a max rental increase
  • landlord wants to raise it higher
  • tenant refuses to pay more than that
  • landlord proceeds with ending the tenancy, but will be required to pay the difference between what they are allowed to increase, and what the landlord wants to charge for up to a year
manlycoffee, to programming
@manlycoffee@techhub.social avatar

In databases, in order to "work smart, not hard", you resort to data normalization.

And I think when dealing with in-memory data, you can take advantage of this idea as well.

Like, once you've stored some value in memory (could be a whole structure), you don't have to also update a materialized view of that value.

What would that term be called?

Sill normalization?

#programming

manlycoffee, to fediverse
@manlycoffee@techhub.social avatar

Ideally, at the bare minimum, ActivityPub should have explicitly specified the "shape" of JSON (not JSON-LD) documents.

For example, the spec could have stipulated:

"An Actor document MUST contain the following fields, and MAY be extended via JSON-LD contexts"

And then also stipulate:

"Clients SHOULD expand incoming JSON-LD documents".

This way, applications could skip the expansions step for significantly large subset of the Fediverse.

This is important because not all environments (languages, runtime environemnts, etc.) have the luxury of expanding JSON-LD documents.

manlycoffee, to random
@manlycoffee@techhub.social avatar

A lot of people were upset at Linus Torvalds for posting this back in 2012, but I actually agree with him here.

Shipping a bug, and blaming the user is unacceptable.

manlycoffee, to random
@manlycoffee@techhub.social avatar

So, turns out, there are "agents" on the Internet that merely "expects" a specific HTTP endpoint to exist, without checking where to look.

Here's an example:

NodeInfo.

It just assumes that everything is in /nodinfo/2.1, without having first consulted /.well-known/nodeinfo for where to properly look.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • mdbf
  • everett
  • osvaldo12
  • magazineikmin
  • thenastyranch
  • rosin
  • normalnudes
  • Youngstown
  • Durango
  • slotface
  • ngwrru68w68
  • kavyap
  • DreamBathrooms
  • tester
  • InstantRegret
  • ethstaker
  • GTA5RPClips
  • tacticalgear
  • Leos
  • anitta
  • modclub
  • khanakhh
  • cubers
  • cisconetworking
  • provamag3
  • megavids
  • lostlight
  • All magazines