From what I’ve read, you want to make sure that the setting is spelled FILMMAKER MODE (in all caps) with a (TM) symbol, since that means that the body who popularized the setting has approved whatever the manufacturer does when you turn that on (so if there’s a setting called “Cinephile Mode” that could mean anything).
With that being said, I’ve definitely seen TVs that just don’t have FILMMAKER MODE or have it, but it doesn’t seem to apply to content from sources like Chromecast. The situation is far from easy to get a handle on.
You can skip the elevation if you don't mind being limited to working when the moon is near the horizon. You don't need to deal with polarization if the far side can handle it.
Maplibre[1] + PMTiles + Felt's "tippecanoe"[2] (it can output .pmtiles) are an awesome combination for self-hosted web maps if you're ok with being locked into a Web Mercator projection
for pretty much any geospatial source you can convert to .pmtiles via GDAL[3] and tippecanoe
(.shp .gpkg ...) | ogr2ogr -> .geojson | tippecanoe -> .pmtiles
for OpenStreetMap data there's planetiler[4], and and openmaptiles[5] styles that work with Maplibre
with those combinations you've got a great start to something you can host for pennies on AWS S3+CloudFront or Cloudflare R2, with an open source data pipeline
I'm a student trying to upskill in geospatial/compsci. What kinds of projects could you make with all of this? Any good starting points you'd recommend?
Not OP, but almost anything where "a map" is the output will be a hugely big learning opportunity for you. Static maps, print-quality maps, interactive web maps -- the experience of building any of those will bring lots of learning. (That's how I got started.)
In 2012, Dmitri Krioukov, a physicist at the University of California, San Diego, faced a $400 fine for allegedly running a stop sign. Instead of accepting the fine, Krioukov crafted an academic paper titled "The Proof of Innocence" to argue his case in court.
Surprisingly, the judge was convinced and acquitted him. Krioukov shared his paper online with a subtitle, "A way to fight your traffic tickets," humorously noting that the paper earned a special prize of $400, which he didn't have to pay to California.
The paper discusses a scenario in which if a car stops at a stop sign, an observer (e.g., a police officer) located at a specific distance perpendicular to the car's trajectory might perceive the car as not stopping under specific conditions. These conditions are:
1 - The observer measures not the linear but angular speed of the car.
2 - The car decelerates and subsequently accelerates relatively quickly.
3 - There is a short-time obstruction of the observer's view of the car by an external object (e.g., another car) at the moment when both cars are near the stop sign.
Disclaimer: the paper was submitted on April 1st, 2012, so there's a non-zero probability this could a be joke by Dmitri :) Either way, it's a good paper."
I'm guessing they've got something like Go's `DisallowUnknownFields()` turned on and the Pleroma extension block is causing an error.
FWIW GotoSocial seems to work (although Ivory is showing that timeline under the wrong user for some reason - all the GtS timeline posts are shown as the user I logged into the Akkoma instance with.)
In summary, if you're not using a Mastodon instance, probably give it a month or two.
EDIT: Having said that, it's showing every timeline item on the GtS instance as the same one - I suspect they might be using integers for IDs (which is what Mastodon - but no-one else - does) and coincidentally this timeline has IDs that all start with `01`. Which would also explain the Akkoma problem since all those IDs are currently starting with `AR` and thus unparseable as integers.
That seems to be deliberate, and I hate it. There are very few reasons any client implementing MastoAPI shouldn't also support Akkoma/Pleroma.
None of the iOS Mastodon apps (except one that is proprietary and seemingly not published on the german appstore) properly support Akkoma notifications, but a somewhat broken Ivory would still be better than a halfway broken Metatext.
> There are very few reasons any client implementing MastoAPI shouldn't also support Akkoma/Pleroma.
Depends how you implement it. e.g. If you use `int64` for your IDs, Akkoma and GotoSocial won't work. Or if you send your POST parameters in the URL, Akkoma won't work. There's other subtle stuff too - toot codes unset optional fields as `null` in the JSON it sends (rather than leaving them out) which breaks both Akkoma and GotoSocial.
In summary, someone needs to write a decent MastoAPI spec and get everyone to agree on that rather than this ad-hoc balkanisation.
Description: ID of the status in the database.
Type: String (cast from an integer but not guaranteed to be a number)
Version history:
0.1.0 - added
In other words, even the Mastodon API docs claim the ID isn't guaranteed not to be a string.
I'm sure there are undocumented differences, but if you base your data model on the spec then there's no reason to even assume you can just use a number.
That was added after the developers of Toot! (iOS app) claimed Pleroma was at fault for it not working with their app because they implemented MastoAPI wrong.
Toot! seems to work with Akkoma/Pleroma now, but notifications are still somewhat lossy.
just tried to get my ruby project running on jruby. It's not a drop in replacement unfortunately, especially with database connectors. I think it makes sense if you're familiar with the Java ecosystem, but a lot of people aren't.
People think I'm joking, but yes. I've had people walk up to me in the store and ask about it. It's a flip on the old joke:
How do you know you are wearing your Apple Watch?
Everyone will ask you about it.
And they are all looking for me to tell them that it's great, that it's wonderful, and that it changed my life. And when I don't, they inevitably have a glint of disappoint in their eyes.
reply