I love the idea of taking on a monopoly, but I don’t like that, without regulation, it has a low chance of success, and the consumer gets to suffer as the monopoly fights back.

Resume field would get an api endpoint that only returns a json resume, and only if the request header is application/json. And the json resume would have embedded json.

We should just use second notation for everything.

I’ll be there in 5 min? I’ll be there in 2 or 3 hundo!

See you tommorow? See you in in 86K!

Next week? About half a Megasec!

Doesn’t Megasecond sound better than Fortnite?

There never was love for flatpaks and there never will be. I’ll never forgive them for killing my son.

Was the OP a blahaj account, or someone from a different instance?

Ahh. I see. I took a look at the script. “Blocked Users,” is not reported by an instance, but rather It’s calculated by this script by looking at “Blocked Instances,” which is reported. How many active users each blocked instance has and then summing this together, the script shows “BU.” I was thinking it was an explicit list of users the instance blocked based on ban/block lists.

It’s a derivative, but still useful metric, I guess. BU could be high, but BI could be low and vice-versa.

This could always change at the whim of an admin as well. It’s good to have admin “teams” and even foundations, but a lot of the time there’s one person making those decisions.

Users and communities could be more portable. Admins should get to decide what is on their instance for sure, but right now there’s kind of a “lock in.” Which give admins disproportional control / responsibility. IMO.

You mean blocked instances right? AFAIK an instances “blocked users” is not published in aggregate. You’d have to comb through the modlog.

More “portable” and secure identities would have been a good feature. The client could have handled most of the crypto required for signing and validating content. As it stands now, the instance Admin has complete control over your identity. Portable communities would follow that easily.

Most of the syncing issues are actually between the large instances or instances that having performance issues.

I had a “bearstein effect” moment just now. I had thought wireshark sold out. Like “Wireshark by Rapid7,” but i just checked and it looks like they’ve stayed the FOSS course! Way to go!

https://wezfurlong.org/wezterm/ssh.html

Bot, you also need to tell people that /c/blah is meaningless. This is not Reddit bot homie!

You’ve got something pretty interesting for us don’t you? Let’s take a look. Wow, yes. I think we might have something here. You should be pretty excited about this!

So, I’ve been looking at old memes for most of my career and only come across a few like this.

There were many communities made to capture old memes but only a few were truly popular. The rarity of these communities also plays a huge part in how valuable the memes are to collectors.

I’ve seen a few others in better condition, but collector demand for this item is still very high.

Given the condition of community and the records kept about the origins, at auction: I’d expect this to go for about…

… three to four million doge.

sparkle sound effect

“Antique Memes Community - Near Worthless” “Owners Thrilled”

When Palo Alto sells your dipshit CIO one firewall appliance per virtual server. “Somehow. Someway,” says the salesperson, “we’re gonna get even more firewalls in here!”

And now the ENTIRE INSTANCE for lululemon, who’s bot posts 1000 times a minute.

If the only criteria to be in a private channel for admins is being an admin, there’s no use making it private. ;) Unless your just looking to filter out bad actors who don’t want to take 5 min and 5$ to make an instance.

FYI for anyone looking to deface more instances, That list is only updated every 24 hours. Depending on when it last run on your home instance, the info could be out of date.

Out of curiosity, where would the regulators go for a case like this? There’s no “company” running it per. se.

Concerns were posted a few days ago, but no POC that used the exact same attack as we saw here. Basically, there were some warnings, and work was underway that would have prevented this, but it was not done fast enough. There is a patch now, that will take a while to roll out, plus a renewed focus on general and related issues.

Don’t fall for it. They’re also an admin on mastodon.world! :)