Similarly, promise of future plugins from “the community”.
290 karma · joined July 28, 2022
So they wouldn’t be selling the US subsidiary, they’d be selling the entire golden goose.
May I ask how you came to this conclusion?
The Cloudinary article appears to show jpegli beating mozjpeg and turbojpeg even at the "Medium" setting (less bits per pixel).
At least you get a clue in this case (and the famous 500 miles email), I was having sporadic disconnections with cable internet for the last 2 month and my ISP can’t find anything wrong.
Had to switch back to DSL and pay more for slower speed.
https://github.com/mudgen/runcss
The fact that you now require JS to get your styling to work is a big con.
They probably gave up because they simply don’t have the money/resources to pursue this.
Chrome never gained that ability for whatever reason.
You don't have to operate like a VC-funded company and look for infinite growth, if you want to stay small with cheap production then just stay small?
There's likely a silent majority that supported the creator because they are authentic and relatable.
Just make it clear to your supporters that's your objective and don't expect more.
And I doubt the type of user Nekoweb (and Neocities) targets is well-versed or comfortable with S3/Cloudfront.
I feel that if you decouple the social reward and the grunt work of moderation and financial burden of hosting the relay, then the incentives just wouldn't be there to do the dirty work unless it becomes paid or monetized in some way.
After the Twitter debacle I'm done with the idea of being "married" to any network.
I'd say all the long-running forum based communities proves that yes it is. Not counting Usenet, IRC and other "old internet communities" which have withstood the test of time.
> Can you trust an admin to host and police your social network?
That's where the federated part comes in, you choose a server and admin that you trust.
Preventing people from moving server would be holding them hostage, breaking the fundamental trust of the platform and become public enemy numero uno overnight.
I really doubt anyone would do it, but yes the chance isn't zero. Plenty of people host servers with their real identity and reputation on the line though.
If you are still paranoid you can join a commercial server where by contractual obligation they have to provide service to you and allow you to move away.
> What is there to hold hosts accountable for security? The threat of reputational damage doesn't seem like it is going to mean much to pseudonymous volunteers, so what can be done to ensure hosts are properly protecting the system from promise?
Again, you choose your server based on your risk tolerance. You can go with the main mastodon.social server, or join a server owned by a real person you feel is reputable/trustworthy, or join a paid server.
And I would disagree about pseudonymous volunteers not caring about reputation damage, the vast majority of people would feel a sense of ownership over their online identity, especially if it has a lot of clout.
> Reddit moderators are, by and large, reasonable but there's a non-trivial minority who will do things like stage a coup against the other moderators, start arbitrarily banning or harassing people, or just straight up ghost the site and never follow up on the rules. same as above, what mechanisms exist to prevent or reverse or take over the actions of an rogue/absentee mod?
Reddit mods are not server owners, at the end of the day they know they're just hosting someone else's party so there isn't a true sense of ownership.
But if a moderator decided to go rogue? It's just like a forum isn't it? Either the owner gets rid of them or you're out of luck.
You can limit damage by backing up your followers and follows on a regular basis so you can rebuild your network if you are forced to create a new account on a different server.
With federated system come the freedom to chose your server and the consequences thereof, you're gonna have to take some personal responsibility by choosing a server that has a healthy community and a responsible moderation team.
At the end of the day I don't think a perfect system exists, they are just different sets of compromises.
Because there’s no social incentive for anyone to set up and maintain relays and moderation service when divorced from actual communities, what’s left are purely financial incentives - paid service, advertisement insertion, data mining, information manipulation etc.
Also the centralization of data distribution and moderation means they are huge undertaking now, both in terms of hosting cost and human cost, it’s almost forcing these services to be commercialized, or you can say discourage anyone not Bluesky from setting up their own relay or moderation service.
For all the faults of ActivityPub, the extremely “gated community” like approach provides the social incentive for users to feel a sense of belonging to a server, and for the server owner and moderator to feel a sense of pride and ownership over providing service to their users. Being within a valued community also incentivizes people to donate to pay for server cost and moderation effort.
ATprotocol will technically allow multiple relays and moderation services, but in reality how many will actually materialize?
As such I feel judging social networking protocols from a purely technical and adversarial point of view (like ATprotocol does) is a mistake, sure you are now no longer beholden to a server, but at the same time you are divorced from a tight knit community and you no longer have skin in the game.
When you have nothing to lose (data, identity and community wise), that’s a double-edged sword.
Traditional way of using CSS I feel is still advantageous for websites (instead of apps) with a limited set of highly reused styles.
Nowadays however there’s a general lack of restraint and self-control when it comes to web design, you must have a million variations of everything.
In that case utility-first CSS clearly wins because there’s almost no reuse except at the per-property level.
https://miragecraft.com/blog/responsive-css-properties
This is what I use for my own site.
This is not designed to attract open source developers, but offers reassurance to end-users against hostile vendor behavior (drastic price increase, disagreeable change of direction, general lack of development etc).
If not a hatch, which model/car do I get for a cheap, reliable, fuel efficient car that can haul largish items?
What it comes down to is what you can legally prove in court and that means having big foundries sue you and having to defend yourself.
Nobody wants to go through that just to use some fonts when there are open fonts available.
If you want something custom then pick a variable font, such as Roboto Flex, and customize it beyond recognition.
In fact that’s where I see the future is headed - “master” variable fonts with all the axis, variant glyphs etc. available to be tweaked.
The user then gets to play with dials and knobs and when satisfied recompile the font to be non-variable in order to shave down the file size.
@media (prefers-color-scheme: dark) { :root { --light: ; --dark:initial; } }
Missed the selector.
You can already do this using the space toggle technique:
:root { --dark: ; }
@media (prefers-color-scheme: dark) { --light: ; --dark:initial; }
.example { color: var(--light, #000) var(--dark, #fff); }
> If no <scope-start> is specified, the scoping root is the parent element of the owner node of the stylesheet where the @scope rule is defined.
It also comes with the ability to set scoping limit.