Mastodon Feed: Posts

Mastodon Feed

Reblogged by kornel ("Kornel"):

AsahiLinux@treehouse.systems ("Asahi Linux") wrote:

For years, the M1 has only supported OpenGL 4.1. That changes today – with our release of full OpenGL® 4.6 and OpenGL® ES 3.2! 🎉

Unlike the vendor’s drivers, our open source Linux drivers are conformant to the latest OpenGL versions, finally promising broad compatibility with modern OpenGL workloads, like Blender, Ryujinx, and Citra.

https://rosenzweig.io/blog/conformant-gl46-on-the-m1.html

Attachments:

Mastodon Feed

Reblogged by isagalaev ("Ivan Sagalaev :flag_wbw:"):

dskuza ("David Skuza") wrote:

After being with Mozilla for a little over 5 years, I've been laid off today, alongside a group of some of my favorite people. So, I'm on the job market! I've got ~8 years #iOS, #Swift, and #ObjC under my belt, working on everything from libraries all the way through full user-facing features. So, I'm #opentowork. Remote (US), working out of the Chicagoland area. 👀 LinkedIn in bio. Boosts would be much appreciated!

Mastodon Feed

Reblogged by isagalaev ("Ivan Sagalaev :flag_wbw:"):

rreverser ("Ingvar Stepanyan") wrote:

I see Mastodon is still being Mastodon: everyone super mad at a guy who just wanted to tinker with protocols and provide a useful bridge between two social networks. Wouldn't want to be in his position today.

What's particularly weird is that ppl seem to be complaining that other servers can effortlessly read their posts without an explicit opt-in. What exactly did they think "decentralised" means?

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

tess ("Dana Fried") wrote:

The issue with the bsky bridge isn't that it's opt-out; as people have pointed out much of fedi is opt-out by default.

The problem is: who do you send a moderation report to? The problem is: it's a server which most fedi servers will have to immediately block for basic policy reasons. The problem is: it's a technical solution to a cultural divide.

And, unless things like blocking, muting, and notifications are done very carefully, it will be easy for bad actors to exploit.

Mastodon Feed

fromjason ("fromjason.xyz 🖤") wrote:

@pluralistic on how #Facebook beat MySpace:
>... It gave them a bot. You fed the bot your Myspace username and password, and it would login to Myspace and pretend to be you, and scrape everything waiting in your inbox, copying it to your FB inbox, and you could reply to it and it would autopilot your replies back to Myspace.
Great read. https://pluralistic.net/2024/01/30/go-nuts-meine-kerle/

Mastodon Feed

collinsworth@hachyderm.io ("Josh Collinsworth") wrote:

I literally don't like *any* of my browser choices now.

Mastodon Feed

pzmyers@octodon.social ("pzmyers 🦑") wrote:

Those aren't love's scars, those are epigenetic marks.

https://freethoughtblogs.com/pharyngula/2024/02/14/how-love-can-last-a-lifetime/

Attachments:

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

CEOs of big corps seem to live on different planets. Announce layoffs and then say, “Your talents have helped us advance our mission of unleashing the power of content around the world.”

https://deadline.com/2024/02/paramount-global-layoffs-begin-ceo-bob-bakish-1235824028/

You may be fired from the job you use to pay for your existence in this world, but just imagine how you advanced the mission of "unleashing the power of content", everybody!

Just wow... O_O

Mastodon Feed

Reblogged by zack@toot.cafe ("Zack"):

Db0@dbzer0.com wrote:

Looks like someone really kicked the hornet’s nest recently on mastodon by announcing (not even deploying) a Mastodon-BlueSky bridge. Just take a look at the github comments here to get an idea of how this was received.

Plenty of people way more experienced than myself have weighted on this issue so I don’t feel the need to leave my two cents. However I wanted to talk about a very common counter-argument made towards those who do not want such bridges to exist. Namely, that Fediverse already provides the tools towards not having such a bridge be an issue: The allow-list model.

The idea being that if your ActivityPub server by default rejects all federation except towards trusted instances, then such bridges pose no problems whatsoever. The bridge (and any potential undercover APub scrappers) would not be able to get to your instance anyway.

Naturally, the counterargument is that this is way too limiting to one’s reach, and they shouldn’t be forced into isolation like this. Unfortunately the alternative here appears to try and scold others into submission, and this is unlikely to be long term solution. Eventually the Eternal September will come to the Fediverse. If you spent the past few years relying on peer pressure to enforce social norms, then the influx of people who do not share your values is going to make that tactic moot.

In fact, we can already see the pushback to the scolding tactics unfolding right now.

The solution then has to be a way to improve the way we handle such scenarios. Improve the tooling and our tactics so that such bridges and scrappers cannot be an issue.

A lot of the frustration I feel also comes down to the limited set of tools provided by Mastodon and other Fediverse services. A lot of the time, the improvement of tooling is stubbornly refused by the privileged core developers who don’t feel the need to support the needs of the marginalized communities. But that doesn’t mean the tooling couldn’t be expanded to be more flexible.

So let’s think about the Allow-List model for a moment. The biggest issue of an Allow-List is not necessarily that the origin server restricts themselves from the discussion. In fact they’re probably perfectly happy with that. The problem is that if this became the norm, it massively restricts the biggest strength of the Fediverse, which is for anyone to create and run their own server.

If I make a new server and most of everyone I want to interact with is in Allow-List mode, how do I even get in? We then have to start creating informal communication channels where one has to apply to join the allow-circle. Such processes have way too many drawbacks to list, such as naturally marginalizing Neurodivergent people with Rejection Sensitivity Dysphoria, balkanizing the Fediverse, empowering whisper networks and so on.

I want to instead suggest an alternative hybrid approach: The Feeler network. (provisional name)

The idea is thus: You have your well protected servers in Allow-List mode. These are the servers which require protection from constant harassment when their posts are spread publicly. These servers have a few “Feeler” instances they trust on their allow-list. Those servers in turn do not have an allow-mode turned on, but rely on blocklist like usual. Their users would be those privileged enough to be able to handle the occasional abuse or troll coming their way before blocking them.

So far so good. Nothing changes here. However what if those Feeler servers could also use the wider reach to see which instances are cool and announce that to their trusted servers? So a new instance appears in your federation. You, as a Feeler server, interact with them for a bit and nothing suspicious happens, and their users seem all to be ideologically aligned enough. You then add them into a public “endorsed list”. Now all the servers in your trust circle who are in allow-mode see this endorsement and automatically add them to their allow-lists. Bam! Problem solved. New servers have a way to be seen and eventually come into reach with Allow-List instances through a sort of organic probation period, and allow-listed servers can keep expanding their reach without private communications, and arduous application processes.

Now you might argue: “Hey Db0, yes my feelers can see my allow-list server posts, but if they boost them, now anyone can see them, and now they will be bridged to bluesky and I’m back in a bad spot!”

Yes this is possible, but also technically solvable. All we need to do is to make the Feeler servers only federate boosted posts from servers in allow-mode, to the servers that the ones in the allow-list already allow. So let’s say Server T1 and T2 are instances in allow-list mode which trust each other. Server F1 is a Feeler server trusted by T1 and T2. Server S1 is an external instance that is not blocked by F1, but not yet endorsed either. User in F1 boosts a post from T1. Normally a user in S1 would see that post by following that user. All we need to do is to change the software so that if F1 boosts a post from T1, the boost would only federate towards T2 and other instances in T1’s allow-list, instead of everyone. Sure this would require a bit more boost complexity, but it’s nothing impossible. Let’s call this “protected boost”.

Of course, this would require all Apub software to expose an “Endorsement” list for this to work. This is where the big difficulty comes from, as you now have to herd the cats that are the multitude of APub developers to add new functionality. Fortunately, this is where tools like the Fediseer can cover for the lack of development, or outright rejection by your software developer. The Fediseer already provides endorsement functionality along with a full REST API, so you can already implement this Feeler functionality by a few simple scripts!

The “protected boost” mode would require mastodon developers to do some work of course, as that relies in the software internals which cannot be easily hacked by server admins. But this too can potentially just be a patch to the software that only Feeler-admins would need to run.

The best part of this approach is that it doesn’t require any communication whatsoever. All it needs is for the “Feeler” admins to be actively curating their endorsements (either on the Fediseer, or locally if it’s ever added to the SW). Then all allow-list server has to do is choose which Feelers they trust and “subscribe” to their endorsement list for their own allow-list. And of course, they can synchronize or expand their allow-list further as they wish. This approach naturally makes the distributed nature of the Fediverse into a strength, instead of a weakness!

Now personally, I’m a big proponent of the “human touch” in social networks, so I feel that endorsement lists should be a manual mechanism. But if you want to take this to the next level, you could also easily set up a mechanism where newly discovered instances would automatically pass into your endorsement list after X weeks/months of interaction with your user without reports and X-amount of likes or whatever. Assuming admins on-point, this could make widely Feeler servers as a trusted gateway into a well protected space on the fedi, where bad actors would find it extraordinarily difficult to infiltrate, regardless of how many instances they spawn. And it this network would still keep increasing each reach constantly, without adding an extraordinary amount of load to its admins.

Barring the “protected boost” mode, this concept is already possible through the Fediseer. The scripts to do this work already exist as well. All it requires is for people to attempt to use it and see how it functions!

Do point out pitfalls you foresee in this approach and we can discuss how to potentially address them.

https://dbzer0.com/blog/can-we-improve-the-fediverse-allow-list-model/

#fediseer #fediverse #mastodon

Attachments:

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

WARNING: Possible context collapse. You are about to reply to a person you do not follow, and they do not follow you. To continue, please check the boxes that describe your post:

[ ] It is true
[ ] It is kind
[ ] It is necessary

[ OK ] [ Cancel ]

Mastodon Feed

Gargron ("Eugen Rochko") wrote:

Brickwork. Brussels.

Pentax 6x7
Ilford Delta 400
Takumar 105mm/2.4

#BelieveInFilm #FilmPhotography #AnalogPhotography #MediumFormat #MonochromePhotography #BlackAndWhitePhotography

Attachments:

Mastodon Feed

fribbledom ("muesli") wrote:

Keming, noun.

kem-ing, plural kemings.

The result of improper kerning.

Mastodon Feed

fribbledom ("muesli") wrote:

"Hey, how are you, is everything okay?"

LOL OMG NO.

But for the purposes of this conversation, thanks for asking, I'm just fine.

Mastodon Feed

fribbledom ("muesli") wrote:

That elephant really tied the room together.

Mastodon Feed

Reblogged by kornel ("Kornel"):

falkowata@strangeobject.space ("Kat") wrote:

Our take on catification is a permanent pile of papers in the middle of the kitchen - and the cats love it!
#CatsOfMastodon

Attachments:

Mastodon Feed

Reblogged by fribbledom ("muesli"):

grindhold@chaos.social wrote:

you've heard of PALWORLD. now, get ready for NTSCWORLD! 🕶️

Mastodon Feed

Reblogged by keul@fosstodon.org ("Luca Fabbri"):

eric@mastodon.ericlathrop.com ("Eric Lathrop") wrote:

Some cool #Firefox add-ons for improving #Mastodon:

Simplified Federation: https://addons.mozilla.org/en-US/firefox/addon/mastodon-simplified-federation/?ref=upstract.com
Automatically take you to your home instance when you try to follow people from a page on another instance.

StreetPass: https://addons.mozilla.org/en-US/firefox/addon/streetpass-for-mastodon/
Automatically discovers mastodon accounts on any web page you visit. Keeps a list so you can browse accounts at your convenience.

Substitoot: https://addons.mozilla.org/en-US/firefox/addon/substitoot/
Fill in missing replies, boost/favorite counts, profile pages.

Mastodon Feed

Reblogged by keul@fosstodon.org ("Luca Fabbri"):

andreabettini@mastodon.uno ("Andrea Bettini") wrote:

La concentrazione oraria di PM10 in Pianura Padana fra il 1° gennaio e il 31 gennaio 2024. Impressionante
(Fonte: CAMS/ECMWF) https://www.esa.int/Applications/Observing_the_Earth/Air_pollution_fluctuations_over_the_Po_Valley

Attachments:

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

esther@strangeobject.space ("Esther is walking") wrote:

Earlier today, @danhon posted these amazing signs against unwanted replies.

Here's a convenient little website (with no cookies, no ads, no tracking) with all of them ready to download and use, including alt-text that you can easily copy.

https://files.selfawaresoup.com/need-not-reply/

See also Dan's thread https://dan.mastohon.com/@danhon/111925461009889302

Attachments:

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

SmudgeTheInsultCat@mas.to ("Smudge The Insult Cat 🐀") wrote:

Attachments:

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

kdriscoll@aoir.social ("Kevin Driscoll 📳") wrote:

The original WWW proposal is a Word for Macintosh 4.0 file from 1990. Recovering the text, diagrams, and formatting was not impossible but it was hard. A great example of the use of #emulation for historical research and digital preservation.

https://blog.jgc.org/2024/02/the-original-www-proposal-is-word-for.html

Attachments:

Mastodon Feed

Reblogged by rmrenner ("The Old Gay Gristle Fest"):

mouse@bookwyrm.social wrote:

"We usually describe the smell [of blood] as "metallic" because it's similar to the smell left on our fingers when we handle coins, or in the air when we scrub a bare metal pan or sink. ... Our hominid ancestors would have known that molecule [epoxy decenal] and smell long before they paid much attention to rocks and ores, so for much of our prehistory, they may well have experienced metals as bloody-smelling."

— Harold Mcgee: Nose Dive, pp. 502-503

Attachments:

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

(I'm ignoring for the moment the problematic attitude of those who think they have a natural right to do something simply because it is easy to do with a computer and a network.)

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

I think that it's probably not possible to serve both the desire to potentially reach everyone (1:∞) and a desire to have mostly private conversations with a small group of people (1:1) on a single platform.

We probably all need access to both types of communication media, but it doesn't feel like they can fit together in the same space. It's like trying to have your book club meeting at a rock festival. Or hold your rock festival at the corner coffee shop.

Mastodon Feed

fromjason ("fromjason.xyz 🖤") wrote:

"Tech #Threads" is almost exclusively #Meta employees quote posting Meta affiliates about Meta offerings, while trying to appear organic.

It's all very "hey fellow kids" meets Truman Show.

Attachments:

Mastodon Feed

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

mcc wrote:

I wish that it felt like Mozilla knew what Mozilla is for

Mastodon Feed

lloydmeta ("Lloyd") wrote:

This sucks… got an email from Authy saying they’re discontinuing their desktop app even earlier than expected. I wish they offered an export to 1Password

Mastodon Feed

cstanhope@social.coop ("Your friendly 'net denizen") wrote:

I hadn't heard Michigan repealed their "right to work" law, but it's in effect now.

https://truthout.org/articles/michigans-historic-right-to-work-repeal-goes-into-effect/

Probably helps that they only passed the "right to work" in 2012, but still good news.

Mastodon Feed

Reblogged by collinsworth@hachyderm.io ("Josh Collinsworth"):

henry@front-end.social ("henry ✷") wrote:

is there a mister en place

Mastodon Feed

Reblogged by fromjason ("fromjason.xyz 🖤"):

Jyoti@mas.to ("Jyoti Mishra") wrote:

I'm gonna keep posting this as it keeps annoying bootlickers.

#ACAB #FuckThePolice

Attachments: