wut42

15 ms·

151.
by wut42 4y ago
I kinda regret putting "transphobic" in my own comment tbh- it may have been better to just say at "toxic personality". My intention when raising that fact was just to add color to the thread, not really to start a flame
152.
by wut42 4y ago
Sorry to not have kept a complete collection and memory all a random asshole on the Internet has said.
153.
by wut42 4y ago
There was a some efforts to bring Pleroma-specific features to apps but that went down the drain. Some apps do (Fedilab comes to my mind, IIRC). Given it clones the Mastodon API- all clients should work with Pleroma, minus the small Pleroma
154.
by wut42 4y ago
I have really stopped following the Gleason' arc like three years ago, so I don't remember. He surely does lot of crappy comments but I cannot remember the specifics, maybe someone with a larger memory than mine can reply to this.
155.
by wut42 4y ago
I mean, it is strictly informational. I'm just pointing out a fact, that also made a couple of core devs go away.
156.
by wut42 4y ago
For context and history about Soapbox: it originated from the Gab.com's frontend, and is developed by Alex Gleason, an infamous transphobe/alt-right dude. His involvement in Pleroma made many of its developers leave the project, e
157.
by wut42 4y ago
Agree. While I'm pretty sure this is to bury the articles in search, that part is probably just technical reasons (or, even more credible, technical laziness).
158.
by wut42 4y ago
I was thinking of the Pytorch supply-chain issue as well: https://www.bleepingcomputer.com/news/security/pytorch-discl... I can see someone working at Slack try a nightly, they surely work with ML.
159.
by wut42 4y ago
Very doubtful on SEO and/or alternate content. BleepingComputer also notes the August 2022 notice, which is 'noindex' on all versions. This is most definitely to burry the notices.
160.
by wut42 4y ago
In a "few days", well we have the August 2022 precedent! > In August 2022, Slack reset user passwords after accidentally exposing the password hashes in a separate incident. Unsurprisingly, that particular notice is also marked
161.
by wut42 4y ago
that's why you use rel=canonical and rel=alternate. Read the google recommandations. Nowhere it is said to add noindex. Just the rels.
162.
by wut42 4y ago
Late to the party but depending on your charger voltage, it may be. e.g. I can charge my mbp on a cheap usb-usb-c charger but as soon as I use it _too_ much, it will stall, or worse, lower.
163.
by wut42 4y ago
That must be using CUDA then, and you need a gpu with at least 8GB of VRAM, afaik (not RAM).
164.
by wut42 4y ago
He did made a research team at Twitter for distributed protocols, "Project Bluesky". Looks like it spinned of Twitter as a Public Benefit LLC in the early months of 2022. https://blueskyweb.xyz
165.
by wut42 4y ago
Previously: https://news.ycombinator.com/item?id=24279093
166.
by wut42 4y ago
And their post history says: "still speculation without being an employee"
167.
by wut42 4y ago
Yes, it was the point I was trying to make: it all comes with tradeoffs. Sidekiq choosed to not go forward with backwards compat, and I don't feel it make them "bad citizens" like you implied in your original comment.
168.
by wut42 4y ago
>How does backward compatibility mean a project is unhealthy? It doesn't mean it is, yes. Compat or not isn't a "healthy metric" at all. >How is someone who shows up and volunteers to help not a contributor by defa
169.
by wut42 4y ago
Are they really not "good open-source citizens" ? Keeping backwards compatibility doesn't mean a project is healthy, far from it. Volunteering to maintain backward compat. It can be very damaging in an open-source project. So
170.
by wut42 4y ago
They could have migrated customers while saying EOL to the free tier. I'm more inclined to think that they had two Redis SaaS offerings and the one who was less used/less maintained lost the internal battle.
171.
by wut42 4y ago
They (Rackspace) OWNS another Redis hosting platform: https://www.objectrocket.com/managed-redis/ . It's ridiculous that they didn't migrate customers instead of closing up with a two months notice in the summ
172.
by wut42 4y ago
I don't think you are. My knowledge may be outdated but Spotify uses a lower bitrate than Apple Music (which can go up to lossless) and the Airpods supports that lossless, too.
173.
by wut42 4y ago
The only thing they can make scale is their pricing, I guess! :)
174.
by wut42 4y ago
I wonder if this isn't an exaggeration of the feature freeze announced yesterday.
175.
by wut42 4y ago
While I absolutely hate when companies hikes up prices, "how do you know they won’t do it again next year?" isn't really a good argument. Any company can and will rise their prices whenever they want. You can not know if Miga
176.
by wut42 5y ago
Well given they went bust... don't worry about buying one of their products again :)
177.
by wut42 5y ago
Erlang/Elixir + Rust is an awesome couple. For the downside you mentioned, depending on the use case, it could be interesting to use Rust as a node: https://github.com/sile/erl_dist
178.
A New Chapter Begins for Triton and SmartOS(joyent.com)
3 points by wut42 5y ago|0 comments
179.
by wut42 5y ago
The Joyent that made Node wasn't really the Joyent that brought TextDrive, afaik. That company has a long history of.... fuckups, maybe ?
180.
by wut42 5y ago
https://signal.org/bigbrother/

More ›