That is a known bug at the moment. I believe there is a fix in review right now but Codeberg seems to be down.
Search for a community just like you would elsewhere.
This place would be @fediverse@kbin.social, so you'd search that to find this place on the fediverse. Lemmy communities use the same format.
I dislike GBoard because it will frequently autocorrect words which are already correct.
It drives me absolutely insane. Like "it's" is a contraction for "it is", but "its" is a possessive. Yet whenever I want to use possessive "its", autowrong "corrects" it into "it's".
No, that's not what I wanted to say - if I wanted to say that, I would've typed that. You recognize both words as "real" words, yet you insist on changing the correct thing to the incorrect thing.
I love GBoard otherwise, but that drives me positively up the wall. It's a relatively recent behavior, too - it hasn't always done that.
It's funny - I used it for such a long time. Then YouTube didn't support it properly (of all things) and it drove me nuts so I went back to 3 buttons.
The 3 buttons felt so familiar. It was like coming home after being away for a long time.
I'm in the same boat. It was getting to the point where my whole computer would randomly lock up whenever I tried to share my screen on Zoom or when I opened the Windows settings menu. Opening the Start menu could take a solid 30 seconds sometimes.
Then I got an OS notification that was actually an Xbox Game Pass ad and decided I had enough. I installed Linux, and after a few days of distro-hopping I settled on KDE Neon. I WFH from it every day, using Zoom for meetings and Parsec to connect to a Windows computer in the office for work. No issues, except that Proton isn't quite as performant as native Windows.
Yes, and that's likely why Threads uses ActivityPub to begin with. See the EU's Digital Markets Act: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/digital-markets-act-ensuring-fair-and-open-digital-markets_en
Examples of the “do’s” - Gatekeeper platforms will have to:
- allow third parties to inter-operate with the gatekeeper’s own services in certain specific situations
- allow their business users to access the data that they generate in their use of the gatekeeper’s platform
- provide companies advertising on their platform with the tools and information necessary for advertisers and publishers to carry out their own independent verification of their advertisements hosted by the gatekeeper
- allow their business users to promote their offer and conclude contracts with their customers outside the gatekeeper’s platform
The interoperability is the big one. Being federated means that Threads isn't considered a "gatekeeper platform". I wouldn't be surprised if Instagram and maybe even Facebook itself start to federate as well. Since Threads isn't currently connected to the wider fediverse, that's probably why they're not in the EU yet.
This also means that fears of "Embrace, Extend, Extinguish" are likely overblown. Breaking fediverse interoperability means that they'd be a gatekeeper again and subject to EU regulations against gatekeepers. The whole reason why Facebook is making Threads ActivityPub is so they don't get hit by EU rules about being gatekeepers of content.
This means your normal fediverse apps (e.g. Fedilab) would be able to work with Threads natively, without any need for "read-only" instances like you say.
Interestingly, on Kbin this is upside down but on the original instance it's right-side up.
- React.js
React is a JavaScript library that was created by Facebook.
It makes webpages pretty, basically. It makes things load really really fast while still looking clean and modern.
Dropbox, Paypal, Discord, Slack, Netflix, AirBnB all use React.
- MySQL
Facebook didn't create MySQL, but they have contributed to it.
MySQL is a way of efficiently storing large amounts of data. Users, passwords, credit card info, anything that needs to store a lot of things will have at least considered MySQL.
Other places that use MySQL are Twitter, Pinterest, GitHub, YouTube, Spotify, and so on.
- Memcached
Memcached was originally developed for LiveJournal, but Facebook has contributed to it.
It's a way to quickly store arbitrary data, and reduces how many API calls you need to make. This in turn makes running a large website cheaper, since you can just look up the data in your own memory rather than needing to make an API call.
YouTube, Twitter, Reddit, and Pinterest all use Memcached.
- HHVM
HHVM was created by Facebook.
HHVM is what executes the Hack programming language (also made by Facebook). Hack is based on PHP (the same thing Kbin runs on), but is optimized in a different way and is more flexible than traditional PHP.
Slack and Wikipedia are the biggest users of HHVM.
- Cassandra
Cassandra was created by Facebook.
Cassandra works basically as an alternative to NoSQL (mentioned above). It does much of the same job, but works a bit better making sure there's no single point of failure.
Uber, Netflix, Reddit, Spotify, and Twitter all use Cassandra.
- Scribe
Scribe was created by Facebook.
Scribe aggregates logs from many many servers and helps engineers find problems in large networks.
The name is a little generic so it's hard to find examples, but I know that Dropbox uses Scribe internally and other large companies probably do too.
- Hadoop
Facebook did not create Hadoop, but has contributed to it.
Hadoop is meant for solving problems that take a lot of data. Machine learning (ChatGPT etc.) is the classical example, but really it works well any time you need to process a lot of data.
Uber, Pinterest, Netflix, Spotify, Amazon, and Slack all use Hadoop.
- Hive
Facebook created Hive.
Hive lets you query the results of work done by Hadoop (above). It provides an interface that is similar to MySQL but lets you access Hadoop data.
Uber, Pinterest, Netflix, Spotify, Amazon, and Slack all used to use Hive. It's largely dying out now because it can't keep up with modern data sets.
- Apache Thrift
Thrift was created by Facebook.
It connects programs that were created using different programming languages. They can all share a data format through Thrift, which lets them talk to each other.
Thrift is used by Netflix, Evernote, Twitter, Uber, and reCAPTCHA.
- Varnish
Facebook did not create Varnish, but has contributed to it.
It dynamically figures out what to load when you're on a website, so you can have a lot of stuff on one webpage but have it still load quickly.
GitLab, Pinterest, Twitch, and Udemy all use Varnish.
Literally you could not use the modern web without using these technologies. Meta has a loud voice in most of those techs, and outright controls a handful of them. That's been the case for most of the 2010s into the 2020s.
While I don't think Facebook necessarily has good intentions - they're a corpo, corpos are never your friends, Facebook especially has proven to be evil - they have proven to be good stewards of open-source technologies for over a decade now.
I wouldn't say I trust them with the fediverse. But I'm also not so quick to jump to EEE because they do have a fairly solid track record when it comes to web tech.
Are you worried about EEE coming for those techs?
It's the same thing. Why are people treating them differently?
A more likely explanation for Meta's actions is that the Digital Markets Act is forcing them to adopt the fediverse: https://commission.europa.eu/strategy-and-policy/priorities-2019-2024/europe-fit-digital-age/digital-markets-act-ensuring-fair-and-open-digital-markets_en
Examples of the “do’s” - Gatekeeper platforms will have to:
- allow third parties to inter-operate with the gatekeeper’s own services in certain specific situations
- allow their business users to access the data that they generate in their use of the gatekeeper’s platform
- provide companies advertising on their platform with the tools and information necessary for advertisers and publishers to carry out their own independent verification of their advertisements hosted by the gatekeeper
- allow their business users to promote their offer and conclude contracts with their customers outside the gatekeeper’s platform
The interoperability is the big one. The fediverse gives a way for Meta to be in compliance. EEE that breaks the wider fediverse will cause the EU to come down on them.
Exactly. Keep this flagship instance general-purpose. If federation with Meta means you can't "feel safe here", then "pack it up" as you say and choose a place with a moderation style that fits you.
Don't try intimidating everywhere else into adopting your beliefs, like many people here are doing.
At the Extend phase I would encourage fighting back - or at least making it clear that we are separate from Threads and shouldn't copy them.
I wouldn't leave for Threads during Extinguish; I'd stay here. But I would just sit back and mourn what could've been.
Just like how I mourn XMPP whenever I see Pidgin in software center.
Just like how I mourn when my Windows Phone had SMS, Hangouts, and Facebook Messenger all in the stock texting app.
I'll survive. I'm not going to Zuck's site. But I'll be really sad that I'm not going to be able to talk to my friends from anywhere else.
EnglishMobster
joined 1 year ago
I believe it would also extend to anything that can be confused with the white and blue logo in the context is social media.
I can't take the Android droid logo, make him blue, give him a squiggly antenna, and then try to make him the logo of my new phone company.
While Meta doesn't own the letter X, if the government says "People might get confused between these two marks" that's a valid reason to reject the trademark or prevent the company from calling itself that. See https://www.uspto.gov/trademarks/search/likelihood-confusion:
So basically it would come down to a judge deciding if the marks are too similar to each other or not.
So I could use something similar to the Android logo to sell fishing supplies, since the likelihood of confusion is small - Android doesn't make fishing supplies. We only have an issue if I start selling phones or if Android starts selling fishing supplies.