And no mention of what happens to their API but knowing google it either goes away entirely or totally changes with significant rework required.

Related, the reason I no longer use any google API: https://steve-yegge.medium.com/dear-google-cloud-your-deprecation-policy-is-killing-you-ee7525dc05dc

I don’t know what happened but in the last half hour the website has become highly responsive again. Thank you admins for your hard work.

I don’t see a problem so long as they do so in good faith - for example publishing full event contents to ActivityPub instead of adding a link back to the Facebook Threads app, which is basically what a lot of news sites do with their RSS feeds to get advertising money.

So long as they do that, it’s not really possible to do a rug-pull. There are far more Facebook users than Fediverse users after all, so it’s going to be advertising for the Fediverse for as long as this lasts and if users would like to remain part of it they’ll have to move to another server. That is, assuming it ends.

To answer the question though, I don’t care for microblogging personally and I don’t like Meta as a company so I won’t use it. I appreciate the scepticism but I feel optimistic.

I expect they’re under some kind of enterprise tier deal so I imagine they’ll get quite a few calls from their account manager before inevitably they just shut off access. This kind of thing happens more often than you’d expect when a company has cashflow issues, they’re probably using many other suppliers as free lines of credit as well.

Look at the top right of my screenshot, you will see some extra icons. I’m sorry, I should have included the URL: https://lemmy.ml/post/1212570?scrollToComments=true

I was logged in under this same account as I was browsing.

Yes, looking at the docs linked from a sibling comment I see that upvotes and downvotes are part of the protocol, which is good to see. To prevent vote stuffing however, it does seem that all instances will have a database of upvotes and downvotes and who did them. They were never really secret anyway but it’s interesting that any server can see this, it’ll be an interesting development to be able to track vote brigading.

It is yes, but there is an (unrelated) Android client called Jerboa if that is the OS you use.

I would very much like the Apollo developer to do this but possibly he’s burnt out on social media and would like to work on something else. He has developed a series of other unrelated apps that make him a decent income also.

Furthermore friends, please sort by new where possible to help give new posts visibility when you interact with them.

I expect it’s accurate to say; their architecture is not like a database where you can add an index on a blocked state and then join against it. You have to get a list of potential posts that the user might want to see and then eliminate any in the block list. There will be a few edge case users who have thousands of block entries and a multithreading strategy is likely required to swiftly filter it in a reasonable timeframe.

However, an architecture I’ve seen that works around this is to build this timeline in the background and present it to the user from a cache, I don’t know if this is what Twitter does as I never worked on that. However, if you want to not have a block feature but have some kind of mute feature anyway I don’t see how there is a meaningful difference.

Haha, that’s a throwback to the days when I helped to manage a phpBB board and there were a few members that would just continuously get into arguments so I edited the database so both of them had each other on their block list. It was very telling when I discovered they unblocked each other a few weeks later and got back to arguing and derailing thread topics.

It is definitely slower than usual. It’s not just you. The site is clearly under very heavy load.

I think probably a pluggable storage backend is the best move. For example, any cloud hosted instance could use a native document storage format such as dynamodb, which is often quite cheap or free for small use-cases.

Furthermore it was quite computationally expensive. Modern CPUs have special instructions to work with AES and other algorithms, but back then it had to be done with individual instructions and with slow clock speeds.

Do upvotes and downvotes federate similarly? If so, how does the protocol prevent vote rigging?

More people = more problems I am certain but this is a social network and without people it will fail. We must all make an effort to be the change that we want to see in the world.

I don’t foresee a problem in the immediate future aside from higher server load, but in terms of culture, only people who believe in a new social network will be willing to join.

In 5 years however when this is a great place to be, a large number of people will join who don’t respect the legacy. The departure from Digg to Reddit felt like this too, I hope that the federation aspect will ensure this is longer lived.