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.
💩 🫘
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.
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.
Bot, you also need to tell people that /c/blah is meaningless. This is not Reddit bot homie!
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!”
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.
You’re not misunderstanding. They just solve more than one issue, and create a few too.
That’s a personal preference though. You don’t have a need for a relay. There are more than a few people who want to run their own instance and at least browse all the things without having to subscribe to them. This is a news aggregator at the core after all.
I’ve been pondering trying to make one, but it’s not going to be a cake-walk. The tool (that was a script) I wrote ruffled some feathers for it’s potential to destroy the lemmyverse. While I don’t believe that could happen. I’m still interested in something easier and more integrated.
The theory is simple and I am willing to take a stab at it, but there might be road blocks trying to make or incorporate changes to the actual lemmy code.
That makes more sense.
So any comment or post?
People can defederate from an instance for any reason they want, but if I get what you’re trying to say: you think people should defederate from any instance that has a user that subscribes to all of their communities.
I actually wrote it with the flip side of your centralization argument in mind. If a community exists outside of the popular ones a user may never even know of its existence. Having more show up SHOULD be better to prevent centralization no? It requires the users to change their browsing behaviour but at least they don’t have gonsearching offsite.
The pricing scheme here is designed to gouge businesses for equal or more than the traditional non-cloud equivalent. Which happens to be completely unaffordable. Imagine buying a new enterprise grade server for your home setup.